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
Configuring the Application agent to make OHASD highly available
You can configure the Application agent to ensure the OHASD process is made highly available in the VCS cluster.
To configure the Application agent for the Ohasd process to ensure the service is online
Configure the Application agent
Application ohasd_res ( StartProgram = "<GRID_HOME>/bin/crsctl start has" StopProgram = "<GRID_HOME>/bin/crsctl stop has" PidFiles @node1 = { "<GRID_HOME>/ohasd/init/node1.pid" } PidFiles @node2 = { "<GRID_HOME>/ohasd/init/node2.pid" } )
Set up the resource dependency on the Ohasd daemon if the resource is configured:
For databases that are running in oracle restart mode
For the ASMInst resource
In the following dependency tree, ohasd resource is configured in a failover service group or parallel service group.
Run the # $GRID_HOME/bin/srvctl disable has command to disable the automatic startup of ohasd on all the nodes in the VCS cluster.
Figure: shows OHASD resource configured in Parallel service group with the ASMInst resource in the Failover service group