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
Typical Oracle configuration in a VCS cluster
A typical Oracle configuration in a VCS cluster has the following characteristics:
VCS is configured in a two-node cluster.
The Oracle data is installed on shared storage.
The Oracle binaries are installed locally on both nodes or on shared disks.
If you use Oracle ASM feature, then the characteristics are as follows:
The Oracle binaries are installed locally on both the nodes.
The database files are installed on the ASM disk groups.
Review the typical cluster setup illustration for ASM-managed database.
See Figure: Oracle binaries on local disk and Oracle data on shared disk.
The Cluster Server agent for Oracle is installed on both nodes.
For ASM, ASMInst and ASMDG agents are installed on both nodes.
Figure: Oracle binaries and data on shared disks depicts a configuration where Oracle binaries and data are installed completely on shared disks.
Figure: Oracle binaries on local disk and Oracle data on shared disk depicts a configuration where Oracle binaries are installed locally on each node and Oracle data is installed on shared disks.