Today i faced Strange issue with Shutdown immediate command on cluster database which is when run shutdown immediate the command hangs and take so long and sometimes it’s working and most of the time not working.
the below command was working without any problem :-
SQL > shutdown abort
to solve this issue & trace the error since the alertlog not indicating to anything interesting i have to dump systemstate every 5 minutes to know what going on :-
connect / as sysdba
alter session set events ‘10400 trace name context forever, level 1’;
After this you can kill the session that preventing shutdown.
The hangs usually happened for two reasons :-
- Query running on Database.
- Transaction happened while you are trying to shutdown database.
For the first reason :
use v$session_longops Read more here.
Run the below query to check the query.
select count(*) from v$session_longops where time_remaining>0;
Second reason you can use
v$transaction Read from here.
Useful Document :-
Alert Log: Shutdown Waiting for Active Calls to Complete (Doc ID 1039389.6)
Published by Osama Mustafa
Osama considered as one of the leaders in Cloud technology, DevOps and database in the Middle-East. I have more than ten years of experience within the industry. moreover, certfied 4x AWS , 4x Azure and 6x OCI, have also obtained database certifications for multiple providers.
In addition to having experience with Oracle database and Oracle products, such as middle-ware, OID, OAM and OIM, I have gained substantial knowledge with different databases.
Currently, I am architecting and implementing Cloud and DevOps. On top of that, I'm providing solutions for companies that allow them to implement the solutions and to follow the best practices.
View all posts by Osama Mustafa