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
Zone root on shared disk for single Oracle instance
Figure: Single Oracle instance in zone on shared disk describes a typical service group in a Solaris zone that is on shared disk. If the root file system of a zone is on a shared disk, the file system should be mounted by VCS. Hence, separate DiskGroup and Volume resources are required for the zone.
In this sample configuration, Oracle Home is installed locally inside the zone and the data files of Oracle instance are stored on shared disks. The shared disk groups and volumes in the cluster are configured as resources of type DiskGroup and Volume respectively. The volumes are mounted using the Mount agent. The file system mounted by Mount agent is mounted inside the zone as LOFS mount by zone configuration. The Solaris zone is monitored through a zone resource, which is dependent on the Mount and NIC resources. The Oracle server can be started after each of these resources is brought online.