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
Verifying access to the Oracle database
You can verify access to the database by running an SQL query. Depending on the location of your $ORACLE_HOME, perform one of the following procedures.
Upon completion, the Oracle database is started from the node in the cluster that you last performed this procedure.
To verify access to the Oracle database
- Depending on the location of your $ORACLE_HOME, perform one of the following procedures:
For $ORACLE_HOME on shared disks, start the Oracle database.
Verify that you can access the shared database from each node. Perform the steps from each node that would be a part of the Oracle cluster.
To start the Oracle database (for $ORACLE_HOME on shared disks)
If the Oracle binaries are mounted on any other node, unmount it.
If the data files on shared disk are mounted on any node, unmount it.
Mount the Oracle binaries and data files.
Start the database.
For $ORACLE_HOME on local disks, start the Oracle database.
Verify that you can access the database individually on each node that would be a part of the Oracle cluster.
To start the Oracle database (for $ORACLE_HOME on local disks)
Make sure you have installed Oracle binaries on the node.
If the data files on shared disk are mounted on any node, unmount it.
Mount the data files.
Start the database.
For ASM, the $ORACLE_HOME is on local disks and the database is configured on ASM disk groups.
Start the ASM-managed Oracle database.
Verify that you can access the database individually on each node that would be a part of the Oracle cluster.
To start the Oracle database (for $ORACLE_HOME on local disks)
Make sure you have installed Oracle binaries on the node.
If you use VxVM disks as ASM disks, do the following:
If the ASM disk groups are mounted on any node, do the following:
Unmount the ASM disk groups from the ASM instance.
Stop the ASM instance.
Stop the VxVM volumes.
Deport the VxVM disk groups.
Import the VxVM disk groups on this node and start the volumes.
Start the ASM instance.
Mount the ASM disk groups.
If you use CVM volumes for ASM, do the following:
Unmount the ASM disk group from the ASM instance on the node where the disk group is mounted.
Mount the ASM disk groups on the other node.
If you use raw disks as ASM disks, do the following:
If the ASM disk groups are mounted on any node, unmount it.
If the ASM instance is not running on this node, then start the ASM instance.
Mount the ASM disk groups.
Start the database.