Home » RDBMS Server » Server Administration » DB doesn't go down. (Oracle 10G/HPUX)
DB doesn't go down. [message #322166] Thu, 22 May 2008 12:17 Go to next message
me_maddy
Messages: 31
Registered: April 2008
Member
Hello Everybody,

We have issued shutdown immediate towards one of our database.
however it is almost 7 hrs but DB doesn't go down.
below is the Alert log contents.

EMN0 started with pid=13, OS id=9029
Thu May 22 18:10:27 2008
Shutting down instance: further logons disabled
Thu May 22 18:10:28 2008
Stopping background process QMNC
Thu May 22 18:10:28 2008
Stopping background process CJQ0
Thu May 22 18:10:30 2008
Stopping background process MMNL
Thu May 22 18:10:31 2008
Stopping background process MMON
Thu May 22 18:10:32 2008
Shutting down instance (immediate)
License high water mark = 9
Thu May 22 18:10:32 2008
Stopping Job queue slave processes
Thu May 22 18:10:35 2008
Waiting for Job queue slaves to complete
----Thu May 22 18:30:32 2008
KTSMG_UPDATE_MQL(): MMNL absent for 1262 secs; Foregrounds taking over

Listener is already stopped, but There was still one session connected to the DB in addition to SYS user, so we killed that session and oracle displayed the message session marked for kill.

Please suggest what could be the bottleneck.

Thanks
Maddy.

Report message to a moderator

Re: DB doesn't go down. [message #322167 is a reply to message #322166] Thu, 22 May 2008 12:19 Go to previous messageGo to next message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
identify the OS process where LOCAL=NO & do kill -9 <pid>

Report message to a moderator

Re: DB doesn't go down. [message #322173 is a reply to message #322166] Thu, 22 May 2008 12:38 Go to previous messageGo to next message
me_maddy
Messages: 31
Registered: April 2008
Member
Quote:
identify the OS process where LOCAL=NO & do kill -9 <pid>


I didn't understand the term LOCAL=NO

Please elaborate a bit.

Thanks for your time.

Regards,
Maddy.

Report message to a moderator

Re: DB doesn't go down. [message #322176 is a reply to message #322166] Thu, 22 May 2008 12:43 Go to previous messageGo to next message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
 
ps -ef | grep LOCAL=NO
oracle   12818     1  0 May15 ?        00:23:03 oracleora1d (LOCAL=NO)
oracle   28102     1  0 May15 ?        00:01:27 oracleora1d (LOCAL=NO)
oracle   19854     1  0 10:40 ?        00:00:00 oracletest (LOCAL=NO)
oracle   20672     1  0 10:41 ?        00:00:00 oracletest (LOCAL=NO)
oracle   22254  2881  0 10:43 pts/1    00:00:00 grep LOCAL=NO

Report message to a moderator

Re: DB doesn't go down. [message #322202 is a reply to message #322166] Thu, 22 May 2008 14:56 Go to previous messageGo to next message
me_maddy
Messages: 31
Registered: April 2008
Member
Hi

I tried but didn't get anything

$ ps -ef |grep LOCAL=NO
   ora10 28946  8867  0 01:25:01 pts/tg    0:00 grep LOCAL=NO


Regards
Maddy

Report message to a moderator

Re: DB doesn't go down. [message #322203 is a reply to message #322166] Thu, 22 May 2008 15:02 Go to previous messageGo to next message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
ps -ef |grep LOCAL=YES

or

alternatively start another sqlplus session &
shutdown abort

[Updated on: Thu, 22 May 2008 15:03] by Moderator

Report message to a moderator

Re: DB doesn't go down. [message #322208 is a reply to message #322166] Thu, 22 May 2008 15:12 Go to previous messageGo to next message
me_maddy
Messages: 31
Registered: April 2008
Member
Thanks Anacedent

I got something now while using the below command.

$ ps -ef |grep LOCAL=YES
   ora10  6368     1  0 17:55:13 ?         0:01 oracletnd (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))


Is it safe to kill the pid [6368] now, if yes what would be the impact.

Regards,
Maddy.

Report message to a moderator

Re: DB doesn't go down. [message #322210 is a reply to message #322166] Thu, 22 May 2008 15:23 Go to previous messageGo to next message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
On the surface I suspect it is just a sqlplus session.
you could query against v$session to see who, what & such got logged into the DB around that time.

I would not be surprised if you have no choice but to do
sqlplus
/ as sysdba
shutdown abort
exit

Report message to a moderator

Re: DB doesn't go down. [message #322212 is a reply to message #322202] Thu, 22 May 2008 15:33 Go to previous messageGo to next message
joy_division
Messages: 4963
Registered: February 2005
Location: East Coast USA
Senior Member
me_maddy wrote on Thu, 22 May 2008 15:56
Hi

I tried but didn't get anything

$ ps -ef |grep LOCAL=NO
   ora10 28946  8867  0 01:25:01 pts/tg    0:00 grep LOCAL=NO




Did you do this on the client, app server or DB server? If you are doing it on your client, this would be the expected result. If you are using an application server, you would need to run that command on the app server.

Report message to a moderator

Re: DB doesn't go down. [message #322216 is a reply to message #322166] Thu, 22 May 2008 15:40 Go to previous messageGo to next message
me_maddy
Messages: 31
Registered: April 2008
Member
I am connected to the DB itself using telnet, and the command is being fired on the DB server.

Any clues.

Thanks,
Maddy.

Report message to a moderator

Re: DB doesn't go down. [message #322220 is a reply to message #322216] Thu, 22 May 2008 15:55 Go to previous messageGo to next message
joy_division
Messages: 4963
Registered: February 2005
Location: East Coast USA
Senior Member
But where do the apps run? Or more precisely, what was connected to the database that you killed?

And you have to clarify what you mean by connected to the DB by telnet. Telnet is a tool to connect to servers, not databases.

[Updated on: Thu, 22 May 2008 15:57]

Report message to a moderator

Re: DB doesn't go down. [message #322284 is a reply to message #322216] Fri, 23 May 2008 00:23 Go to previous message
abs_amit
Messages: 59
Registered: January 2006
Location: delhi
Member
Try this
stop the listener first and then do shutdown abort. After that you can do startup and shutdown immediate for a clean shutdown.

it will rollback all uncompleted transactions.


1. lsnrctl stop <listener_name>

2. sqlplus / as sysdba

SQL> shutdown abort

SQL> startup

SQL> shutdown immediate


Regards
Amit Yadav

Report message to a moderator

Previous Topic: 10.2.0.4 Upgrade issues
Next Topic: SCN
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Mon Dec 02 00:45:07 CST 2024
.:: Forum Home :: Blogger Home :: Wiki Home :: Contact :: Privacy ::.