ORIGINATING_TIMESTAMP

TIMESTAMP(9) WITH TIME ZONE

Date and time when the message was generated

NORMALIZED_TIMESTAMP

TIMESTAMP(9) WITH TIME ZONE

Date and time when the message originated, normalized for clock drift to the Oracle Enterprise Manager repository time

ORGANIZATION_ID

VARCHAR2(67)

ID of the organization that wrote the originating component, usually the domain of the organization

COMPONENT_ID

VARCHAR2(67)

ID of the product or component that originated the message

HOST_ID

VARCHAR2(67)

DNS hostname of originating host

HOST_ADDRESS

VARCHAR2(49)

IP of other network address of the originating host for the mesaage

MESSAGE_TYPE

NUMBER

Type of the message, indicating that a different type of response is required. Possible values include:

• 1 - UNKNOWN: Essentially the NULL type

• 2 - INCIDENT_ERROR: The program has encountered an error for some internal or unexpected reason, and it must be reported to Oracle Support

• 3 - ERROR: An error of some kind has occurred

• 4 - WARNING: An action occurred or a condition was discovered that should be reviewed and may require action

• 5 - NOTIFICATION: Reports a normal action or event. This could be a user action such as "logon completed."

• 6 - TRACE: Output of a diagnostic trace

MESSAGE_LEVEL

NUMBER

Level the message belongs to. Lower level values imply higher severity for errors. Possible values include:

• 1 - CRITICAL: Critical errors

• 2 - SEVERE: Severe errors

• 8 - IMPORTANT: Important message

• 16 - NORMAL: Normal message

MESSAGE_ID

VARCHAR2(67)

ID of the message

MESSAGE_GROUP

VARCHAR2(67)

Name of the group to which the message belongs

CLIENT_ID

VARCHAR2(67)

ID of the client or security group that the message relates to

MODULE_ID

VARCHAR2(67)

ID of the module that originated the message. This value is unique within a component.

PROCESS_ID

VARCHAR2(35)

ID of the process that originated the message

THREAD_ID

VARCHAR2(67)

ID of the thread of the process that originated the message

USER_ID

VARCHAR2(131)

ID of the user that originated the message

INSTANCE_ID

VARCHAR2(67)

For internal use only

DETAILED_LOCATION

VARCHAR2(163)

Absolute pathname of supplemental detail file on the originating host

UPSTREAM_COMP_ID

VARCHAR2(103)

ID of a component that the originating component is working with on the upstream (client) side

DOWNSTREAM_COMP_ID

VARCHAR2(103)

ID of a component that the originating component is working with on the downstream (server) side

EXECUTION_CONTEXT_ID

VARCHAR2(103)

Identifies the thread of execution that the originating component participates in

EXECUTION_CONTEXT_SEQUENCE

NUMBER

Execution sequence of the thread that the originating component participates in

ERROR_INSTANCE_ID

NUMBER

ID of the instance where error occurred

ERROR_INSTANCE_SEQUENCE

NUMBER

Instance sequence where error occurred

MESSAGE_TEXT

VARCHAR2(2051)

Fully formed and localized text of the message

MESSAGE_ARGUMENTS

VARCHAR2(515)

Arguments to be bound with the generic text of the message

SUPPLEMENTAL_ATTRIBUTES

VARCHAR2(515)

Supplemental attributes that are specific to a message. This field contains the impacts for an incident type error message.

SUPPLEMENTAL_DETAILS

VARCHAR2(515)

Supplemental data that is specific to a particular program and error message required to complete the diagnosis. Similar to the extra detail referred to in DETAILED_LOCATION but short enough to simply provide in the message itself

PARTITION

NUMBER

Segment number of physical file

RECORD_ID

NUMBER

Record number for the message (this value is same as the row number)

FILENAME

VARCHAR2(515)

Physical file on disk

LOG_NAME

VARCHAR2(67)

For internal use only

PROBLEM_KEY

VARCHAR2(553)

Describes the key for the current problem that the message is associated with

VERSION

NUMBER

ARB version number for the message

CON_UID

NUMBER

The unique ID of the container to which the data pertains

CONTAINER_ID

NUMBER

The ID of the container to which the data pertains

CONTAINER_NAME

VARCHAR2(67)

Name of the container to which the data pertains

ATTENTION_ID

NUMBER

Unique ID for the message

This column is used primarily for attention messages. Alert messages may or may not have an ID. If the same attention message is triggered multiple times, it will have the same ID each time.

ID_SUFFIX

VARCHAR2(67)

Reserved for future use

OPERATION_ID

VARCHAR2(67)

Reserved for future use

CAUSE_TEXT

VARCHAR2(2051)

Cause of the message

ACTION_TEXT

VARCHAR2(2051)

Recommended action to resolve the issue triggering the message

ORACLE_PROCESS_ID

NUMBER

ID of the Oracle process triggering the message

DATABASE_ID

VARCHAR2(33)

Database identifier, as specified by the DB_NAME initialization parameter

SQL_ID

VARCHAR2(16)

Identifier of the SQL statement being processed when the message was triggered

SESSION_ID

VARCHAR2(19)

Identifier of the session in which the message was triggered

IMPACT_ID

VARCHAR2(35)

Reserved for future use

IMPACT_SCOPE

VARCHAR2(35)

Scope of impact of the issue triggering the message:

• ASM CLUSTER - The extent of damage or influence encompasses Oracle ASM at the cluster level.

• ASM INSTANCE (TRANSIENT) - The extent of damage or influence is limited to a specific Oracle ASM instance.

• CDB CLUSTER - The extent of damage or influence encompasses the entire CDB and its cluster.

• CDB Instance (TRANSIENT) - The extent of damage or influence encompasses the entire CDB. The issue is not permanent and can be resolved, for example, by an instance restart.

• CDB (PERSISTENT) - The extent of damage or influence encompasses the entire CDB. The issue is persistent, for example, an issue with persistent storage, and typically cannot be resolved by an instance restart.

• DISK GROUP - The extent of damage or influence is limited to the disk group.

• ORACLE INSTANCE - The extent of damage or influence is limited to the Oracle instance. For example, an Oracle database instance or an Oracle ASM instance.

• PDB Instance (TRANSIENT) - The extent of damage or influence encompasses the PDB. The issue is not permanent and can be resolved, for example, by a PDB restart.

• PDB (PERSISTENT) - The extent of damage or influence encompasses the PDB. The issue is persistent, for example, an issue with persistent storage, and typically cannot be resolved by a PDB restart.

• PROCESS - The extent of damage or influence is limited to the process in which the error happened. If the affected process terminates or restarts, the impact of the error will not be felt.

• SESSION - The extent of damage or influence is limited to the session in which the message was triggered. The issue will not be experienced in other sessions executing concurrently in the system.

TARGET_USER

VARCHAR2(35)

User at whom the message is targeted:

• APP-DEV

• CDB-ADMIN

• CLUSTER-ADMIN

• DATAOPS-ADMIN

• NET-ADMIN

• PDB-ADMIN

• SEC-ADMIN

• SERVER-ADMIN

• STORAGE-ADMIN

CALL_STACK

VARCHAR2(1027)

Function call stack

This column is populated when the MESSAGE_TYPE value is 2 (INCIDENT_ERROR), 3 (ERROR), or 4 (WARNING).

FLAGS

NUMBER

Reserved for internal use

URGENCY

VARCHAR2(19)

Time criticality of the message

Possible values, ordered from highest urgency to lowest urgency:

• IMMEDIATE - The issue must be looked at immediately by administrators. Examples: Database down, data corruption, instance down, or a memory leak that could cause a crash.

• SOON - The issue should be looked at in a reasonably short time frame, that is, the same day, but does not require immediate action. Examples: Isolated internal error or a disk filling up.

• DEFERABLE - The issue should be looked at, but it is acceptable to look at it later. Example: Configuration advice.

• INFO - Used mostly for notifications and does not require administrator attention. Example: Instance started.

Frequently occurring messages are upgraded to higher urgency values.

START_VERSION

VARCHAR2(19)

Version of the product for which this message first starts being used

This column is populated only for messages that are registered, that is, messages that have a MESSAGE_ID.

SECURITY_LABEL

VARCHAR2(19)

Reserved for internal use

CON_ID

NUMBER

The ID of the container to which the data pertains. Possible values include:

• 0: This value is used for rows containing data that pertain to the entire CDB. This value is also used for rows in non-CDBs.

• 1: This value is used for rows containing data that pertain to only the root

• n: Where n is the applicable container ID for the rows containing data