Please enter search query.
Search <book_title>...
Cluster Server 8.0.2 Agent for Oracle Installation and Configuration Guide - Solaris
Last Published:
2024-01-09
Product(s):
InfoScale & Storage Foundation (8.0.2)
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
Failing over Oracle after a VCS node failure during hot backup
If a node fails during a hot backup, VCS can succeed with a node failover only if you meet VCS requirements for Oracle hot backup.
See About VCS requirements for installing Oracle.
If you do not meet VCS requirements, the agent cannot open the database in the backup mode on the failover node. Therefore, VCS cannot online the Oracle group on the failover node. You may encounter the following Oracle errors in this situation:
$ ORA-1110 "data file %s: '%s'"
or
$ ORA-1113 "file %s needs media recovery"
In such cases, you must manually end the hot backup and then fail over Oracle to another node.
To manually fail over Oracle after a node failure that occurs during hot backup
- Take the datafiles in the database out of the backup mode.
Refer to the Oracle documentation for instructions on how to change the state of the database files.
- Shut down the database.
- Bring the Oracle service group online on the failover node.
The agent can now start the Oracle instance, mount the database, and open the datafiles.