problem occured in shutting down the database
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 7 of 7

Thread: problem occured in shutting down the database

  1. #1
    Join Date
    Jul 2006
    Posts
    96

    problem occured in shutting down the database

    hi friends , some times when i shut down the database
    it hangs, and in alert log file it notes ' waiting for active calls...'

    i restarted the system. i am sending the alert log file contents
    and trace file also. can u plz tell what could be the reason
    and in future will become problem??

    IN alert log file:

    Thu . Oct 19 17:56:12 2006

    shutting down instance: further logon disabled
    shutting down instance(immediate)
    licence high water mark = 34

    The Oct 19 18:01:19 2006

    Active Call for Process 3685 user 'oracle' Program ' oracle@hp2(s000)
    shutdown: waiting for active calls to complete

    also the trace file :

    /opt/ora9/admin/oracle/udump/oracle_ora_4834.trc
    Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.4.0 - Production
    ORACLE_HOME = /opt/ora9/product/9.2
    System name: Linux
    Node name: hp2
    Release: 2.4.21-32.ELsmp
    Version: #1 SMP Fri Apr 15 21:17:59 EDT 2005
    Machine: i686
    Instance name: oracle
    Redo thread mounted by this instance: 1
    Oracle process number: 13
    Unix process pid: 4834, image: oracle@hp2 (TNS V1-V3)
    *** SESSION ID:(26.905) 2006-10-19 18:01:19.715
    SHUTDOWN: waiting for active calls to complete.
    *** 2006-10-19 18:06:25.715
    SHUTDOWN: waiting for active calls to complete.
    *** 2006-10-19 18:11:31.715
    SHUTDOWN: waiting for active calls to complete.


    my shell program to shutdown is :

    sqlplus /nolog<< EOF
    conn sys/sys as sysdba
    shutdown immeditae
    !lsnrctl stp
    !sleep3
    EOF

  2. #2
    Join Date
    Dec 2000
    Location
    Ljubljana, Slovenia
    Posts
    4,439
    It means that Oracle is rolling back all active transactions. It has disabled all current session from performin any further actions, it has also disabled any new connections to the database, but in order to shut down a database in consistent state, it must perform a rollback of all the transactions that have not yet been commited at the time when shutdown has begun. If those transaction were "huge" it might take a while before the rollback (and thus shutdown) completes.

    If this takes too long or in the event that database for some reason realy "hangs", you still have the option to perform a SHUTDOWN ABORT.
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

  3. #3
    Join Date
    May 2000
    Location
    ATLANTA, GA, USA
    Posts
    3,135
    Before issuing "SHUTDOWN ABORT" command, you must execute "ALTER SYSTEM CHECKPOINT".

    Tamil

  4. #4
    Join Date
    Dec 2000
    Location
    Ljubljana, Slovenia
    Posts
    4,439
    Quote Originally Posted by tamilselvan
    Before issuing "SHUTDOWN ABORT" command, you must execute "ALTER SYSTEM CHECKPOINT".
    Ummm, why? In particular, why did you use word must? Commited changes are allready witten to disk (redo logs), if they are not allready written to the datafiles they will get there during the startup procedure anyway. I'm not saying that there is anything wrong with performing a system checkpoint before aborting the instance, but it certanly is not mandatory to do it.
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

  5. #5
    Join Date
    Nov 2006
    Location
    Sofia
    Posts
    630
    I see interesting discussion here
    The job should be done and the difference in shutdown immediate and shutdown abort is when the job is done.
    So
    1) Whit shutdown immediate, rollback and checkpoint is done before the database is stopped and that's slow
    2) With shutdown abort none of these is done on shutdown, and it's fast. However, on instance startup you need instance recovery (i.e. roll forward and roll back) The rollback however is doen AFTER the instance opens and in parallel so it seems to be faster aproach. I say SEEMS to be since the rollback is still done but with opened instance.
    3) If you ussue checkpoint before the shutdown abort, you'll save the instance recovery roll forward phase

  6. #6
    Join Date
    May 2000
    Location
    ATLANTA, GA, USA
    Posts
    3,135
    Great guys from Sofia and Ljubljana, Slovenia.

    Tamil

  7. #7
    Join Date
    Oct 2006
    Location
    Mumbai
    Posts
    184
    Quote Originally Posted by madhugp
    hi friends , some times when i shut down the database
    it hangs, and in alert log file it notes ' waiting for active calls...'

    i restarted the system. i am sending the alert log file contents
    and trace file also. can u plz tell what could be the reason
    and in future will become problem??

    IN alert log file:

    Thu . Oct 19 17:56:12 2006

    shutting down instance: further logon disabled
    shutting down instance(immediate)
    licence high water mark = 34

    The Oct 19 18:01:19 2006

    Active Call for Process 3685 user 'oracle' Program ' oracle@hp2(s000)
    shutdown: waiting for active calls to complete

    also the trace file :

    /opt/ora9/admin/oracle/udump/oracle_ora_4834.trc
    Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.4.0 - Production
    ORACLE_HOME = /opt/ora9/product/9.2
    System name: Linux
    Node name: hp2
    Release: 2.4.21-32.ELsmp
    Version: #1 SMP Fri Apr 15 21:17:59 EDT 2005
    Machine: i686
    Instance name: oracle
    Redo thread mounted by this instance: 1
    Oracle process number: 13
    Unix process pid: 4834, image: oracle@hp2 (TNS V1-V3)
    *** SESSION ID:(26.905) 2006-10-19 18:01:19.715
    SHUTDOWN: waiting for active calls to complete.
    *** 2006-10-19 18:06:25.715
    SHUTDOWN: waiting for active calls to complete.
    *** 2006-10-19 18:11:31.715
    SHUTDOWN: waiting for active calls to complete.


    my shell program to shutdown is :

    sqlplus /nolog<< EOF
    conn sys/sys as sysdba
    shutdown immeditae
    !lsnrctl stp
    !sleep3
    EOF
    Dear All,

    I think we havent answered the original question:

    Try this, when you get:

    Active Call for Process 3685 user 'oracle' Program ' oracle@hp2(s000)
    shutdown: waiting for active calls to complete

    At O.S. level:

    $kill -9 3685

    and the shutdown immediate command will execute immediately, you can see the difference by opening alert.log with $ tail -f alert_sid.log

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width