[Translated from mos] The Database job cannot run after a failed Shutdown Immediate .,

[Translated from mos] after a failed 'shutdown immediate', the Database job cannot run .,
After a failed 'shutdown immediate', the Database job cannot run.

Reference Original:
Database Jobs Do Not Run After a Failed 'shutdown immediate' (Doc ID 434690.1)

Applicable:
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, if it has not been executed one hour later, oracle server will automatically cancel this operation.
A message will appear in the alert Log:
SHUTDOWN: Active sessions prevent database close operation

Unfortunately, shutting down all job queue slave processes that are part of the shutdown process has an additional impact,
This effect is-any job in dba_jobs cannot run.
This affects a wide range of functions, such as statistical information collection, replication and propagation, and materialized view refresh.

Cause:

This is the expected behavior. The shutdown command must be executed once it is issued.

The shutdown process cannot be rolled back. This is because the instance will not live after shutdown conceled.

Solution:
Perform the following steps:
1. If there are related operating system processes in the job in DBA_JOBS_RUNNING, these processes should be kill from the OS level
2. Issue shutdown immediate
3. Monitor the database's alert log. If the new 'shutdown: waiting for active callto complete' message appears, execute the following:

Shutdown abort
Startup restrict
Shutdown immediate
Startup

We recommend that you have a good backup available before using abort database.