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.
Popular Posts - All Times
-
This error means that you are trying to perform some operation in the database which requires encryption wallet to be open, but wallet is ...
-
Finding space usage of tablespaces and database is what many DBAs want to find. In this article I will explain how to find out space usage ...
-
ORA-01653: unable to extend table <SCHEMA_NAME>.<SEGMENT_NAME> by 8192 in tablespace <TABLESPACE_NAME> This error is q...
-
You may also want to see this article about the ORA-12899 which is returned if a value larger than column’s width is inserted in the col...
-
This document explains how to start and stop an Oracle cluster. To start and stop Grid Infrastructure services for a standalone installatio...
-
If database server CPU usage is showing 100%, or high 90%, DBA needs to find out which session is hogging the CPU(s) and take appropriate ...
-
If you want to know how we upgrade an 11g database to 12c using DBUA, click here . For upgrading 12.1.0.1 to 12.1.0.2 using DBUA, ...
-
By default AWR snapshot interval is set to 60 minutes and retention of snapshots is set to 8 days. For better and precise investigation of...
-
SWAP space recommendation from Oracle corp. for Oracle 11g Release 2 If RAM is between 1 GB and 2 GB, SAWP should be 1.5 times the s...
-
This article explains how to install a 2 nodes Oracle 12cR1 Real Application Cluster (RAC) on Oracle Linux 7. I did this installation on O...