Cluster Server 8.0.2 Agent for Oracle Installation and Configuration Guide - Linux
- Introducing the Cluster Server agent for Oracle
- About the Cluster Server agent for Oracle
- About the agent for Oracle ASM
- Supported software for VCS agent for Oracle
- 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
- Monitor options for the Oracle agent in traditional database and container database
- Startup and shutdown options for the pluggable database (PDB)
- Monitor for the pluggable database
- Recommended startup modes for pluggable database (PDB) based on container database (CDB) startup modes
- 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 in a VCS environment
- Configuring Oracle ASM on the first node of the cluster
- Configuring and starting up ASM on remaining nodes
- 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
- 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 Veritas High Availability solution for VMware
- Getting ready to configure VCS service groups using the wizard
- Before configuring application monitoring
- Launching the Veritas High Availability Configuration wizard
- Configuring the agent to monitor Oracle
- Understanding service group configurations
- Understanding configuration scenarios
- Veritas 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
Enabling and disabling intelligent resource monitoring for agents manually
Review the following procedures to enable or disable intelligent resource monitoring manually. The intelligent resource monitoring feature is enabled by default. The IMF resource type attribute determines whether an IMF-aware agent must perform intelligent resource monitoring.
See How the Oracle and Netlsnr agents support intelligent resource monitoring.
To enable intelligent resource monitoring
- Make the VCS configuration writable.
# haconf -makerw
Run the following command to enable intelligent resource monitoring.
To enable intelligent monitoring of offline resources:
# hatype -modify resource_type IMF -update Mode 1
To enable intelligent monitoring of online resources:
# hatype -modify resource_type IMF -update Mode 2
To enable intelligent monitoring of both online and offline resources:
# hatype -modify resource_type IMF -update Mode 3
- If required, change the values of the MonitorFreq key and the RegisterRetryLimit key of the IMF attribute.
- Save the VCS configuration.
# haconf -dump -makero
- Make sure that the AMF kernel driver is configured on all nodes in the cluster.
/opt/VRTSamf/bin/amf status
If the AMF kernel driver is configured, the output resembles:
AMF: Module loaded and configured
Configure the AMF driver if the command output returns that the AMF driver is not loaded or not configured.
- Restart the agent. Run the following commands on each node.
# haagent -stop agent_name -force -sys sys_name # haagent -start agent_name -sys sys_name
To disable intelligent resource monitoring
- Make the VCS configuration writable.
# haconf -makerw
- To disable intelligent resource monitoring for all the resources of a certain type, run the following command:
# hatype -modify resource_type IMF -update Mode 0
- To disable intelligent resource monitoring for a specific resource, run the following command:
# hares -override resource_name IMF # hares -modify resource_name IMF -update Mode 0
- Save the VCS configuration.
# haconf -dump -makero
Note:
VCS provides haimfconfig script to enable or disable the IMF functionality for agents. You can use the script with VCS in running or stopped state. Use the script to enable or disable IMF for the IMF-aware bundled agents, enterprise agents, and custom agents.