This discussion is archived
1 2 Previous Next 28 Replies Latest reply: Jan 17, 2013 7:42 AM by oveht RSS

SHUTDOWN: waiting for logins to complete.

732311 Newbie
Currently Being Moderated
Hi expert,
i'm trying to shutdown the db but the command don't finish.
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jul 2 11:24:37 2010
Copyright (c) 1982, 2005, Oracle.  All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options

SQL> shutdown normal;
in alert file log:
Active process 13138 user 'oracle' program 'oracleTMPDB@SvilDB01'
Active process 6615 user 'oracle' program 'oracleTMPDB@SvilDB01'
Active process 8262 user 'oracle' program 'oracleTMPDB@SvilDB01'
SHUTDOWN: waiting for logins to complete.
Fri Jul  2 11:44:49 2010
MMNL absent for 1203 secs; Foregrounds taking over
$ date
Fri Jul  2 12:17:08 CEST 2010
I can connect because:
$ echo $ORACLE_SID
TMPDB
$ sqlplus /nolog

SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jul 2 12:21:09 2010

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

SQL> conn /as sysdba
Connected to an idle instance.
SQL> select name from v$database;
select name from v$database
*
ERROR at line 1:
ORA-01034: ORACLE not available
what kind of check can I do?
Many thanks for all suggests.
Cheers,
Lain
  • 1. Re: SHUTDOWN: waiting for logins to complete.
    618702 Expert
    Currently Being Moderated
    Dear Lain,

    Simply kill those session if you want it to continue;
    kill -9 13138 6615 8262
    Ogan
  • 2. Re: SHUTDOWN: waiting for logins to complete.
    618702 Expert
    Currently Being Moderated
    SQL> conn /as sysdba
    Connected to an idle instance.
    SQL> select name from v$database;
    select name from v$database
    *
    ERROR at line 1:
    ORA-01034: ORACLE not available
    You can not query the fixed views until you have successfully mounted the database.
    $ sqlplus / as sysdba
    
    SQL*Plus: Release 10.2.0.4.0 - Production on Fri Jul 2 13:32:51 2010
    
    Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.
    
    Connected to an idle instance.
    
    SQL> select * from v$database;
    select * from v$database
    *
    ERROR at line 1:
    ORA-01034: ORACLE not available
    
    
    SQL> startup nomount;
    ORACLE instance started.
    
    Total System Global Area 4294967296 bytes
    Fixed Size                  2061680 bytes
    Variable Size             805309072 bytes
    Database Buffers         3472883712 bytes
    Redo Buffers               14712832 bytes
    SQL> select * from v$database;
    select * from v$database
                  *
    ERROR at line 1:
    ORA-01507: database not mounted
    Ogan
  • 3. Re: SHUTDOWN: waiting for logins to complete.
    714493 Explorer
    Currently Being Moderated
    try

    shutdown immediate;
  • 4. Re: SHUTDOWN: waiting for logins to complete.
    618702 Expert
    Currently Being Moderated
    I agree with Suhail Faraaz, try the immediate option if you can not solve your problem.

    Shutdown normal will wait for users to end their jobs but on the other hand immediate will not wait and force users to rollback their current transactions.

    Hope it Helps,

    Ogan
  • 5. Re: SHUTDOWN: waiting for logins to complete.
    396172 Journeyer
    Currently Being Moderated
    I don't think its gonna work.

    if you issue shutdown immediate now it will say shutdown already in progress.

    you may use shutdown abort and trust the oracle automatic instance recovery but before that its worth trying killing oracle sessions on OS level using kill -9 if this is Linux.
  • 6. Re: SHUTDOWN: waiting for logins to complete.
    714493 Explorer
    Currently Being Moderated
    if he has issued
    shutdown;
    he can cancel it by using
    control+C
    after this issue
    shutdown immediate;
  • 7. Re: SHUTDOWN: waiting for logins to complete.
    618702 Expert
    Currently Being Moderated
    Dear zahid79,

    The OP has already clarified that the database is on idle state.

    If a shutdown normal command has been launched and if i run another shutdown command with the immediate clause, you are right, we are going to have that relevant error.

    Shutdown abort will solve that problem either like you have declared.

    Ogan
  • 8. Re: SHUTDOWN: waiting for logins to complete.
    732311 Newbie
    Currently Being Moderated
    a very strange issue.
    after some times the process roolback.
    SQL> shutdown normal;
    
    ORA-01013: user requested cancel of current operation
    SQL> SQL> 
    but I don't press CTRL+C or other...
    this is the log in the alert log
    Fri Jul  2 13:31:16 2010
    SHUTDOWN: Active sessions prevent database close operation
    now I'm trying to shutdown immediate and inform u.
    thanks,
    Lain
  • 9. Re: SHUTDOWN: waiting for logins to complete.
    618702 Expert
    Currently Being Moderated
    Lain,

    OK, try the shutdown immediate but now the shutdown command may hang. If it hangs, please paste the last 20 lines of the alert.log file to let us find out the locking session (if exists).

    Ogan
  • 10. Re: SHUTDOWN: waiting for logins to complete.
    396172 Journeyer
    Currently Being Moderated
    if he has issued
    shutdown;
    he can cancel it by using
    control+C
    after this issue
    shutdown immediate;
    only if he has the same session and console intact and open where he did the shutdown normal.
    $ sqlplus / as sysdba
    
    SQL> shutdown normal
    ORA-01013: user requested cancel of current operation
    
    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL>
    but the way OP has described his problem I don't think its the case. If he has already closed the session/console where he did the shutdown normal then where to do Ctrl+c and shutdown immediate:

    I opened another console when the db is progressing with shutdown normal:
    $ sqlplus / as sysdba
    
    Connected.
    SQL> shutdown immediate
    ORA-24324: service handle not initialized
    ORA-24323: value not allowed
    ORA-01090: shutdown in progress - connection is not permitted
    SQL>
    now exit out and open another sysdba console:
    $ sqlplus / as sysdba
    
    Connected.
    SQL> shutdown abort
    ORACLE instance shut down.
    SQL>
  • 11. Re: SHUTDOWN: waiting for logins to complete.
    569317 Newbie
    Currently Being Moderated
    This link may help


    http://www.cryer.co.uk/brian/oracle/SYMownsd.htm

    -SK
  • 12. Re: SHUTDOWN: waiting for logins to complete.
    732311 Newbie
    Currently Being Moderated
    now the shutdown immediate are working...
    $ tail -20 ./bdump/alert_TMPDB.log
    before shutdown immediate
    $ tail -20 ./bdump/alert_TMPDB.log
    Active process 6709 user 'oracle' program 'oracleTMPDB@SvilDB01'
    Active process 24139 user 'oracle' program 'oracleTMPDB@SvilDB01'
    Active process 7961 user 'oracle' program 'oracleTMPDB@SvilDB01'
    Active process 6579 user 'oracle' program 'oracleTMPDB@SvilDB01'
    Active process 6749 user 'oracle' program 'oracleTMPDB@SvilDB01'
    Active process 13138 user 'oracle' program 'oracleTMPDB@SvilDB01'
    Active process 6615 user 'oracle' program 'oracleTMPDB@SvilDB01'
    Active process 24153 user 'oracle' program 'oracleTMPDB@SvilDB01'
    Active process 24173 user 'oracle' program 'oracleTMPDB@SvilDB01'
    Active process 8262 user 'oracle' program 'oracleTMPDB@SvilDB01'
    Active process 24147 user 'oracle' program 'oracleTMPDB@SvilDB01'
    Active process 24123 user 'oracle' program 'oracleTMPDB@SvilDB01'
    SHUTDOWN: waiting for logins to complete.
    ... now after shutdown immediate
    Fri Jul  2 13:31:16 2010
    SHUTDOWN: Active sessions prevent database close operation
    Fri Jul  2 13:33:42 2010
    Shutting down instance: further logons disabled
    Fri Jul  2 13:33:42 2010
    Shutting down instance (immediate)
    License high water mark = 158
    Fri Jul  2 13:38:41 2010
    Active call for process 13138 user 'oracle' program 'oracleTMPDB@SvilDB01'
    SHUTDOWN: waiting for active calls to complete.
  • 13. Re: SHUTDOWN: waiting for logins to complete.
    396172 Journeyer
    Currently Being Moderated
    if it takes too long to finish the shutdown you probably can try the following on the Linux OS prompt and user oracle:

    kill -9 13138
  • 14. Re: SHUTDOWN: waiting for logins to complete.
    618702 Expert
    Currently Being Moderated
    Fri Jul  2 13:31:16 2010
    SHUTDOWN: Active sessions prevent database close operation
    Fri Jul  2 13:33:42 2010
    Shutting down instance: further logons disabled
    Fri Jul  2 13:33:42 2010
    Shutting down instance (immediate)
    License high water mark = 158
    Fri Jul  2 13:38:41 2010
    Active call for process *13138* user 'oracle' program 'oracleTMPDB@SvilDB01'
    SHUTDOWN: waiting for active calls to complete.
    Login with the root user and kill that relevant session that cause the shutdown immediate hung;
    kill -9 13138
    Hope it Helps,

    Ogan
1 2 Previous Next

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points