The database job cannot run after a failed ' Shutdown Immediate '.
Reference text:
Database Jobs don't Run after a Failed ' Shutdown Immediate ' (Doc ID 434690.1)
Suitable for:
Oracle server-enterprise edition-version 9.2.0.1 to 10.2.0.1 [Release 9.2 to 10.2]
Information in this document applies to any platform.
Checked for relevance on 25-jul-2012***
Symptoms:
After a ' shutdown immediate ' is issued, Oracle server automatically cancels the operation if it has not been executed after one hours.
A message appears in the alert log:
Shutdown:active sessions prevent database close operation
Unfortunately, closing all job queue slave processes that are part of the shutdown process has an additional impact,
The effect is that any job in the dba_jobs will not work.
This affects a wide range of functions, such as statistical information collection, replication propagation, materialized view refresh, etc.
Reason:
This is the desired behavior. Once the ' shutdown ' command is issued, the shutdown must be executed.
The shutdown process cannot be rolled back. This is because instance will not live after shutdown conceled.
Solution:
Follow the steps below:
1. If the job in Dba_jobs_running has a related operating system process still exists, these processes should be killed from the OS level
2. Issue shutdown immediate
3. Monitor the database's alert log. If the new ' shutdown:waiting for active calls to complete ' message appears, perform the following:
Shutdown abort
Startup restrict
Shutdown immediate
Startup
It is recommended to have a good backup available before abort database.
