This section discusses how to change Oracle settings, apply Oracle patches, backup and recover Oracle Databases. In a cluster system, the shared disk device in which Oracle data is stored is activated and deactivated along with Oracle startup and stop.
Oracle is monitored during userApplication operation. If Oracle is stopped manually, then the cluster system will consider that the Oracle resource fails, so Oracle will be restarted or Oracle operation will be switched to the standby node.
While userApplication is not running, the shared disk is deactivated.
If you need to control Oracle manually for Oracle cold backup or other maintenance tasks, put PRIMECLUSTER in maintenance mode, and stop monitoring the Oracle instances and listeners temporarily.
The basic maintenance procedure is as follows:
Start userApplication
Start userApplication that includes the Oracle instance resource if it is stopped.
Put userApplication into maintenance mode and stop monitoring
Put userApplication into maintenance mode.
Next, stop monitoring the Oracle instance and listener resources by executing the “hvoradisable” command.
Confirmation of maintenance mode and stop of monitoring
Confirm that changing into maintenance mode and stop of monitoring have been successfully done.
(Refer to note of "4.1 hvoradisable - Discontinue Monitoring Resources".)
Stop Oracle-dependent resources
If there are Oracle-dependent resources, stop them manually before stopping Oracle.
Stop Oracle
Stop Oracle manually.
Do maintenance on Oracle
Change the Oracle settings, apply Oracle patches, backup and recovery Oracle Databases.
Start Oracle
After the maintenance is completed, start Oracle. Restart the Oracle listener, if it is also stopped. Before going on to the next step, be sure to check that Oracle instance and listener are properly running. The Oracle instance must be OPEN.
Start Oracle-dependent resources
If Oracle-dependent resources are stopped, start them manually.
Restart resource monitoring and stop maintenance mode
Restart monitoring the Oracle instance and listener resources again using the hvoraenable command.
Next, stop maintenance mode of userApplication.
Confirmation of restart of monitoring and maintenance mode
Confirm that restart of monitoring and changing out of maintenance mode have been successfully done.
(Refer to note of "4.2 hvoraenable - Restart Monitoring Resources".)
Information
About Discontinue Monitoring, Restart Monitoring
For stopping Oracle while userApplication is running, use function of "Discontinue Monitoring" of PRIMECLUSTER Wizard for Oracle.
Function of "Discontinue Monitoring" discontinue only Oracle monitoring. Therefore, note that the failover occurs due to the failure of the resource other than Oracle.
Oracle RAC
To operate Oracle RAC resources, control RMS userApplication without using the srvctl or shutdown command. If you execute these commands to the Oracle instance directly, PRIMECLUSETR will consider that the resource fails, and recovery processing might be initiated for the Oracle resource. To execute these commands, put userApplication into maintenance mode.
Maintenance mode of userApplication
If you put userApplication into maintenance mode, resource failure is ignored. It means that userApplication failover and resource autorecovery do not occur even if Oracle is manually stopped. This enables maintenance work of resources including Oracle resources.
For information on how to put userApplication into maintenance mode, see “5.4.11 Maintenance mode” of the “PRIMECLUSTER RMS Configuration and Administration Guide”.
Oracle instance and listener monitoring
hvoradisable and hvoraenable commands enable to discontinue and restart monitoring Oracle instances and Oracle listener resources.
If you put userApplication into maintenance mode only, Oracle session for monitoring remains. If you execute hvoradisable command additionally, the Oracle session is killed. This enables executing shutdown command with “normal” option in Oracle manual stop.
For information on how to cancel or restart monitoring the Oracle instance and listener resources, see “4.1 hvoradisable - Discontinue Monitoring Resources” and “4.2 hvoraenable - Restart Monitoring Resources”.
Note
Monitoring restart
If Oracle instances and Oracle listeners are stopped manually after resource monitoring disruption, start them manually before starting resource monitoring again. If you restart resource monitoring with the Oracle resources inactive, the Oracle resources may fail.
Resource state during monitoring
If the “hvoradisable” command properly stops monitoring the resources, they will enter Warning.
Plan the maintenance procedure according to the operation environment and the maintenance requirement. Refer to the following procedure and the Oracle document.
