< Previous  | TOC | Index | Next  >

Configuring the Oracle resource

An Oracle resource starts and stops an Oracle instance, and monitors the process table. In addition to the required attributes for the resource, you can modify these attributes to suit your environment. See the Veritas High Availability Agent for Oracle Installation and Configuration Guide for details on the Oracle agent and ways to manage database functions from within VCS.

StartUpOpt attribute

The Oracle agent supports the StartUpOpt attribute to enable you to control how VCS starts a database instance.

• RECOVERDB:Assume that in the event the database node fails for a non-database issue, you do not want the database to start up (come online) if any data file recovery needs to take place. If you set StartUpOpt to RECOVERDB and the system running the database faults, VCS starts the database in recovery mode when it fails to another node.
• CUSTOM: You may want to start the database up in standby mode and apply logs. In this case, you can create an SQL script to perform these actions, and this script is called when you set StartUpOpt to CUSTOM. You must start the script in /opt/VRTSvcs/bin/oracle with the name of start_custom_SID.sql, where SID is the same as the value of the SID attribute.

ShutDownOpt attribute

Configure the ShutDownOpt attribute for the Oracle resource to control how VCS stops a database instance when the Oracle resource is taken offline. If CUSTOM is specified, a script must exist in /opt/VRTSvcs/bin/oracle with the name of the shut_custom_SID.sql, where SID is the same as the value of the SID attribute for this Oracle resource.

Other optional Oracle attributes

Review these additional Oracle attributes:

• AutoEndBkup takes the data files in the database out of the backup mode when coming online. The default value is 1 (true).
• EnvFile speciifies the location of a file sourced by the Oracle agent entry point scripts containing environment variables.
• Encoding specifies encoding for other language sets.

Configuring Oracle detail monitoring

These optional Oracle attributes are used to configure detail monitoring:

• DetailMonitor: A flag to enable and disable detail monitoring. The default value of 0 prevents detail monitoring. You can set this value higher than zero to control how often detail monitoring occurs.
• User: A database user account with updated privileges.
• Pword: The password for the database user account.
• Table: The name of the database table VCS uses for additional monitoring.
• MonScript: The executable script file containing the SQL statements VCS uses when writing to the table.
• EnvFile: The file containing environmental variables sources by the agent.

Configuration prerequisites include:

• Create the database user and password for use by VCS.
• Create a test table with the monitored database.
• Create an executable script with SQL statements.

You can use the VCS encryption utility to encrypt database passwords before configuring the Pword attribute in the Oracle agent configuration.

  Note   The value of Pword is automatically encrypted when you use the Oracle configuration wizard or one of the VCS GUIs to configure the resource.

• To encrypt a password, use the vcsencrypt command:

  # root:/opt/VRTSvcs/bin> vcsencrypt -agent

You can configure the optional Oracle error handling file when using detail monitoring to specify VCS response based on the type of database errors. See /opt/VRTSvcs/bin/Oracle/oraerror.dat.