Comments on: Resolving Shutdown Immediate Hang Situations http://askdba.org/weblog/2008/05/shutdown-immediate-hang-2/ Writing About Our Experiences With Oracle Databases Fri, 05 Mar 2010 10:24:30 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Tallarico http://askdba.org/weblog/2008/05/shutdown-immediate-hang-2/comment-page-1/#comment-7714 Tallarico Thu, 14 Jan 2010 19:03:39 +0000 http://askoracledba.wordpress.com/?p=44#comment-7714 Thanks very much for the post. This saved the day for me! Thanks very much for the post. This saved the day for me!

]]> By: Saurabh Sood http://askdba.org/weblog/2008/05/shutdown-immediate-hang-2/comment-page-1/#comment-1584 Saurabh Sood Thu, 12 Feb 2009 14:39:18 +0000 http://askoracledba.wordpress.com/?p=44#comment-1584 Hi Sunny, I doubt that it will be useful everytime, because the drop temporary tablespace command will hang also and may take hours. I have seen this type of situation earlier where the temporary tablespace was dropped and we were left with hanging drop tablespace command. Moreover if there are very large temporary segments, it can happen that they will get corrupted and SMON will never clean them up, they will simply consume disk space on the server. Then we have to use the dbms_space_admin.drop corrupt segments() So, I think, it is better to set the event. Cheers!!! Saurabh Sood Hi Sunny,

I doubt that it will be useful everytime, because the drop temporary tablespace command will hang also and may take hours.
I have seen this type of situation earlier where the temporary tablespace was dropped and we were left with hanging drop tablespace command.
Moreover if there are very large temporary segments, it can happen that they will get corrupted and SMON will never clean them up, they will simply consume disk space on the server. Then we have to use the dbms_space_admin.drop corrupt segments()
So, I think, it is better to set the event.

Cheers!!!
Saurabh Sood

]]> By: Sunny http://askdba.org/weblog/2008/05/shutdown-immediate-hang-2/comment-page-1/#comment-1576 Sunny Tue, 10 Feb 2009 18:10:53 +0000 http://askoracledba.wordpress.com/?p=44#comment-1576 Thanks. Sorry it was typo i meant shutdown immediate at end. Instead as we know that shutdown will cleanup the temp segments and if temp tablespace has allocated many(can be checked before shutdown. need to find magin number) that will take up time to cleanup and also do not want to do shutdown abort then create new temp--> reset default temp ts(10g)-->drop temp tabelspace(can be switched again at startup to orignal name since all the users has default temp ts and may be app is alos using temp ts name -->shutdown immediate. (anyways before shutdown we will check and make sure no session are not connected). Just a theory. Thanks. Thanks. Sorry it was typo i meant shutdown immediate at end.
Instead as we know that shutdown will cleanup the temp segments and if temp tablespace has allocated many(can be checked before shutdown. need to find magin number) that will take up time to cleanup and also do not want to do shutdown abort then create new temp–> reset default temp ts(10g)–>drop temp tabelspace(can be switched again at startup to orignal name since all the users has default temp ts and may be app is alos using temp ts name –>shutdown immediate. (anyways before shutdown we will check and make sure no session are not connected).
Just a theory.

Thanks.

]]> By: Saurabh Sood http://askdba.org/weblog/2008/05/shutdown-immediate-hang-2/comment-page-1/#comment-1564 Saurabh Sood Sat, 07 Feb 2009 09:57:44 +0000 http://askoracledba.wordpress.com/?p=44#comment-1564 Hi Sunny, If the shutdown immediate command is hanging, then once you have to a shutdown abort. Then put the event in the init.ora file, startup the database and then issue a shutdown immediate command. It will just force the SMON to skip temporary objects cleanup. There is no need to issue shutdown abort second time. It is : it shutdown abort–>event in .ora –>startup–>shutdown immediate Now with the event in place shutdown immediate command will succeed. Cheers!!! Saurabh Sood Hi Sunny,

If the shutdown immediate command is hanging, then once you have to a shutdown abort.
Then put the event in the init.ora file, startup the database and then issue a shutdown immediate command.
It will just force the SMON to skip temporary objects cleanup.
There is no need to issue shutdown abort second time.
It is :
it shutdown abort–>event in .ora –>startup–>shutdown immediate

Now with the event in place shutdown immediate command will succeed.

Cheers!!!
Saurabh Sood

]]> By: Sunny http://askdba.org/weblog/2008/05/shutdown-immediate-hang-2/comment-page-1/#comment-1559 Sunny Fri, 06 Feb 2009 21:48:14 +0000 http://askoracledba.wordpress.com/?p=44#comment-1559 What is menat by "you can set the following event and bounce the database and reissue shutdown immediate to skip this cleanup:" Is it shutdown abort-->event in .ora -->startup-->shutdown abort. What is menat by “you can set the following event and bounce the database and reissue shutdown immediate to skip this cleanup:”
Is it shutdown abort–>event in .ora –>startup–>shutdown abort.

]]>