Cluster Server 7.3.1 Agent for Oracle Installation and Configuration Guide - Solaris
- 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.3.1 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
- 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 configuration for Oracle instances in Solaris zones
- Zone root on local disk for single Oracle instance
- Zone root on shared disk for single Oracle instance
- Zone root on local disk for multiple Oracle instances
- Zone root on shared disk for multiple Oracle instances
- Zone root on local disk for Oracle instance with shared server support
- Zone root on shared disk for Oracle instance with shared server support
- Oracle instance in the context of project
- Sample VCS configuration file for zone root on local disk or on shared disk
- 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
Encrypting Oracle database user and listener passwords
VCS provides a utility to encrypt database user passwords and listener passwords. You must encrypt the Pword attribute in the Oracle agent and the LsnrPwd attribute in the Netlsnr agent before you configure these attributes.
See the vcsencrypt manual page.
The vcsencrypt utility also allows you to encrypt the agent passwords using a security key. The security key supports AES (Advanced Encryption Standard) encryption which creates a more secure password for the agent.
See the Cluster Server Administrator’s Guide for more information.
Note:
You need not encrypt passwords if you use the VCS Cluster Manager (Java Console) to configure attributes.
The user passwords that are used for detail monitoring of the Oracle database are encrypted. The listener password that is considered for querying the status of the listener and stopping the listener is also encrypted.
Oracle provides the option of storing the listener password in the listener.ora file, in both clear text and encrypted formats. Irrespective of the format in which the password is stored in Oracle, you must encrypt the password using the vcsencrypt utility before you configure the LsnrPwd attribute.
If you encrypted the listener password using the Oracle lsnrctl utility, do the following depending on the Oracle version you use:
Pass the clear text password to the vcsencrypt utility.
For example, if the listener password is "oracle" pass this clear text password to the vcsencrypt utility as follows:
# vcsencrypt -agent oracle
The vcsencrypt utility displays the encrypted password. For example: bnqPdnCneNnnG
The vcsencrypt utility also allows you to encrypt the agent passwords using a security key. The security key supports AES (Advanced Encryption Standard) encryption which creates a secure password for the agent. See the Cluster Server Administrator's Guide for more information.