8.185 V$DIAG_ATTENTION

V$DIAG_ATTENTION displays attention messages in the XML-based alert log in the Automatic Diagnostic Repository (ADR) for the current container (PDB).

Column Datatype Description

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

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.

ATTENTION_TYPE

VARCHAR2(12)

Type of the attention message, indicating the type of response required:

  • ERROR - An error has occurred.

  • WARNING - An event occurred or a condition was discovered, and it should be reviewed and may require action.

  • NOTIFICATION - An event occurred or a condition was discovered, but action is not required. For example, this could be an event such as "shutdown completed."

  • UNKNOWN - An unknown event occurred.

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.

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

MESSAGE_TEXT

VARCHAR2(2051)

Fully formed and localized text of the message

SUPPLEMENTAL_DETAILS

VARCHAR2(515)

Supplemental data that is specific to a particular program and error message required to complete the diagnosis.

CAUSE_TEXT

VARCHAR2(2051)

Cause of the message

ACTION_TEXT

VARCHAR2(2051)

Recommended action to resolve the issue triggering the message

START_VERSION

VARCHAR2(19)

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

SECURITY_LABEL

VARCHAR2(19)

Reserved for internal use

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

DATABASE_ID

VARCHAR2(33)

Database identifier, as specified by the DB_NAME initialization parameter

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

Note:

This view is available starting with Oracle AI Database 26ai.

See Also:

"V$DIAG_ALERT_EXT" to view the entire contents of the alert log in the Automatic Diagnostic Repository (ADR)