In Oracle RAC, the Oracle instances and listeners are automatically started, monitored, and recovered through the Oracle Clusterware. If PRIMECLUSTER Wizard for Oracle detects a resource failure, it will notify RMS of the “Warning” state then ask Oracle Clusterware to generate a failover or recover the failed resource (depending on the WFTime setting).
Also, the resources are started or stopped along with userApplication startup and stop.
Oracle RAC instance startup
Start an Oracle RAC instance as follows:
su - <Oracle user>
srvctl start instance -d $DB_NAME -i $ORACLE_SID
Oracle RAC instance stop
Stop an Oracle RAC instance as follows:
su - <Oracle user>
srvctl stop instance -d $DB_NAME -i $ORACLE_SID
Oracle RAC instance monitoring
The monitoring of an Oracle RAC instance is the same as standby operation. However, the default value of monitoring interval is 60 seconds.
For details, see “Oracle monitoring” of “3.1.1 Standby Operation”.
Listener startup
Listener startup depends on Oracle Clusterware, and PRIMECLUSTER Wizard for Oracle also starts the listener.
Start listener 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.
Listener monitoring
The Oracle monitoring setup is the same as standby operation.
However, tnsping monitoring is not performed, and the default value of monitoring interval is 60 seconds.
For details, see “Oracle monitoring” of “3.1.1 Standby Operation”.
Oracle Clusterware startup
Start Oracle Clusterware 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 Oracle Clusterware as follows:
Shut down Oracle Clusterware using “crsctl stop crs”.
Oracle Clusterware monitoring
PRIMECLUSTER Wizard for Oracle does not monitor Oracle Clusterware. NullDetector flag is automatically enabled.
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.
