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
Building the Oracle agent executable using the build_oraapi.sh script
To build the Oracle agent executable using the build_oraapi.sh script:
- Log in as root user on the node.
- Set the Oracle home directory path.
# export ORACLE_HOME=/u01/oraHome
where, /u01/oraHome is the Oracle home directory that stores files.
- Access the Oracle agent directory.
# cd /opt/VRTSagents/ha/bin/Oracle
- Run the following command from the Oracle agent directory.
# ./build_oraapi.sh -version <version>
where version is the Oracle database version on the node.
- Alternatively, if you did not set the ORACLE_HOME variable, you can set the oracle_home parameter as a command line option.
#./build_oraapi.sh -version <version> -oracle_home /u01/oraHome
where version is the Oracle database version on the node and /u01/oraHome is the Oracle home directory path, which is set as the ORACLE_HOME variable value.
The script generates binaries under agent directory /opt/VRTSagents/ha/bin/Oracle. Oracle health check binaries generated on a node is based on the system architecture (32 bit or 64 bit) available on that node, and the full Oracle version.
For example, oraapi_64_121010 is a binary created with Oracle version 12 on a 64-bit system.
See Verifying the Oracle health check binaries and intentional offline for an instance of Oracle .