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
Administering the AMF kernel driver
Review the following procedures to start, stop, or unload the AMF kernel driver.
To start the AMF kernel driver
- Set the value of the AMF_START variable to 1 in the following file, if the value is not already 1:# /etc/default/amf 
- Start the AMF kernel driver. Run the following command:# svcadm enable amf 
To stop the AMF kernel driver
- Set the value of the AMF_STOP variable to 1 in the following file, if the value is not already 1:# /etc/default/amf 
- Stop the AMF kernel driver. Run the following command:# svcadm disable amf 
To unload the AMF kernel driver
- If agent downtime is not a concern, use the following steps to unload the AMF kernel driver: - Stop the agents that are registered with the AMF kernel driver. - The amfstat command output lists the agents that are registered with AMF under the Registered Reapers section. - See the amfstat manual page. 
- On Solaris 11, set the value of the AMF_DISABLE variable to 1 in the following file (before stopping the AMF kernel driver): - # /etc/default/amf - Note: - Reset the AMF_DISABLE variable in the /etc/default/amf file before starting AMF kernel driver. 
- Stop the AMF kernel driver. 
- Start the agents. 
 
- If you want minimum downtime of the agents, use the following steps to unload the AMF kernel driver: - Run the following command to disable the AMF driver even if agents are still registered with it. - # amfconfig -Uof 
- On Solaris 11, set the value of the AMF_DISABLE variable to 1 in the following file (before stopping the AMF kernel driver): - # /etc/default/amf - Note: - Reset the AMF_DISABLE variable in the /etc/default/amf file before starting AMF kernel driver. 
- Stop the AMF kernel driver.