This discussion is archived
1 2 Previous Next 28 Replies Latest reply: Jan 17, 2013 7:42 AM by oveht Go to original post RSS
  • 15. Re: SHUTDOWN: waiting for logins to complete.
    19426 Guru
    Currently Being Moderated
    What are all these 'oracleTMPDB@SvilDB01' sessions doing? I don't think interactive user sessions, maybe you have to shutdown 'something else' (an application server for example) before shutting down the database.

    Werner
  • 16. Re: SHUTDOWN: waiting for logins to complete.
    mbobak Oracle ACE
    Currently Being Moderated
    If I want a very fast shutdown, and the database in a non-aborted state, I like to do:
    (starting from instance that is up and running)
    SQL> startup force restrict
    SQL> shutdown immediate
    The startup force does a shutdown abort, followed by immediate startup, and the restrict option puts instance into restricted session, to guarantee no users can connect. Then, shutdown immediate will get you a clean shutdown, and it will be fast, cause all users were already booted off.

    Hope that helps,

    -Mark
  • 17. Re: SHUTDOWN: waiting for logins to complete.
    732311 Newbie
    Currently Being Moderated
    great! now the shutdown is done, but after some times.
    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> 
    in the alert log
    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.
    Fri Jul  2 13:43:31 2010
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    Fri Jul  2 13:43:42 2010
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    Fri Jul  2 13:43:53 2010
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    Fri Jul  2 13:44:03 2010
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    Fri Jul  2 13:44:14 2010
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    Fri Jul  2 13:44:24 2010
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    Fri Jul  2 13:44:34 2010
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    Fri Jul  2 13:44:47 2010
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    Fri Jul  2 13:45:00 2010
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    Fri Jul  2 13:45:07 2010
    ALTER DATABASE CLOSE NORMAL
    Fri Jul  2 13:45:07 2010
    SMON: disabling tx recovery
    SMON: disabling cache recovery
    Fri Jul  2 13:45:07 2010
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    Thread 1 closed at log sequence 1680
    Successful close of redo thread 1
    Fri Jul  2 13:45:10 2010
    Completed: ALTER DATABASE CLOSE NORMAL
    Fri Jul  2 13:45:10 2010
    ALTER DATABASE DISMOUNT
    Completed: ALTER DATABASE DISMOUNT
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    about the kill i'm in disaccord with the workaround.
    The kill with "-9" is a SIGKILL, the application can't terminate it internal process. Are u sure that I can this in the unix env?

    Owevere many thanks for all suggest and support.

    Cheers,
    Lain
  • 18. Re: SHUTDOWN: waiting for logins to complete.
    618702 Expert
    Currently Being Moderated
    Hi Lain,

    Just to let you know, when you run the startup command to open up the database, the SMON and PMON may work a little bir harder to maintain the instance consistency by rolling back or forward the transactions and releasing the locks.

    Ogan
  • 19. Re: SHUTDOWN: waiting for logins to complete.
    732311 Newbie
    Currently Being Moderated
    oradba: I don't know who is this user, but u have right, all application will be stop.
    now is ok and thanks to all for any suggest and support :-)
    Cheers,
    Lain

    P.S: this forum is very great and all people very professional, thanks again
  • 20. Re: SHUTDOWN: waiting for logins to complete.
    714493 Explorer
    Currently Being Moderated
    @lain

    have a look at the forum etiquette here
    http://forums.oracle.com/forums/ann.jspa?annID=718

    mark the the reply as helpful or correct

    Edited by: Suhail Faraaz on Jul 2, 2010 6:54 AM
  • 21. Re: SHUTDOWN: waiting for logins to complete.
    732311 Newbie
    Currently Being Moderated
    i'm sorry and thanks for the appointment.
    cheers,
    Lain
  • 22. Re: SHUTDOWN: waiting for logins to complete.
    jgarry Guru
    Currently Being Moderated
    The docs say:

    In unusual circumstances, you might experience problems when attempting to start a database instance. You should not force a database to start unless you are faced with the following:

    You cannot shut down the current instance with the SHUTDOWN NORMAL, SHUTDOWN IMMEDIATE, or SHUTDOWN TRANSACTIONAL commands.

    You experience problems when starting an instance.

    Personally, I think production DBA's should habitually use a tread-lightly, minimal-force-necessary approach, especially when ignoring the docs. Not that the docs are all-seeing and all-knowing and always right. Try doing a startup force pfile=somewrongfile and see if it does what a newbie would expect.

    But then again, I believe in kill before kill -9. So call me a burnt techoweenie.
  • 23. Re: SHUTDOWN: waiting for logins to complete.
    mbobak Oracle ACE
    Currently Being Moderated
    Hi Joel,

    Hmmm.... I checked the 11.2 docs, and found the same text as you quoted above. I'm a little surprised. To the best of my knowledge, startup force is nothing but shutdown abort followed by a startup. Further, to the best of my knowledge, there is no real danger to a shutdown abort, and hasn't been for many years, if there ever was. All we're talking about is doing instance recovery on startup. Same as if your database crashed, and was restarted.

    So, I think the documentation is overly cautious here....but, it's difficult to really argue with the documentation on this point.

    -Mark
  • 24. Re: SHUTDOWN: waiting for logins to complete.
    jgarry Guru
    Currently Being Moderated
    mbobak wrote:
    Hi Joel,

    Hmmm.... I checked the 11.2 docs, and found the same text as you quoted above. I'm a little surprised. To the best of my knowledge, startup force is nothing but shutdown abort followed by a startup. Further, to the best of my knowledge, there is no real danger to a shutdown abort, and hasn't been for many years, if there ever was. All we're talking about is doing instance recovery on startup. Same as if your database crashed, and was restarted.
    There have been several dangers over the years, usually platform specific (shared memory not released, etc.), sometimes feature specific (there was a LOB corruption error under high load, for example - data changing on startup recovery, yikes). Yes, it's instance recovery, and if your instance recovery doesn't work, you have a real problem. From a conservative viewpoint, many standby bugs could be included, since they could happen on startup. Think of standby as quality assurance for startup, and maybe you'll see what I mean. You could do a thousand startups and never see a problem, compare that to the volume of standby applies.

    Personally, I've seen both (standby and startup problems). And if something isn't easily replicable, that doesn't mean it isn't a problem. Should anyone worry about problems from the distant past? Probably not, but still, production DBA's need a conservative viewpoint. Out of production, anything can and should go. Problems arise when cowboy DBA's do macho things in production. That's why you don't allow developers in production, right?

    >
    So, I think the documentation is overly cautious here....but, it's difficult to really argue with the documentation on this point.
    It's caused enough people grief in the past, that's probably one reason (the windows shutdown registry parameter doc bug comes immediately to mind). Another may be DBA 2.0.

    We all need to re-read the docs periodically anyways, preferably with a jaundiced eye.

    >
    -Mark
  • 25. Re: SHUTDOWN: waiting for logins to complete.
    ata_rehman70 Explorer
    Currently Being Moderated
    To implement the solution: 11g

    1. Given OEM connections are active (SYSMAN and DBSNMP), de-activate these sessions, i.e. by stopping the agent/DBConsole
    2. Then shutdown immediate as normal
    - OR -
    There may be processes still running and holding locks at the time a shutdown is issued.
    Sometimes these are failed jobs or transactions, which are effectively 'zombies', which are not able to receive a signal from Oracle.


    If this occurs, the only way to shutdown the database is by doing:
    sql>
    shutdown abort
    startup restrict
    shutdown normal


    The startup does any necessary recovery and cleanup, so that a valid cold backup can be taken afterward.

    If this issue occurs frequently, it would be a good practice to see if there are any active user processes running in v$session or v$process before shutting down the instance.


    If the problem persists, and no apparent user processes are active, you can set this event prior to issuing the shutdown command in order to see what is happening. This will dump a systemstate every 5 minutes while shutdown is hanging
    SQL>
    connect / as sysdba
    alter session set events '10400 trace name context forever, level 1';


    Then issue the shutdown command.


    Ata ur Rehman
  • 26. Re: SHUTDOWN: waiting for logins to complete.
    jgarry Guru
    Currently Being Moderated
    ata_rehman70 wrote:
    To implement the solution: 11g
    Why are you giving an 11g solution to a 10g post that is years old? Please don't revivify old threads.

    >
    1. Given OEM connections are active (SYSMAN and DBSNMP), de-activate these sessions, i.e. by stopping the agent/DBConsole
    How do you know that works? OEM is 9i software.
    2. Then shutdown immediate as normal
    - OR -
    There may be processes still running and holding locks at the time a shutdown is issued.
    Sometimes these are failed jobs or transactions, which are effectively 'zombies', which are not able to receive a signal from Oracle.
    And sometimes people kill parent processes leaving unhandled child processes. And in this thread, there was a dblink issue.

    >
    >
    If this occurs, the only way to shutdown the database is by doing:
    sql>
    shutdown abort
    startup restrict
    shutdown normal


    The startup does any necessary recovery and cleanup, so that a valid cold backup can be taken afterward.
    What's this about a cold backup?

    >
    If this issue occurs frequently, it would be a good practice to see if there are any active user processes running in v$session or v$process before shutting down the instance.


    If the problem persists, and no apparent user processes are active, you can set this event prior to issuing the shutdown command in order to see what is happening. This will dump a systemstate every 5 minutes while shutdown is hanging
    You might want to look up the -prelim command, too.
    SQL>
    connect / as sysdba
    alter session set events '10400 trace name context forever, level 1';


    Then issue the shutdown command.


    Ata ur Rehman
    You might also consider creating two sysdba sessions before trying to shutdown.
  • 27. Re: SHUTDOWN: waiting for logins to complete.
    oveht Newbie
    Currently Being Moderated
    Hello:

    It happened to me as well.
    The solution was to do the following:

    1. Kill Active Sessions
    2. shutdown abort
    3. Startup
    4. shutdown immediate


    Regards,
    Belki
  • 28. Re: SHUTDOWN: waiting for logins to complete.
    oveht Newbie
    Currently Being Moderated
    Hello:

    It happened to me as well.
    The solution was to do the following:

    1. Kill Active Sessions
    2. shutdown abort
    3. Startup
    4. shutdown immediate

    Regards,
    Belki
1 2 Previous Next

Legend

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