This section describes startup, shutdown and monitoring of Oracle resources in the scalable operation with Oracle RAC.
See
In the Oracle Data Guard/Oracle Active Data Guard environment, for details about startup, shutdown and monitoring of Oracle resources in the scalable operation with Oracle RAC, see "G.3.2 Oracle database Control (Scalable Operation with Oracle RAC)".
Oracle RAC instance startup
Startup procedure of an Oracle RAC instance is as follows:
su - <Oracle user>
srvctl start instance -d $DB_NAME -i $ORACLE_SID
Oracle RAC instance stop
Stop procedure of an Oracle RAC instance is as follows:
su - <Oracle user>
srvctl stop instance -d $DB_NAME -i $ORACLE_SID
Listener startup
Listener startup depends on Oracle Clusterware. PRIMECLUSTER Wizard for Oracle checks listeners. If the listeners are not started, they are started by PRIMECLUSTER Wizard for Oracle.
Startup procedure of a listener is as follows:
su - <Grid user>
srvctl start listener -n $NODE_NAME -l $LSNR_NAME
Listener shutdown
Listener stop depends on Oracle Clusterware, not PRIMECLUSTER Wizard for Oracle.
Oracle Clusterware startup
Startup procedure of an Oracle Clusterware is as follows:
Start up Oracle Clusterware using “crsctl start crs”.
Check if Oracle Clusterware is activated using “crsctl status resource -t”.
Oracle Clusterware stop
Stop procedure of an Oracle Clusterware is as follows:
Shut down Oracle Clusterware using “crsctl stop crs”.
Note
If you want to startup, stop, or switch Oracle instances, execute hvswitch and hvutil on RMS userApplication. If you execute the Oracle Clusterware srvctl command or shutdown command to the Oracle instance directly, PRIMECLUSETR will consider that the instance fails, and recovery processing might be initiated for the Oracle instance. To executing the command, put userApplication into maintenance mode.
Stop userApplication and RMS before shutting down or restarting the OS for maintenance. When shutting down or restarting the OS, the Oracle Clusterware, the Oracle instance, and the listener stop. Therefore, the Oracle instance resource and the listener resource failure will occur when userApplication is Online state.
Monitoring Oracle RAC instances
The monitoring of an Oracle RAC instance is the same as standby operation. For details, see “3.1.1.2 Monitoring Oracle resources".
Monitoring interval (Interval)
The default value of monitoring interval for the background processes (PMON, SMON, DBWn, LGWR, CKPT) is 60 seconds.
Oracle RAC instance errors and recovery
If Oracle RAC instance errors are detected, PRIMECLUSTER Wizard for Oracle notifies RMS of the warning state and waits for Oracle RAC resources to be restarted by Oracle Clusterware.
Oracle Clusterware automatically restart Oracle RAC resources if they fail.
If Oracle Clusterware cannot restart them within a set time of "Interval", PRIMECLUSTER Wizard for Oracle notifies RMS of the Fault state and stops Oracle RAC instances.
For details about "Interval", see "2.3.5 userApplication with Oracle RAC Instances and Listeners".
Monitoring PDB
PDB is not monitored.
Monitoring Listeners
The monitoring of listeners is the same as standby operation. For details, see “3.1.1.2 Monitoring Oracle resources".
Monitoring interval (Interval)
The default value of monitoring interval for listener processes using ps command is 60 seconds.
The tnsping monitoring is not performed.
Listener errors and recovery
If Listener errors are detected, PRIMECLUSTER Wizard for Oracle notifies RMS of the warning state and waits for Listeners to be restarted by Oracle Clusterware.
Oracle Clusterware automatically restart Listeners if they fail.
If Oracle Clusterware cannot restart them within a set time of "Interval", PRIMECLUSTER Wizard for Oracle notifies RMS of the Fault state. PRIMECLUSTER Wizard for Oracle does not stop Listeners.
For details about "Interval", see "2.3.5 userApplication with Oracle RAC Instances and Listeners".
Oracle Clusterware monitoring
PRIMECLUSTER Wizard for Oracle does not monitor Oracle Clusterware. NullDetector flag is automatically enabled.
