InfoScale™ 9.0 Cluster Server 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
Installing ASM binaries in a VCS environment
Perform the following procedure if want to configure Oracle ASM instances for high availability.
Note:
If you want to use Oracle ASM feature, do not disable the Cluster Synchronization Services.
To install ASM binaries for Oracle for VCS
- Run the Oracle installer as an Oracle user.
- In the Select Installation Option dialog box, choose the Install Grid Infrastructure Software Only option and click Next.
- Follow the wizard instructions and select other options.
- In the Specify Installation Location dialog box, specify a location on the local disk for both Oracle base and Software location.
- Follow the wizard instructions and select other options
- In the Summary dialog box, review your selections. Click Back to make changes. Otherwise click Finish.
- The installer prompts whether you want to instantiate a standalone version of the software or a cluster version of the software. Choose the version that you want to install.
Instantiate a standalone version
Note:
If you choose this option, you must execute
roothas.pl. This option creates a configuration named Oracle Restart, which is used on standalone servers and not on RAC clusters. Therefore, you must perform this installation on all nodes in the VCS cluster that are used as failover destinations for Oracle Grid Infrastructure and Oracle ASM.This option requires you to install the Oracle Grid Infrastructure software locally on every node. You must not use the same set of binaries on more than one node because the same CSSD daemon (used in a particular configuration) cannot be run on nodes with different host names, requiring you to reconfigure the daemon each time it fails over or is used on another node.
In the Oracle Restart configuration the newly created database instance and netlsnr resources automatically get registered to the Oracle Grid Infrastructure. In VCS, these resources are configured as part of failover service group.
If the database and netlsnr resources accidentally go offline, Oracle Grid Infrastructure tries to restart the resources. However, VCS tries to online these resources on another node within the failover service group. This behavior causes concurrency violation.
To avoid concurrency violation perform one of the following:
In the Oracle Grid Infrastructure, set the auto_start attribute of each database and netlistner resource to 0.
In VCS, set the RestartLimit attribute value of each database and netlistner resource to the corresponding value set for these resources in the RESTART_ATTEMPTS attribute in Oracle Grid Infrastructure. For detailed description on configuring VCS to support the Oracle retsart funtion refer to
Don't instantiate a standalone version
Choose this option to instantiate a cluster version of the software. This is required for a RAC database.
- Click Next after the installation is complete.
- In the End of Installation dialog box, click Exit.
- Proceed to configure ASM disk group on shared disks using the asmca utility.