Cluster Server 7.2 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
Startup and shutdown options for the Oracle agent
You can specify Startup and Shutdown options for the Oracle instances that are configured.
Table: Startup options for traditional database and container database lists the startup options that the agent supports for traditional database and container database.
Table: Startup options for traditional database and container database
Option | Description |
---|---|
STARTUP_FORCE (Default) | Runs the command startup force pfile='location_of_pfile' if the pfile is configured. If the pfile is not configured, the agent runs startup force. It picks up the default parameter files from their default locations. |
STARTUP | Runs the command startup pfile='pfile_name_with_absolute _path' if the pfile is configured. For example: startup pfile = '</dbs/pfilename>' If the pfile is not configured, the agent runs startup without pfile. |
RESTRICTED | Starts the database in the RESTRICTED mode. |
RECOVERDB | Performs a database recovery on instance startup. |
CUSTOM | Uses a predefined SQL script (start_custom_$SID.sql) and runs custom startup options. The script must be in the /opt/VRTSagents/ha/bin/Oracle directory and must have access to the Oracle Owner OS user. If the file is not present, the agent logs an error message. With a custom script, the agent takes the following action: sqlplus /nolog <<! connect / as sysdba; @start_custom_$SID.sql exit; ! |
SRVCTLSTART |
Uses the srvctl utility to start an instance of the database. For RAC clusters, you must manually set the default startup option as SRVCTLSTART. Note: This is applicable only when an Oracle grid infrastructure is configured. |
SRVCTLSTART_RO | Uses the srvctl utility to start an instance of the database with the Note: This is applicable only when an Oracle grid infrastructure is configured. |
Table: Shutdown options for traditional database and container database lists the shutdown options that the agent supports for traditional database and container database.
Table: Shutdown options for traditional database and container database
Option | Description |
---|---|
IMMEDIATE (Default) | Shuts down the Oracle instance by running shutdown immediate. |
TRANSACTIONAL | Runs the shutdown transactional command. This option is valid only for the database versions that support this option. |
CUSTOM | Uses a predefined SQL script (shut_custom_$SID.sql) and runs custom shutdown options. The script must be in the /opt/VRTSagents/ha/bin/Oracle directory and must have access to the Oracle Owner OS user. If the file is not present, the agent shuts the agent down with the default option. |
SRVCTLSTOP |
Uses the srvctl utility to stop an instance of the database. For RAC clusters, you must manually set the default option as SRVCTLSTOP. Note: This is applicable only when an Oracle grid infrastructure is configured. |
SRVCTLSTOP_TRANSACT | Uses the srvctl utility to stop an instance of the database with the Note: This is applicable only when an Oracle grid infrastructure is configured. |
SRVCTLSTOP_ABORT | Uses the srvctl utility to stop an instance of the database with the Note: This is applicable only when an Oracle grid infrastructure is configured. |
SRVCTLSTOP_IMMEDIATE | Uses the srvctl utility to stop an instance of the database with the |