If you have initiated
SHUTDOWN command to stop the database, new sessions cannot connect with the
database. This means that even oracle scheduled jobs also cannot be initiated
internally. After initiation of SHUTDOWN, if any scheduled jobs get initiated
(because scheduled time of any job has reached), job would not be started and an
error message will be logged in the alert log file. Following is how alert log
would look like after that. Since this is just an information message, therefore
no action is needed.
Oracle Installation guides, Linux Administration tips for DBAs, Performance Tuning tips, Disaster Recovery, RMAN, Dataguard and ORA errors solutions.
No contents from my website can be published anywhere else without my permission. Test every solution before implementing in the production environment.
Tuesday, July 30, 2019
Friday, July 19, 2019
ORA-39700: database must be opened with UPGRADE option
This message would
appear if you have opened a database from a newer version ORACLE_HOME instead
of the current version of the database. Alert logs shows messages similar to
the following when you open your database with “startup open” command. Instance
would immediately crash after logging these messages in the alert log file.