Cluster Server 7.4.1 Agent for Oracle Installation and Configuration Guide - Linux
- 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 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
- Configuring VCS service groups for Oracle using the Veritas High Availability Configuration wizard
- Understanding service group configurations
- Understanding configuration scenarios
- Troubleshooting
- Sample configurations
- 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
- Resource type definition for the Oracle agent
- Resource type definition for the Netlsnr agent
- Resource type definition for the ASMInst agent
- Resource type definition for the ASMDG agent
- 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 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
Enabling Oracle Cluster Synchronization Service daemon to start automatically
The Oracle ASM instance resource faults if the required Oracle Cluster Synchronization Services process (occsd.bin
) is not active. To prevent the resource from faulting, modify the AUTO_START attribute of the CSSD resource (ora.cssd
). This configuration change enables the Oracle High Availability Services daemon (ohasd
) to start the ocssd.bin
process as soon as the ohasd
daemon starts on each node in the cluster.
For Oracle 11g R2 or later up to 12.1.0.1, perform the following procedure on each node of the cluster.
To enable Oracle Cluster Synchronization Service daemon to start automatically
- Set the AUTO_START attribute of the
ora.cssd
resource as follows:# $GRID_HOME/bin/crsctl modify resource ora.cssd -attr AUTO_START=always
Note:
You must perform this step on all nodes in the VCS cluster that have Oracle Grid Infrastructure installed.
For Oracle 12.1.0.2 onwards, you cannot perform this procedure, because Oracle does not let you modify ora.* resources by using the crsctl
command. The ASMInst agent now handles this task internally.