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
- Supported software for VCS agent for Oracle
- Changes introduced in the 7.3.1 release
- How the agent makes Oracle highly available
- About Cluster Server agent functions for Oracle
- Oracle agent functions
- Startup and shutdown options for the Oracle agent
- Startup and shutdown options for the pluggable database (PDB)
- Recommended startup modes for pluggable database (PDB) based on container database (CDB) startup modes
- Monitor options for the Oracle agent in traditional database and container database
- Monitor for the pluggable database
- How the agent handles Oracle error codes during detail monitoring
- Info entry point for Cluster Server agent for Oracle
- Action entry point for Cluster Server agent for Oracle
- How the Oracle agent supports health check monitoring
- Netlsnr agent functions
- ASMInst agent functions
- ASMDG agent functions
- Oracle agent functions
- Typical Oracle configuration in a VCS cluster
- About setting up Oracle in a VCS cluster
- Installing and configuring Oracle
- About installing Oracle in a VCS environment
- Before you install Oracle in a VCS environment
- 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
- Configuring and starting up ASM on remaining nodes for 11gR2 or 12c
- Installing Oracle binaries on the first node of the cluster
- Configuring the Oracle database
- Copying the $ORACLE_BASE/admin/SID directory
- Copying the Oracle ASM initialization parameter file
- Verifying access to the Oracle database
- Installing and removing the agent for Oracle
- Configuring VCS service groups for Oracle
- About configuring a service group 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
- About troubleshooting Cluster Server agent for Oracle
- Error messages common to the Oracle and Netlsnr agents
- Error messages specific to the Oracle agent
- Error messages specific to the Netlsnr agent
- Error messages specific to the ASMInst agent
- Error messages specific to the ASMDG agent
- Troubleshooting issues specific to Oracle in a VCS environment
- Verifying the Oracle health check binaries and intentional offline for an instance of Oracle
- Disabling IMF for a PDB resource
- Appendix A. Resource type definitions
- Appendix B. Sample configurations
- About the sample configurations for Oracle enterprise agent
- 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
- Zone root on local disk for single Oracle instance
- Zone root on shared disk for single Oracle instance
- Zone root on local disk for multiple Oracle instances
- Zone root on shared disk for multiple Oracle instances
- Zone root on local disk for Oracle instance with shared server support
- Zone root on shared disk for Oracle instance with shared server support
- Oracle instance in the context of project
- Sample VCS configuration file for zone root on local disk or on shared disk
- Sample Oracle ASM configurations
- Sample configuration of Oracle pluggable database (PDB) resource in main.cf
- Sample configuration of migratable Oracle pluggable database (PDB) resource in main.cf
- Sample Configuration of Oracle supported by systemD
- Sample configuration of ASMInst supported by systemD
- Appendix C. Best practices
- Appendix D. Using the SPFILE in a VCS cluster for Oracle
- Appendix E. OHASD in a single instance database environment
Location of the $ORACLE_HOME
You can place the Oracle home directory ($ORACLE_HOME), which contains the Oracle binaries and configuration files, locally on each server's disk. Alternatively, you can place the Oracle home directory on the shared storage. The correct location for Oracle binaries depends on your environment. The following points discuss the advantages of each approach.
$ORACLE_HOME directory on shared disks | You can install the Oracle Database Server ($ORACLE_HOME) on shared disks. Each node in the cluster must have the same mount point directory for the shared file system. Placing the Oracle binaries on shared storage simplifies setting up a given node in a cluster to run an instance. Each database service group is self-contained. An instance can be moved to a new node in the cluster that shares the storage. For example, in a cluster with four nodes, you can have three database instances or service groups, each at a different Oracle version. If the Oracle binaries are placed on shared storage, three copies of Oracle, that is, one per version are required on shared storage. By contrast, placing the Oracle binaries on local storage, would require as many as 12 copies of the binaries (three versions on four nodes). The disadvantage of this approach is that a rolling upgrade of Oracle binaries on shared storage is not possible. |
$ORACLE_HOME directory on local disks | You can install the Oracle Database Server ($ORACLE_HOME) on the local disk. The advantage is that you can upgrade the Oracle database binaries on an offline node while the database server runs on another node. The database server can later be switched to the upgraded node (provided the database is compatible), permitting a minimum amount of downtime. The disadvantage of this approach is that with a large number of nodes, it becomes difficult to maintain the various Oracle installations. |
If you want to use Oracle ASM, then you must place the Oracle home directory only on the local disks of each node. You can install Oracle ASM on the same Oracle home as Oracle Database, or you can install Oracle ASM on a different Oracle home directory.
See Oracle documentation.