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
Sample configuration for ASM disks as CVM volumes
Figure: Dependency graph for ASM on CVM volumes describes a typical service group with CVM volumes chosen for Oracle ASM.
This configuration has two service groups. The Oracle, ASMDG, and CVMVolDG resources are part of the parent failover service group oraasm_grp. The ASMInst resource belongs to the CVM service group cvm_grp, which is a parallel service group. The service groups are linked with online local firm dependency.
After the CVM volume where the database resides comes online, the ASMDG agent mounts the ASM disk group that the database requires. The virtual IP address for the service group is configured using the IP and NIC resource types. The Oracle server can be started after each of these resources come online.
Figure: Dependency graph for Oracle ASM with multiple Oracle instances on a node describes a typical service group with multiple Oracle instances which share the ASMInst resource that is part of a CVM parallel service group.
If you have multiple Oracle instances, a failover service group is configured for each Oracle instance. The Oracle service groups share a single ASM instance that is configured as part of the CVM parallel service group. The Oracle service groups are made dependent on the CVM service group using an Online Local Firm dependency. However, each database must use exclusive ASM disk groups, so that the Cluster Server agent for Oracle can fail over the disk group.