Cluster Server 7.4 Agent for Oracle Installation and Configuration Guide - Linux
- 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.4 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
- Configuring VCS service groups for Oracle using the Veritas High Availability Configuration wizard
- Typical VCS cluster configuration in a virtual environment
- About configuring application monitoring using the High Availability solution for VMware
- Getting ready to configure VCS service groups using the wizard
- Before configuring application monitoring
- Launching the High Availability Configuration wizard
- Configuring the agent to monitor Oracle
- Understanding service group configurations
- Understanding configuration scenarios
- High Availability Configuration wizard limitations
- Troubleshooting
- Sample configurations
- 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
- About the resource type and attribute definitions
- Resource type definition for the Oracle agent
- Resource type definition for the Netlsnr agent
- Resource type definition for the ASMInst agent
- Resource type definition for the ASMDG agent
- 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 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
Verifying the Oracle health check binaries and intentional offline for an instance of Oracle
This section describes the steps to verify the state of Oracle instance, the Oracle health check binaries, and intentional offline behavior for an Oracle agent.
Note:
The steps listed in the table below should be executed by the operating system user specified in Owner attribute.
Table: Oracle health check options lists the checks you can verify with Oracle health check binaries.
Table: Oracle health check options
Verify | Solution |
|---|---|
If the ORACLE_HOME variable is set. | Run the following command to verify that the $ORACLE_HOME variable is correctly set. # echo $ORACLE_HOME Set the ORACLE_HOME environment variable if it is not already set. For example, run the following command to set the ORACLE_HOME variable: # export ORACLE_HOME=/u01/oraHome where |
If the SID for the Oracle instance is set. | Run the following command to verify that the $ORACLE_SID variable is correctly set. # echo $ORACLE_SID If required, run the # export ORACLE_SID=db command to set the $ORACLE_SID variable. |
If the library path is set. | Run the following command to verify that the $LD_LIBRARY_PATH variable is correctly set. # echo $LD_LIBRARY_PATH If required, run the # export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH command to set the $LD_LIBRARY_PATH variable. |
If the Oracle instance is online. | Run the following command to verify that the Oracle health check binary reports the status correctly: # ./oraapi_<Arch>_<Oracle_FullVersion> where <Arch>_<Oracle_FullVersion> is the system architecture and the Oracle full version. For example, # ./oraapi_64_121010, where oraapi_64_121010 is a binary built for Oracle version 12 on a 64-bit system. The system displays the following message: Instance is online Run # echo $? If the system displays 110 the instance is online and active. |
If the Oracle instance is offline. | Run the following command to verify that the Oracle health check binary reports the status correctly: # ./oraapi_<Arch>_<Oracle_FullVersion> where <Arch>_<Oracle_FullVersion> is the system architecture and the Oracle full version. For example, # ./oraapi_64_121010, where oraapi_64_121010 is a binary built for Oracle version 12 on a 64-bit system. The system displays the following message: Failure: Instance Shutdown class: SOFT Proper Shutdown Run # echo $? If the system displays 100 the instance is offline. |
If the Oracle instance is abnormally terminated. | If any of the important Oracle process is killed (for example, ora_pmon_<sid>, ora_smon_<sid>), the Oracle instance is abnormally terminated. In such a case run the Oracle health check binary, and the system displays following message: For example, run # ./oraapi_64_121010 Failure: Abnormal Termination class: SOFT Abnormal termination Run # echo $? If the system displays 98 the termination of Oracle processes. The VCS resource fails over as Oracle termination was abnormal and not intentional. |