SHUTDOWN IMMEDIATE TAKES LONG TIME
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3

Thread: SHUTDOWN IMMEDIATE TAKES LONG TIME

  1. #1
    newbie5 is offline Call me super inquisitive
    Join Date
    Jun 2002
    Posts
    178
    I have a win2000, 8.1.7 database on my laptop. It is a test database with minimal activity. When I issue shutdown immedate it says, database closed and dismounted and hangs there. I had to close the service to shutdown the database.

    How long shutdown immedate normally take? I have the db in archivelog mode. Is there any other alternative other than abort?

  2. #2
    Join Date
    Dec 2001
    Location
    SAN FRANCISCO, CA
    Posts
    306
    shutdown immediate doesnot take much time.
    First instance shutdown , database dismounted and after few seconds then u get database closed.
    should not take much time. ?

    but Do u have more than one instances in ur laptop?

    just try connecting to correct nstance.
    then go to svrmgrl prompt and give connect internal
    and tnen issue shutdown immediate

    Before that just query v$session to see what processes are still running.

    --pravin

    Eat , Drink & Enjoy life -

    pravin_kini@hotmail.com

  3. #3
    Join Date
    Jun 2002
    Posts
    64
    Hi,
    Shutdown immediate disconnects all user sessions and rollback uncommitted transactions. It also causes SMON to clean up temp segments and coalesces free space.

    So, either give it a time to complete what it is doing or do a SHUTDOWN ABORT and then a SHUTDOWN IMMEDIATE, which is not always advisable in a production dbs.

    Also, size your TEMP tablespace to reduce creating many small extents, which will speed up SMON work.


    Cheers

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