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
Action entry point for Cluster Server agent for Oracle
The Cluster Server agent for Oracle supports the Action entry point, which enables you to perform predefined actions on a resource.
To perform an action on a resource, type the following command:
# hares -action res token [-actionargs arg1 ...] \
[-sys system] [-clus cluster]You can also add custom actions for the agent.
For further information, refer to the Cluster Server Agent Developer’s Guide.
See Table: Predefined virtual fire drill actions. describes the agent's predefined virtual fire drill actions.
Table: Predefined agent actions describes the agent's predefined actions.
Table: Predefined agent actions
Action | Description |
|---|---|
VRTS_GetInstanceName | Retrieves the name of the configured instance. You can use this option for the Oracle and the Netlsnr resources. |
VRTS_GetRunningServices | Retrieves the list of processes that the agent monitors. You can use this option for the Oracle and the Netlsnr resources. |
DBRestrict | Changes the database session to enable the RESTRICTED mode. |
DBUndoRestrict | Changes the database session to disable the RESTRICTED mode. |
DBSuspend | Suspends a database. |
DBResume | Resumes a suspended database. |
DBTbspBackup | Backs up a tablespace; actionargs contains name of the tablespace to be backed up. |
Note:
VRTS_GetRunningServices, DBRestrict, DBResume, DBSuspend, DBTbspBackup, and DBUndoRestrict action entry points are not supported for Oracle PDB resources.
Table: Predefined virtual fire drill actions lists the virtual fire drill actions of the Cluster Server agent for Oracle that lets you run infrastructure checks and fix specific errors.
Table: Predefined virtual fire drill actions
Virtual fire drill action | Description |
|---|---|
getid (Oracle agent) | Verifies that the Oracle Owner exists on the node. |
home.vfd (Oracle agent) | Verifies the following:
Note: It is mandatory from Oracle 21c and later versions for a client to configure .env file path in EnvFile attribute. This file must have ORACLE_BASE path added to work on Oracle virtual firedrill feature. Sample EnvFile content with ORACLE_BASE path for Oracle 21c [root@inaqalnx013 Oracle]# cat /opt/VRTSagents/ha/bin/Oracle/envfile ORACLE_BASE="/u02/app/oracle/product/21.0.0/dbhome_1/"; export ORACLE_BASE; Sample attribute value EnvFile = "/opt/VRTSagents/ha/bin/Oracle/envfile" |
owner.vfd (Oracle agent) | Verifies the uid and gid of the Oracle Owner attribute. Checks if uid and gid of Owner attribute is the same on the node where the Oracle resource is currently ONLINE. |
pfile.vfd (Oracle agent) | Checks for the presence of pfile or spfile on the local disk. If both pfile and spfile are not present, the agent function exits. If the Oracle resource is online in the cluster, the agent function logs a message that the spfile must be on the shared storage because the Oracle resource is online. |
tnsadmin.vfd (Netlsnr agent) | Checks if listener.ora file is present. If the listener.ora file is not present, it checks if ORACLE_HOME is mounted and displays appropriate messages. |