Cluster Server 7.3.1 Agent for Oracle Installation and Configuration Guide - Solaris
- Introducing the Cluster Server agent for Oracle
- About the Cluster Server agent for Oracle
- How the agent makes Oracle highly available
- About Cluster Server agent functions for Oracle
- Oracle agent functions
- How the Oracle agent supports health check monitoring
- ASMInst agent functions
- Oracle agent functions
- Installing and configuring Oracle
- About VCS requirements for installing Oracle
- About Oracle installation tasks for VCS
- Installing ASM binaries for Oracle 11gR2 or 12c in a VCS environment
- Configuring Oracle ASM on the first node of the cluster
- Installing Oracle binaries on the first node of the cluster
- Installing and removing the agent for Oracle
- Configuring VCS service groups for Oracle
- Configuring Oracle instances in VCS
- Before you configure the VCS service group for Oracle
- Configuring the VCS service group for Oracle
- Setting up detail monitoring for VCS agents for Oracle
- Enabling and disabling intelligent resource monitoring for agents manually
- Administering VCS service groups for Oracle
- Pluggable database (PDB) migration
- Troubleshooting Cluster Server agent for Oracle
- Verifying the Oracle health check binaries and intentional offline for an instance of Oracle
- Appendix A. Resource type definitions
- Appendix B. Sample configurations
- Sample single Oracle instance configuration
- Sample multiple Oracle instances (single listener) configuration
- Sample multiple instance (multiple listeners) configuration
- Sample Oracle configuration with shared server support
- Sample configuration for Oracle instances in Solaris zones
- Sample Oracle ASM configurations
- Appendix C. Best practices
- Appendix D. Using the SPFILE in a VCS cluster for Oracle
- Appendix E. OHASD in a single instance database environment
Disabling the Cluster Server agent for Oracle
To disable the Cluster Server agent for Oracle, you must change the Oracle service group to an OFFLINE state. You can stop the application completely or switch the agent to another system.
To disable the agent
- To remove a system from the service group's SystemList, check if the service group is online:
# hagrp -state service_group -sys system_name
If the service group is online, take it offline. Use one of the following commands:
To take the service group offline on one node and online it on another node, you can use the -switch option:
# hagrp -switch service_group -to system_name
To take the service group offline without bringing it online on any other node in the cluster, enter:
# hagrp -offline service_group -sys system_name
- Stop the agent on the node:
# haagent -stop Oracle -sys system_name
When you get the message "Please look for messages in the log file," check the file /var/VRTSvcs/log/engine_A.log for a message confirming the agent has stopped.
You can also use the ps command to confirm the agent is stopped.
- You can now remove the service group, the resource type, or both from the VCS configuration after disabling the agent on all nodes.
See the Cluster Server Administrator’s Guide for more information.