How the agent handles Oracle error codes during detail monitoring
The Cluster Server agent for Oracle handles Oracle errors during detail monitoring. The agent classifies Oracle errors according to their severity and associates predefined actions with each error code.
The agent includes a reference file oraerror.dat, which lists Oracle errors and the action to be taken when the error is encountered.
The file stores information in the following format:
Oracle_error_string:action_to_be_taken
For example:
01035:WARN
01034:FAILOVER
Note: |
When the oraerror.dat file contains two or more errors, the order in which the Cluster Server agent for Oracle handles the errors is: FAILOVER/NOFAILOVER, UNKNOWN, and IGNORE/WARN. |
Table: Predefined agent actions for Oracle errors lists the predefined actions that the agent takes when an Oracle error is encountered.
Table: Predefined agent actions for Oracle errors
|
Action
|
Description |
|
IGNORE
|
Ignores the error.
When the Veritas agent for Oracle encounters an error, the agent matches the error code in the oraerror.dat file. If the error does not have a matching error code in the file, then the agent ignores the error.
|
|
UNKNOWN
|
Marks the resource state as UNKNOWN and sends a notification if the Notifier resource is configured. See the Cluster Server Administrator’s Guide for more information about VCS notification.
This action is typically associated with configuration errors or program interface errors.
|
|
WARN
|
Marks the resource state as ONLINE and sends a notification if the Notifier resource is configured.
This action is typically associated with errors due to exceeded quota limits, session limits/restricted sessions so on.
|
|
FAILOVER
(Default)
|
Marks the resource state as OFFLINE. This faults the service group by default, which fails over to the next available system.
If the file oraerror.dat is not available, the agent assumes this default behavior for every Oracle error encountered.
|
|
NOFAILOVER
|
Freezes the service group temporarily and marks the resource state as OFFLINE. The agent also sends a notification if the Notifier resource is configured.
This action is typically associated with the errors that are not system-specific. For example, if a database does not open from a node due to corrupt Oracle files, failing it over to another node does not help.
|
