Oracle: SHUTDOWN: waiting for logins to complete.

[Frank de Vries]

I paste this from the alert.log

Shutting down instance (immediate)
License high water mark = 17
Sun Feb 5 10:20:23 2006
SHUTDOWN: waiting for logins to complete.

I am puzzled because normally on sunday
there is no activity,
so why is it waiting for logins to complete ?

This is an old version 7.2.3 (I know, but
it is linked to an old factory apps , and
robotics don't change so quickly, I am still
waiting for a proposal from Siemens on the
robotics upgrade, meantime I am stuck with
this donkey version)

Anyway any good idea welcome

[DCE · Accepted solution]

Frank,

Do a ps -ef | grep ora to see if there are any calls into the database. I have found that if there is a user process (a query or sql call that was not terminated correctly) the shutdown will hang until the offending process is terminated.

[Steven E. Protter]

Shalom,

There is a bug in the dbshut dommand that ships with oracle.

It should say shutdown immediate

It says shutdown

Kill the processes manually, modify the dbshut command and it will work normally.

Alternetive: shutdown abort;startup;shutdown

SEP

[Arunvijai_4]

Hi Frank,

You can kill the process manually, that is the way to go.

# ps -ef |grep -i ora

# kill -9

The process could have stuck somewhere in the middle query processing.

-Arun

[Luk Vandenbussche]

Frank,

Perhaps it is better to put
'shutdown abort' instead of 'shutdown immediate' in your shutdown procedure.

So you avoid this problem

[Yogeeraj_1]

hi Frank,

Important that you do a "shutdown immediate" instead of a "shutdown normal".

I have seen cases whereby user sessions are "stuck" for days because of various problems (network, application, user locks, etc )

You may further troubleshoot this by adding the command "select * from v$session" in you script and spooling the output to a file that you can later check...

hope this helps too!

kind regards
yogeeraj

[Jakes Louw]

Be careful of shutdown abort, this does not allow a tidy rollback of any pending transactions, and could lead to data loss and data inconsistency at an application level (note, I don't mean at a database file level).
Shutdown immediate is preferred: this goes thru the redo log and reapplies the before- and after-look entries.

[rariasn]

Hi Frank,

more $ORACLE_LOG/$ORACLE_SID/alert*.log

Create script for shutdown oracle database:

CONECTS=$(ps -ef|grep -i oracle$ORACLE_SID|grep LOCAL=NO|grep -v grep|awk '{print $2}')
kill -9 $CONECTS

sqlplus /nolog <connect / as sysdba
shutdown immediate
exit;
EOF

ran

[Arturo Galbiati]

hi,
I suggest:
alter system checkpoint
shutdown abort
startup restrict
shutdown immediate

In this way you will baort all teh sessions connected but making a sutdown immediate as wel you will clean all the momeries, falf, etc.

Of course you must ahve a user with restricted session privilege to perform this.

HTH,
Art

[Frank de Vries]

Thanks , I appreciate your help, although
most was not that usefull, I think some
did not read the question, as the case
was about an shutdown immediate that was
haning, some of you advised me to do
a shutdown immediate; yeah right :)
Still, not bad overall,
I think mr Shalom sussed it quite well :)
"Goed gedaan"