Event Alarm Parameters

Event alarms have five parameters that describe each event.

The following table lists the parameters that are part of event alarm.
Table 1. Event Alarm Parameters
Parameter Description Data Type
severity The severity of the event. integer
class_id A numeric identifier that classifies the type of event that has occurred. integer
class_msg A brief messages that describes the classification of the event. string
specific_msg Specific messages that describes the event that occurred. string
see_also A reference to a file that contains additional information about the event. string
uniqueid A unique event identifier for the specific message. bigint

Event Severity

An event severity code is a numeric indication of the seriousness of an event. Every event that is included in the message log contains a severity code. The event severity code is the first parameter that is sent to the alarm program. In the ph_alert table, the event severity is reflected by a combination of the alert color and the alert type. The event severity codes are listed in the following table.

Table 2. Event Severity Codes
Severity Description
1 Not noteworthy. The event (for example, date change in the message log) is not reported to the alarm program unless ALRM_ALL_EVENTS configuration parameter is enabled.

In the ph_alert table, the alert color is GREEN and the alert type is INFO.

2 Information. No error has occurred, but some routine event completed successfully (for example, checkpoint or log backup completed).

In the ph_alert table, the alert color is YELLOW and the alert type is INFO.

3 Attention. This event does not compromise data or prevent the use of the system; however, the event warrants your attention. For example, one chunk of a mirrored pair goes down. An email is sent to the system administrator.

In the ph_alert table, the alert color is YELLOW and the alert type is WARNING.

4 Emergency. Something unexpected occurred that might compromise data or access to data. For example an assertion failure, or oncheck reports data corrupt. Take action immediately. The system administrator is paged when this event severity occurs.

In the ph_alert table, the alert color is RED and the alert type is ERROR.

5 Fatal. Something unexpected occurred and caused the database server to fail. The system administrator is paged when this event severity occurs.

In the ph_alert table, the alert color is RED and the alert type is ERROR.

Class ID

The class ID is an integer that identifies the event that causes the database server to run your alarm program. The class ID is the second parameter that the database server displays in your alarm program.

The class ID is stored in the alert_object_name column in the ph_alert table.

Class Message

The class message is a text message briefly describes, or classifies, the event that causes the database server to run your alarm program. The class messages is the third parameter that the database server displays in your alarm program.

Specific Message

The specific message is a text messages the describes in more detail the event that causes the database server to run your alarm program. The specific message is the fourth parameter that the database server displays in your alarm program. For many alarms, the text of this message is the same as the message that is written to the message log for the event.

The specific message is stored in the alert_message column in the ph_alert table.

See Also Paths

For some events, the database server writes additional information to a file when the event occurs. The path name in this context refers to the path name of the file where the database server writes the additional information.

Event ID

The event ID is a unique number for each specific message. You can use the event ID in custom alarm handling scripts to create responses to specific events.

The event ID is stored in the alert_object_info column in the ph_alert table.


Copyright© 2019 HCL Technologies Limited