This chapter provides a description of each event view and its columns. It contains the following sections:
For examples of how to use views, see Chapter 20, "Examples".
The MGMT$INCIDENTS view provides a view of the attributes of the incident including its summary message. Ensure that any query against this view uses filtering on appropriate fields with OPEN_STATUS and CLOSED_DATE being the first to take advantage of partitions.
Column | Description |
---|---|
INCIDENT_ID |
The unique RAW ID of an incident |
INCIDENT_NUM |
The end-user visible ID of the incident |
SUMMARY_MSG |
Summary message of the incident |
SEVERITY |
The severity of the incident |
IS_ESCALATED |
Specifies whether the issue is escalated. Possible values:
|
ESCALATION_LEVEL |
If the incident is escalated, then this value specifies the escalation level. This value can be between level 1 and level 5. |
PRIORITY |
The priority level of the incident. Possible values:
|
RESOLUTION_STATE |
The resolution state of the issue. |
OWNER |
The owner of the issue. If there is no owner, then this value is "-". |
IS_ACKNOWLEDGED |
Specifies whether the incident is acknowledged. Possible values:
|
IS_SUPPRESSED |
Specifies whether the incident is suppressed. Possible values:
|
LAST_ANNOTATION_SEQ |
The sequence ID of the last annotation entered for this issue |
CREATION_DATE |
The date the incident was created |
LAST_UPDATED_DATE |
The date when this incident was updated last |
EVENT_COUNT |
The number of events associated with this incident |
OPEN_STATUS |
Specifies the status of the incident. Possible values:
|
CLOSED_DATE |
The date when the incident is closed (if it is closed) |
SRC_COUNT |
The number of unique target or source object combinations to which events in this incident belong |
TARGET_GUID |
The unique ID of a target associated with the incident This value is set only when all the events in the incident belong to the same target or source object combination. It is set to null when the events belong to multiple sources. |
SOURCE_OBJ_TYPE |
The source object or entity type to which all events in the incident belong (if they all belong to the same target or source object combination). Set to null when the events belong to multiple sources. |
ADR_RELATED |
Indicates if the incident is a Oracle diagnostic incident. Possible values:
|
TICKET_ID |
Ticket associated with this incident (can be null) |
TICKET_STATUS |
Status of the ticket associated with this incident (can be null) |
SR_ID |
ID of the service request associated with this problem (if any) |
PROBLEM_ID |
The unique RAW ID of the related problem (if any) |
PROBLEM_NUM |
The end-user visible ID of the related problem (if any) |
The MGMT$INCIDENT_CATEGORY view is the incident view for the mapping between incidents and categories. An incident can have multiple categories associated with it. Ensure that any query against this view uses filtering on appropriate fields with OPEN_STATUS and CLOSED_DATE being the first to take advantage of partitions.
The MGMT$INCIDENT_TARGET view is the incident view for the mapping between incidents and targets. An incident can be made of multiple events and these events could be from different targets. Ensure that any query against this view uses filtering on appropriate fields with OPEN_STATUS and CLOSED_DATE being the first to take advantage of partitions.
Table 6-3 MGMT$INCIDENT_TARGET
Column | Description |
---|---|
INCIDENT_ID |
The unique RAW ID of an incident |
TARGET_GUID |
The unique ID of a target (can be null) |
OPEN_STATUS |
Specifies the status of the incident. Possible values:
|
CLOSED_DATE |
The date when the incident is closed |
The MGMT$INCIDENT_ANNOTATION view is the view for the mapping between the incidents and annotations. Each incident can have multiple annotations. Ensure that any query against this view uses filtering on appropriate fields with OPEN_STATUS and CLOSED_DATE being the first to take advantage of partitions.
Table 6-4 MGMT$INCIDENT_ANNOTATION
Column | Description |
---|---|
INCIDENT_ID |
The unique RAW ID of an incident |
ANNOTATION_SEQ |
The order ID in which the annotation is added |
ANNOTATION_MSG |
The annotation message |
ANNOTATION_DATE |
The time stamp when the annotation is made |
ANNOTATION_TYPE |
The type of the annotation, that is, whether it is user or system generated. Possible values:
|
ANNOTATION_USER |
The user that added the annotation. If the annotation is system-generated, then this value is set to "-" . |
OPEN_STATUS |
Specifies the status of the incident. Possible values:
|
CLOSED_DATE |
The date when the incident is closed |
The MGMT$EVENTS_LATEST view shows the details of the latest state of all events in a given sequence of events. A sequence is a series of raw events that are related to the same source and reporting on the same issue. For example, for a given host, if the CPU utilization goes from warning to critical and then to warning again, then these three events are correlated into a single sequence with three raw events with warning as the latest state. Ensure that any query against this view uses filtering on appropriate fields with OPEN_STATUS and CLOSED_DATE being the first to take advantage of partitions.
Column | Description |
---|---|
EVENT_SEQ_ID |
The unique RAW ID of an event sequence |
EVENT_ID |
The unique RAW ID of the latest event in the sequence |
EVENT_CLASS |
The event class to which this event belongs |
SEVERITY |
The severity of the event |
LAST_ANNOTATION_SEQ |
The sequence ID of the last annotation entered for this sequence |
MSG |
The event message |
EVENT_NAME |
The internal event name describing the nature of the events |
INCIDENT_ID |
The incident ID to which this event belongs (if any) |
INCIDENT_NUM |
The end-user readable number or ID for the incident |
TARGET_GUID |
The target GUID to which the events of the sequence belong. If the sequence is not related to any target, then this value is set to NULL. |
SOURCE_OBJ_TYPE |
The source object or entity type to which the events of the sequence belong. Default value is NULL |
SOURCE_OBJ_ID |
The source object or entity GUID to which the events of the sequence belong. Default value is NULL |
OPEN_STATUS |
The status of the event sequence. The event sequence is considered open if the severity of the last event is a non-clear severity. Possible values:
|
CLOSED_DATE |
The date when the event is marked as closed, that is, when the event sequence is cleared |
CREATION_DATE |
The date the event sequence was created |
LAST_UPDATED_DATE |
The date when this event sequence was last updated |
The MGMT$EVENTS view shows the details of all the raw events in a given sequence of events. A sequence is a series of raw events that are related to the same source and reporting on the same issue. For example, for a given host, if the CPU utilization goes from warning to critical and then to warning again, then these three events are correlated into a single sequence with three raw events with warning as the latest state. Ensure that any query against this view uses filtering on appropriate fields with OPEN_STATUS and CLOSED_DATE being the first to take advantage of partitions.
Column | Description |
---|---|
EVENT_SEQ_ID |
The unique RAW ID of the event sequence |
EVENT_ID |
The unique RAW ID of the event |
SIGNATURE_ID |
The ID of the unique signature of raw events that is used to correlate all raw events to a sequence |
EVENT_CLASS |
The event class to which this event belongs |
SEVERITY |
The severity of the raw event |
LAST_ANNOTATION_SEQ |
The sequence ID of the last annotation entered for this sequence |
MSG |
The event message |
EVENT_NAME |
The internal event name describing the nature of the events |
INCIDENT_ID |
The incident ID to which this event belongs (if applicable) |
INCIDENT_NUM |
The end-user readable number or ID for the incident |
TARGET_GUID |
The target GUID to which the event belongs. If the sequence is not related to any target, then this value is set to NULL. |
SOURCE_OBJ_TYPE |
The source object or entity type to which the event belongs. Default value is NULL |
SOURCE_OBJ_ID |
The source object or entity GUID to which the event belongs. Default value is NULL |
OPEN_STATUS |
The status of the event sequence. The event sequence is considered open if the severity of the last event is a non-clear severity. Possible values:
|
CLOSED_DATE |
The date when the event is marked as closed, that is, when the event sequence is cleared |
REPORTED_DATE |
The date when the event was reported |
The MGMT$EVENT_ANNOTATION view is the view for the mapping between events and annotations. Each event can have multiple annotations. Ensure that any query against this view uses filtering on appropriate fields with OPEN_STATUS and CLOSED_DATE being the first to take advantage of partitions.
Note:
Annotations are associated with the sequence and not with the individual raw eventsTable 6-7 MGMT$EVENT_ANNOTATION
Column | Description |
---|---|
EVENT_SEQ_ID |
The unique RAW ID of an event sequence |
EVENT_INSTANCE_ID |
The unique RAW ID of an event instance |
ANNOTATION_SEQ_NUM |
The order ID in which the annotations is added |
ANNOTATION_DATE |
The time stamp when the annotation is made |
ANNOTATION_TYPE |
The type of the annotation, that is, whether it is user or system generated. Possible values:
|
ANNOTATION_USER |
The user which added the annotation |
ANNOTATION_MSG |
The annotation message |
OPEN_STATUS |
The status of the event sequence. The event sequence is considered open if the severity of the last event is a non-clear severity. Possible values:
|
CLOSED_DATE |
The date when the event is marked as closed, that is, when the event sequence is cleared |
The MGMT$PROBLEMS view provides a view of the attributes of the problem including its summary message. Ensure that any query against this view uses filtering on appropriate fields with OPEN_STATUS and CLOSED_DATE being the first to take advantage of partitions.
Column | Description |
---|---|
PROBLEM_ID |
The unique RAW ID of the problem |
PROBLEM_NUM |
The end-user visible ID of the problem |
SUMMARY_MSG |
Summary message of the problem |
SEVERITY |
The severity of the problem |
IS_ESCALATED |
Specifies whether the issue is escalated. Possible values:
|
ESCALATION_LEVEL |
If the problem is escalated, then this value specifies the escalation level. This value can be between level 1 and level 5. |
PRIORITY |
The priority level of the incident. Possible values:
|
RESOLUTION_STATE |
The resolution state of the issue |
OWNER |
The owner of the issue. If there is no owner, then this value is "-". |
IS_ACKNOWLEDGED |
Specifies whether the problem is acknowledged. Possible values:
|
IS_SUPPRESSED |
Specifies whether the problem is suppressed. Possible values:
|
LAST_ANNOTATION_SEQ |
The sequence ID of the last annotation entered for this issue |
CREATION_DATE |
The date the problem was created |
LAST_UPDATED_DATE |
The date when this problem was updated last |
INC_COUNT |
The number of incidents associated with this problem |
OPEN_STATUS |
Specifies the status of the problem. Possible values:
|
CLOSED_DATE |
The date when the problem is closed (if it is closed) |
TARGET_GUID |
The unique ID of a target (can be null). This value is set only when all the incidents in the problem belong to the same target or source object combination. It is set to null when the incidents belong to multiple sources. Note: For this release, problems can be associated with a single target only |
PROBLEM_KEY |
Unique signature of this problem |
SR_ID |
ID of the service request associated with this problem, if any |
BUG_ID |
ID of the bug associated with this problem, if any |
The MGMT$PROBLEM_ANNOTATION view is the view for the mapping between problems and annotations. Each problem can have multiple annotations. Ensure that any query against this view uses filtering on appropriate fields with OPEN_STATUS and CLOSED_DATE being the first to take advantage of partitions.
Table 6-9 MGMT$PROBLEM_ANNOTATION
Column | Description |
---|---|
PROBLEM_ID |
The unique RAW ID of a problem |
ANNOTATION_SEQ |
The order ID in which the annotations is added |
ANNOTATION_MSG |
The annotation message |
ANNOTATION_DATE |
The time stamp when the annotation is made |
ANNOTATION_TYPE |
The type of the annotation, either user or system generated. Valid values are 'USER' or 'SYSTEM' |
ANNOTATION_USER |
The user which added the annotation |
OPEN_STATUS |
Specifies the status of the problem. Possible values:
|
CLOSED_DATE |
The date when the problem is closed |