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
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 AIX WPARs. The values for the following keys are only effective when you set the ContainerInfo service group attribute. Symantec recommends that you do not change the following values.
See the Veritas Cluster Server Administrator's Guide and the Veritas Storage Foundation and High Availability Solutions 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:
Default is STARTUP_FORCE. |
||
ShutDownOpt |
string-scalar |
Shut down options for the Oracle instance. This attribute can take the following values:
Default 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. |
||
AutoEndBkup |
integer-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 |
||
MonitorOption |
integer-scalar |
Monitor options for the Oracle instance. This attribute can take values 0 or 1.
You must set the value of this attribute as 1 to use the intentional offline functionality of the agent. The agent supports intelligent resource monitoring only when this attribute value is set to 0. Default = 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:
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.
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 6.0.1 agent, and if you had enabled detail monitoring in the previous version, then do the following:
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 ( |
||
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. Default is "". |
||
IntentionalOffline |
This resource-type level attribute defines how VCS reacts when Oracle is intentionally stopped outside of VCS control. If you stop Oracle out of VCS control, the agent behavior is as follows:
See the Veritas 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. |
||
CleanRetryLimit |
integer-scalar |
Set the CleanRetryLimit attribute to a finite value. When the attribute reaches the set limit, the agent sets the ADMIN_WAIT flag for the Oracle agent resource. It also sends the reason behind setting the flag to VCS. Based on the reason, VCS invokes the resadminwait trigger. Write a custom program that causes the system to panic if the ADMIN_WAIT flag is set for a specific reason. For the system to panic, implement the custom program as part of the resadminwait trigger script. For more information of CleanRetryLimit, refer to the Veritas Cluster Server Agent Developer's Guide. For more information on configuring triggers, refer to the Veritas Cluster Server Administrator's Guide. |
Table: Internal attributes for Oracle agent lists the internal attribute for Oracle agent. This attribute is for internal use only. Symantec recommends not to modify the value of this attribute.
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 Oracle agent
Using the SPFILE in a VCS cluster
Failing over Oracle after a VCS node failure during hot backup