Database Jobs Do Not Run After a Failed 'Shutdown Immediate'
Last updated on SEPTEMBER 09, 2016
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 to 10.2.0.1 [Release 9.2 to 10.2]
Information in this document applies to any platform.
***Checked for relevance on 09-Sep-2016***
After issuing a 'shutdown immediate' command, if the command does not execute after an hour, the Oracle Server automatically cancels the operation. A message will appear in the alert log as follows:
SHUTDOWN: Active sessions prevent database close operation
Unfortunately this has the added effect of shutting down all the job queue slaves as part of the shutdown process. Any jobs listed in the DBA_JOBS view will not run. This can affect a wide variety of functions, such as statistics gathering, replication propagation, materialized view refresh, etc.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms