InfoScale™ 9.0 Agent for Oracle Installation and Configuration Guide - Solaris
- Introducing 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 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
- 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 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
Considerations for running build_oraapi.sh
Run the
build_oraapi.sh
script on each node of the cluster where you want to use Oracle health monitoring.Run the
build_oraapi.sh
script inside each local container (Solaris zone) where you want to use Oracle health monitoring.You need to run the
build_oraapi.sh
script to relink the Oracle libraries whenever the Oracle database version is upgraded on a node.The Oracle health check binaries generated in the Oracle agent directory correspond to the ORACLE_HOME directory and the Oracle database version that are specified while executing the
build_oraapi.sh
script. ORACLE_HOME can be set as an environment variable or specified as a command line option. The Oracle database version can be specified as a command line option with thebuild_oraapi.sh
script.Arctera ships the
build_oraapi.sh
script instead of the pre-built Oracle health check binaries (oraapi_32
,oraapi_3211g
,oraapi_64
, andoraapi_6411g
).To enable health check support in Oracle agent, you must run the
build_oraapi.sh
script to build the Oracle health check binaries based on Oracle version.