InfoScale™ 9.0 Agent for Oracle Installation and Configuration Guide - Linux
- 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
- 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
- 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
Customizing the Oracle service unit file with systemD attributes
As the vcs-<oracl_res>.service
unit file is overwritten when the online entry point is invoked, Veritas does not recommend you to modify or add new systemD attributes to the existing vcs-<oracl_res>.service
unit file. If you want to customize more systemD attributes to the vcs-<oracl_res>.service
file, create a file /etc/systemd/system/vcs-oracl_res.service.d/foo.conf
with new attributes. When the online entry point is invoked, systemD applies the new attributes from the foo.conf
file to the vcs-<oracl_res>.service
unit file and starts the application's unit service file.
- After you add the required system attributes in the foo.conf unit configuration file, ensure to load the systemd daemon.
# systemctl --system daemon-reload
- Check the status of the Oracle application service.
# systemctl status -l vcs-<oracl_res>.service
For more information, refer to the following pages.
systemd.unit (5) manual page