Please enter search query.
Search <book_title>...
InfoScale™ 9.0 Cluster Server Agent for Oracle Installation and Configuration Guide - Solaris
Last Published:
2025-09-09
Product(s):
InfoScale & Storage Foundation (9.0)
Platform: 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
Configuring and starting up ASM on remaining nodes
This procedure is applicable when Oracle grid infrastructure is installed on all nodes and ASM is configured on the first node. See Configuring Oracle ASM on the first node of the cluster.
Configure the remaining nodes by following the procedure given below.
To create ASM and start ASM on remaining nodes
- Copy the
spfilefor ASM from the ASM Disks that is to be used on the remote node.For example:
ASMCMD> spget +DATA/asm/asmparameterfile/<registry_file>ASMCMD> spcopy +DATA/asm/asmparameterfile/<registry_file> /u01/oraHome/dbs/spfileASM.ora - Stop the database and the ASM Disk group on the first node.
- Copy the spfile from the first node to the remote node.
- Copy $ORACLE_BASE/admin/SID* from first node to the remote node.
- Add an asm instance on the remote node.
For example: $/u01/product/oracleVersion/grid/bin/srvctl add asm -p /u01/oraHome/dbs/spfileASM.ora
- Start the asm instance using the srvctl command.
- Import the VxVM disk group on the remote node.
To configure database on remaining nodes that use ASM disk-groups
- Run the srvctl add database command to register the Oracle Database(s) that is running on the nodes.
Note:
Use the credentials of the Oracle software owner to register the database. For more information on the complete list of parameters, refer to the Oracle documentation.
- Login to the Oracle ASM instance running on the remote node.
- Run the SQL> ALTER disk group <DGname> mount command to mount the Oracle ASM disk groups.
- Repeat Step 3 to mount all the required disk groups.
- Run the $GRID_HOME/bin/crsctl stat res -t -init command to check if the disk groups are auto-registered to OHASD.
The output displays ora.<DGname>.dg for the registered disk groups.
- Run the $GRID_HOME/bin/srvctl modify database -a <diskgroup_list> command to add the Oracle ASM disk groups as a dependency to the database(s).