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
- 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 for Oracle 11gR2 or 12c 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
- 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
- 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 configuration for Oracle instances in Solaris zones
- 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 the clustering daemon for Oracle 10g or later
If you installed Oracle binaries for Oracle versions 10g or later on shared disks, you must disable the Oracle clustering daemon.
Warning:
If you want to use ASM feature, then do not disable the Oracle clustering daemon.
Oracle versions 10g and later provide a clustering daemon called Oracle Cluster Synchronization Service Daemon (CSSD). If the Oracle binary files are on a shared storage, the init command to start the daemon may result in an error. Because a VCS cluster for Oracle does not require this daemon, Veritas recommends you to disable the daemon.
To disable the daemon on Solaris 11
On the node from where you ran the Oracle installation wizard:
Find out the Fault Management Resource Identifier (FMRI) for the cssd daemon. Type the following from the command prompt:
# svcs | grep cssd
The FMRI for the cssd daemon is displayed.
Modify the Service Configuration Repository such that the SVC does not control the daemon. Type the following from the command prompt:
# svccfg delete -f <FMRI>
FMRI is the cssd FMRI you obtained.