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, or 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 or stop monitoring
Put userApplication into maintenance mode or stop monitoring the Oracle instance and listener resources by executing the “hvoradisable” command. This will prevent resource failures when Oracle is stopped manually.
Before going on to the next step, be sure to check that userApplication is put into maintenance mode or resource monitoring is disrupted.
Stop Oracle-dependent resources
Before stopping Oracle, stop Oracle-dependent resources manually if there are any. If userApplication is in maintenance mode, stop them manually. If resource monitoring is disrupted with the “hvoradisable” command, stop monitoring the Oracle-dependent resources using the RMS command hvdisable then stop them manually.
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 before canceling maintenance mode or start resource monitoring again. If userApplication is in maintenance mode, start them manually. If resource monitoring is disrupted with the “hvoradisable” command, start monitoring the Oracle-dependent resources again using the RMS command hvdisable, then start them manually.
Restart resource monitoring or cancel maintenance mode
Restart monitoring the Oracle instance and listener resources again using the hvoraenable command or cancel maintenance mode of userApplication.
Information
Maintenance mode and resource monitoring
To stop Oracle with userApplication active, use “Maintenance mode” of PRIMECLUSTER or the “monitoring disruption” function of PRIMECLUSTER Wizard for Oracle.
“Maintenance mode” - Stop monitoring all resources registered in userApplication so that users can perform maintenance of all the resources including Oracle.
“Monitoring disruption” - Stop the Oracle resource monitoring only. If non-Oracle resource fails, a failover will be generated.
Oracle RAC 10g or later
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
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
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 will fail.
State transition during maintenance
If Oracle monitoring is stopped with the “hvoradisable” command, the Oracle resources will fail, or the state transition will not occur even though the resources are stopped manually. However, the state transition might occur due to other reasons then Oracle.
Resource state during monitoring
If the “hvoradisable” command properly stops monitoring the resources, they will enter Warning.
