Cluster Server 8.0.2 Agent for Oracle Installation and Configuration Guide - Solaris
- 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
Best practices for multiple Oracle instance configurations in a VCS environment
Review some of the best practices for using multiple Oracle instances in a VCS environment:
For each SID to be configured, create UNIX accounts with DBA privileges.
Make sure that each Oracle instance has a separate disk group and is configured as a separate service group.
Define the system parameters such that the allocation of semaphore and shared memory is appropriate on all systems.
Use a dedicated set of binaries for each Oracle instance, even if each instance uses the same Oracle version.
If your configuration uses the same Oracle version for all instances, install a version on the root disk or preferably on a secondary disk. Locate the pfiles in the default location and define several listener processes to ensure clean failover.
If your configuration has different versions of Oracle, create a separate $ORACLE_HOME for each Oracle version.
Follow the Optimal Flexible Architecture (OFA) standard (/uxx/<SID>). In cluster configurations, you could adapt the standard to make it more application-specific. For example, /app/uxx/<SID>.
Listeners accompanying different versions of Oracle may not be backward-compatible. So, if you want to create a single listener.ora file, you must verify that the listener supports the other versions of Oracle in the cluster. You must also create a separate Envfile for each version of Oracle.
Make sure that each listener listens to a different virtual address. Also, assign different names to listeners and make sure that they do not listen to the same port.
The pfiles must be coordinated between systems. For the same instance of a database, ensure that the pfiles referenced are identical across the nodes.