Please enter search query.
Search <book_title>...
InfoScale™ 9.0 Agent for Oracle Installation and Configuration Guide - AIX
Last Published:
2025-04-14
Product(s):
InfoScale & Storage Foundation (9.0)
Platform: AIX
- Introducing the Cluster Server agent for Oracle
- How the agent makes Oracle highly available
- About Cluster Server agent functions for Oracle
- Oracle agent functions
- How the Oracle agent supports health check monitoring
- ASMInst agent functions
- Oracle agent functions
- Installing and configuring Oracle
- 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
- Installing Oracle binaries on the first node of the cluster
- Installing and removing the agent for Oracle
- Configuring VCS service groups 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
- Verifying the Oracle health check binaries and intentional offline for an instance of Oracle
- Appendix A. Resource type definitions
- Appendix B. Sample configurations
- 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
- Appendix C. Best practices
- Appendix D. Using the SPFILE in a VCS cluster for Oracle
- Appendix E. OHASD in a single instance database environment
Disabling automatic startup of ASM
When the ocssd.bin
process starts, it automatically starts up the ASM instance. This could cause concurrency violation issues if the ASMInst resource is configured as a part of failover service group in the following scenario. Suppose a node goes down or restarts for some reason, all the resources on this node comes online on the second node. After the reboot, the ohasd
process automatically starts the ocssd.bin
process. This automatically starts the ASM instance on node1, which leads to concurrency violation. To resolve this issue, Arctera recommends you to disable automatic startup of ASM.
Run the following command on each node of the cluster:
# $GRID_HOME/bin/srvctl disable asm