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 |
||||
---|---|---|---|---|---|---|
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.
|
||||
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
|
||||
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:
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 7.3 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 traditional and container database out of VCS control, the agent behavior is as follows:
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. |
||||
UseSystemD SLES 12, RHEL 7, and supported RHEL-compatible distributions |
Boolean |
systemD is a system and service manager for Linux operating systems. It helps manage applications across Linux distributions that support systemD feature. When Online Entry point is invoked with Consideration: Upon a system reboot, if application resource has been started under user.slice, there is a possibility that the processes are not stopped gracefully. This may cause the database to corrupt. This behavior is different for each Oracle application version. Hence, enable UseSystemD attribute for Oracle on you system. The application process can be viewed as vcs-<resource_name>.service, in /etc/systemd/system. Set the |
||||
SystemDAttrList SLES 12, RHEL 7, and supported RHEL-compatible distributions |
string-scalar |
Ensure that For example, # hares -modify oracle SystemDAttrList LimitLOCKS 44433 Where, LimitLOCKS is the key and 44433 is the value for the key. |
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.
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