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
Attribute definition for the Oracle agent
Review the description of the Oracle agent attributes. The agent attributes are classified as required, optional, and internal.
Table: Required attributes for Oracle agent lists the required attributes. You must assign values to the required attributes.
Table: Required attributes for Oracle agent
Required attributes | Type and dimension | Definition |
---|---|---|
Sid | string-scalar | The variable $ORACLE_SID that represents the Oracle instance. The Sid is considered case-sensitive by the Oracle agent and by the Oracle database server. For a policy managed database, the Sid attribute should be set to Sid prefix. |
Owner | string-scalar | The Oracle user who has privileges to start or stop the database instance. The agent also supports LDAP users as Oracle user. |
Home | string-scalar | The $ORACLE_HOME path to Oracle binaries and configuration files. For example, you could specify the path as /opt/ora_home. Note: Do not append a slash (/) at the end of the path. |
Table: Optional attributes for Oracle agent lists the optional attributes for Oracle agent. You can configure the optional attributes if necessary.
Table: Optional attributes for Oracle agent
Optional Attributes | Type and Dimension | Definition |
---|---|---|
ContainerOpts | static-assoc-int | This resource-type level attribute specifies the container options for the Oracle instances that run in the context of Solaris containers (zones or projects). The values for the following keys are only effective when you set the ContainerInfo service group attribute. recommends that you do not change the following values.
See the Cluster Server Administrator's Guide and the Veritas InfoScale 7.3.1 Virtualization Guide. |
DBAUser | string-scalar | The database user who has sysdba privileges to start or stop the database. |
DBAPword | string-scalar | Encrypted password for DBAUser. Encrypt passwords only when entering them using the command-line. Passwords must be encrypted using the VCS Encrypt Utility ( |
StartUpOpt | string-scalar | Startup options for the Oracle instance. This attribute can take the following values for traditional database and container database:
Default is STARTUP_FORCE. Startup options for the Oracle instance in pluggable database. This attribute can take the following values:
|
ShutDownOpt | string-scalar | Shut down options for the Oracle instance. This attribute can take the following values for traditional database and container database:
Default is IMMEDIATE. Shut down options for the Oracle instance in pluggable database is IMMEDIATE. |
EnvFile | string-scalar | The full path name of the file that is sourced by the entry point scripts. This file contains the environment variables set by the user for the Oracle database server environment such as LD_LIBRARY_PATH, NLS_DATE_FORMAT, and so on. The syntax for the contents of the file depends on the login shell of Owner. File must be readable by Owner. The file must not contain any prompts for user input. |
Pfile | string-scalar | The name of the initialization parameter file with the complete path of the startup profile. You can also use the server parameter file. Create a one-line text initialization parameter file that contains only the SPFILE parameter. See the Oracle documentation for more information. Note: This attribute is applicable only for traditional and container databases. |
AutoEndBkup | boolean-scalar | Setting the AutoEndBkup attribute to a non-zero value takes the datafiles in the database out of the backup mode, during Online. Default = 1 Note: If a node fails during a hot backup of container database or pluggable database for Oracle 12C, you must set AutoEndBkup attribute of the corresponding CDB resource to 1. When the AutoEndBkup is set to 1 for the CDB, it also ends the backup of both CDB and PDB during Online. |
MonitorOption | integer-scalar | Monitor options for the Oracle instance. This attribute can take values 0 or 1. For traditional and container databases:
For pluggable databases:
You must set the value of this attribute as 1 to use the intentional offline functionality of the agent. Default = 0 The agent supports intelligent resource monitoring only for traditional and CDBs when the attribute value is set to 0. |
IMF | integer-association | This resource-type level attribute determines whether the Oracle agent must perform intelligent resource monitoring. You can also override the value of this attribute at resource-level. This attribute includes the following keys:
Note: IMF is supported only in traditional and container databases. See Enabling and disabling intelligent resource monitoring for agents manually. |
MonScript | string-scalar | Pathname to the script provided for detail monitoring. The default (basic monitoring) is to monitor the database PIDs only. Note: Second-level monitoring is disabled if the value of the attribute MonScript is invalid or is set to an empty string. The pathname to the supplied detail monitor script is /opt/VRTSagents/ha/bin/Oracle/SqlTest.pl. MonScript also accepts a pathname relative to /opt/VRTSagents/ha. A relative pathname should start with "./", as in the path ./bin/Oracle/SqlTest.pl. |
User | string-scalar | Internal database user. Connects to the database for detail monitoring. |
LevelTwoMonitorFreq | integer-scalar | Specifies the frequency at which the agent for this resource type must perform second-level or detailed monitoring. You can also override the value of this attribute at resource-level. The value indicates the number of monitor cycles after which the agent will monitor Oracle in detail. For example, the value 5 indicates that the agent will monitor Oracle in detail every five online monitor intervals. If you manually upgraded to the VCS 7.3.1 agent, and if you had enabled detail monitoring in the previous version, then do the following:
Note: If you set the AutoEndBkup attribute value to 0, then make sure that the LevelTwoMonitorFreq attribute value is 1 for detail monitoring. Default = 0 |
Pword | string-scalar | Encrypted password for internal database-user authentication. Encrypt passwords only when entering them using the command-line. Passwords must be encrypted using the VCS Encrypt Utility ( Note: This attribute is not applicable for PDB resources. |
Table | string-scalar | Table for update by User/Pword. |
Encoding | string-scalar | Specifies operating system encoding that corresponds to Oracle encoding for the displayed Oracle output. For example, if Oracle output is in "JAPANESE_JAPAN.JA16EUC," then "eucJP" is the Solaris value for Encoding. Refer to the Oracle and Solaris documentation for respective encoding values. Default is "". Note: This attribute is not applicable for PDB resources. |
IntentionalOffline | This resource-type level attribute defines how VCS reacts when Oracle is intentionally stopped outside of VCS control. If you stop Oracle traditional and container database out of VCS control, the agent behavior is as follows:
Note: If you want to use the intentional offline functionality of the agent, you must set the value of the MonitorOption attribute as 1 to enable Health check monitoring in the CDB. Note: If a CDB resource is configured with IntentionalOffline, and the configured CDB is brought down outside the VCS control, then the PDB resources will also report as offline. To enable this functionality, set the IntentionalOffline attribute to 1 for the PDB resource. See the Cluster Server Administrator’s Guide. | |
DBName | string-scalar | Set this attribute only when the database is a policy managed RAC database. The value of this attribute must be set to the database unique name. |
ManagedBy | string-scalar | Default value for this attribute is ADMIN. In a policy managed RAC database this attribute must be set to POLICY. |
PDBName | string-scalar | This attribute must be configured for a PDB. And the value should be set for a PDB database name. For traditional and CDB database, do not set this attribute. |
Table: Internal attributes for Oracle agent lists the internal attribute for Oracle agent. This attribute is for internal use only. Veritas recommends not to modify the value of this attribute.
Table: Internal attributes for Oracle agent
Optional Attributes | Type and Dimension | Definition |
---|---|---|
AgentDirectory | static-string | Specifies the location of binaries, scripts, and other files related to the Oracle agent. Default is /opt/VRTSagents/ha/bin/Oracle. |
More Information
About the Sid attribute in a policy managed database
Encrypting Oracle database user and listener passwords
Startup and shutdown options for the Oracle agent
Startup and shutdown options for the pluggable database (PDB)
Startup and shutdown options for the Oracle agent
Startup and shutdown options for the pluggable database (PDB)
Using the SPFILE in a VCS cluster
Failing over Oracle after a VCS node failure during hot backup
Monitor options for the Oracle agent in traditional database and container database