InfoScale™ 9.0 Agent for Oracle Installation and Configuration Guide - AIX
- 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
- 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
- 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
Upgrading the VCS agent for Oracle
The agent binaries for Cluster Server agent for Oracle are part of VRTSvcsea fileset. The VRTSvcsea fileset is already upgraded if you chose to upgrade to VCS 9.0 on a cluster which has a previous version of Cluster Server agent for Oracle installed.
Before you upgrade the agent, make sure you meet the prerequisites to upgrade the Cluster Server agent for Oracle.
Warning:
The agent fileset VRTSvcsea includes the VCS agents for Oracle, Sybase, and DB2. So, the procedure to upgrade the VCS agent for Oracle upgrades all the other agents also. Make sure that you have also met the upgrade prerequisites for the other agents that are part of the VRTSvcsea fileset.
To upgrade VCS agent for Oracle
- Save the VCS configuration and stop the VCS engine.
# haconf -dump -makero # hastop -all -force
On all nodes on which the Oracle agent was installed, do the following:
Remove the earlier version of the VCS agent for Oracle.
For VCS 5.1, 5.1SP1, 5.1SP1RP1, 6.0, 6.0.1, 6.0.3:
# installp -u VRTSvcsea
For VCS 5.0 or 5.0MP3:
# installp -u VRTSvcsor.rte
For VCS 5.0 or 5.0MP3:
You must also remove the VRTScsocw fileset.
# installp -u VRTScsocw.rte
Delete the file /etc/VRTSvcs/conf/config/OracleTypes.cf.
Install the latest VCS agent for Oracle.
- Make sure that you have copied the OracleTypes.cf file from the /etc/VRTSagents/ha/conf/Oracle directory to /etc/VRTSvcs/conf/config directory.
Make sure to update the newly copied OracleTypes.cf file with all the type-level changes that you had made to the older OracleTypes.cf file.
For example, if you had changed the value of the MonitorInterval attribute from the default 60 to 120 seconds, the OracleTypes.cf file gets updated. You must apply these type-level changes manually to the newly copied OracleTypes.cf file.
- If you use ASM for database storage, then make sure that you have copied the file OracleASMTypes.cf from the directory /etc/VRTSagents/ha/conf/OracleASM to /etc/VRTSvcs/conf/config directory.
Make sure to update the newly copied OracleASMTypes.cf file with all the type-level changes that you had made to the older OracleASMTypes.cf file.
- If you had enabled detail monitoring for the Oracle agent in the previous version, set the value of the LevelTwoMonitorFreq attribute.
- From a node in the cluster, edit your configuration file /etc/VRTSvcs/conf/config/main.cf.
Replace all resources of type Sqlnet with resources of type Netlsnr.
- Verify the configuration.
# hacf -verify config
- Start VCS on local node first.
- Start VCS on other nodes.