Super user
/opt/FJSVclora/sbin/hvoradisable userApplication Resource
/opt/FJSVclora/sbin/hvoradisable -a [userApplication ]
hvoradisable discontinues monitoring the Oracle instance and Oracle listener resources on the local node where the command is executed. The command is used to stop the Oracle instances or Oracle listeners for maintenance. Also, it is available regardless of whether userApplication is activated or deactivated.
If the command is executed while userApplication is stopped, and then it is started, the Oracle resources will enter Warning without being started.
If the command is executed while userApplication is running, it will disable resource monitoring. The Oracle resources will enter Warning. Even though the Oracle instance and Oracle listener are stopped, they will remain Warning. When you execute the command while userApplication is running, be sure to check the resource state is Warning the stop the Oracle instance and Oracle listener.
Stopping userApplication will automatically cancel resource monitoring.
Information
The ASM instance resource and Oracle Clusterware resource are not monitored, so it is not necessary to discontinue monitoring the resource with the command. For further details about ASM instance resources, see “2.4.2 ASM (Automatic Storage Management)”.
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.
The option discontinues 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 discontinue monitoring all the Oracle resources on the local node.
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 execute the command while RMS is not running.
Do not operate userApplications right after execution of the command. (At least a five-seconds interval is necessary.)
