Top
PRIMECLUSTER Wizard for Oracle 4.2 Configuration and Administration Guide

4.2 hvoraenable - Restart Monitoring Resources

User

Super user

Format

/opt/FJSVclora/sbin/hvoraenable userApplication Resource
/opt/FJSVclora/sbin/hvoraenable -a [ userApplication ]

Function

hvoraenable restarts monitoring the Oracle instance and Oracle listener resources on the local node where resource monitoring is disrupted. It is available regardless of whether userApplication is activated or deactivated.
If the command is executed while userApplication is stopped, disabling resource monitoring with hvoradisable will be cancelled. .
If the command is executed while userApplication is running, it will restart resource monitoring.
The command must be executed after the Oracle instance and Oracle listener are started manually. Be sure to check the resource state is changed from Warning to Online.

Information

The ASM instance resource and Oracle Clusterware resource are not monitored, so it is not necessary to cancel resource monitoring with the command. For further details about ASM instance resources, see “2.4.2 ASM (Automatic Storage Management)”.

Parameter
userApplication Resource

Specify userApplication including Oracle resources that will be disrupted monitoring.
Specify either of the Oracle instance or Oracle listener that will be disrupted monitoring.
userApplication and Resource that are specified as parameters should exist on the local node.

-a [ userApplication ]

The option restarts monitoring all Oracle instance and listener resources that belong to userApplication that is running on a local node and is specified for userApplication.
If userApplication is omitted, the option will restart monitoring all the Oracle resources on the local node.

Exit status

0: Normal termination
Non-0: Abnormal termination
2: Abnormal termination (disruption of resource monitoring with the -a option fails)

Note

Note that execution timing. Unexpected resource failure or userApplication failover might be caused.

  • Do not execute the command while state transition of userApplication is in progress.

  • Do not operate userApplications right after execution of the command. (At least a five-seconds interval is necessary.)