Cloud Exadata Infrastructure Event Types

Cloud Exadata Infrastructure Critical and Information Event Types

These events use the additionalDetails section of the event message to provide specific details about what is happening within the infrastructure resource emitting the event. In the additionalDetails section, the eventName field provides the name of the critical or information event. (Note that some fields in the example that follows have been omitted for brevity.)

{
  "eventType" : "com.oraclecloud.databaseservice.exadatainfrastructure.critical",
  ....
  "data" : {
   ....
     "additionalDetails" : {
      ....
      "description" : "SQL statement terminated by Oracle Database Resource Manager due to excessive consumption of CPU and/or I/O. The execution plan associated with the terminated SQL stmt is quarantined. Please find the sql identifier in sqlId field of this JSON payload. This feature protects an Oracle database from performance degradation. Please review the SQL statement. You can see the statement using the following commands: \"set serveroutput off\", \"select sql_id, sql_text from v$sqltext where sql_id =<sqlId>\", \"set serveroutput on\"",
      "component" : "storage",
      "infrastructureType" : "exadata",
      "eventName" : "CloudExadataInfrastructure.SqlQuarantine",
      "quarantineMode" : "\"FULL Quarantine\""
       ....
    }
  },
  "eventID" : "<unique_ID>",
  ....
  }
}

For full-length example critical and information events, see Example: Critical Event for Cloud Exadata Infrastructure Resource and Example: Information Event for Cloud Exadata Infrastructure Resource.

In the tables below, you can read about the conditions and operations that trigger "critical" and "information" events. Each condition or operation is identified by a unique eventName value.

\"set serveroutput off\"
\"select sql_id, sql_text from v$sqltext where sql_id =<sqlId>\"
\"set serveroutput on\"

Example: Critical Event for Cloud Exadata Infrastructure Resource

{
  "eventType" : "com.oraclecloud.databaseservice.exadatainfrastructure.critical",
  "cloudEventsVersion" : "0.1",
  "eventTypeVersion" : "2.0",
  "source" : "Exadata Storage",
  "eventTime" : "2021-07-30T04:53:18Z",
  "contentType" : "application/json",
  "data" : {
    "compartmentId" : "ocid1.tenancy.oc1.<unique_ID>",
    "compartmentName" : "example_name",
    "resourceName" : "my_exadata_resource",
    "resourceId" : "ocid1.dbsystem.oc1.phx.<unique_ID>",
    "availabilityDomain" : "phx-ad-2",
     "additionalDetails" : {
      "serviceType" : "exacs",
      "sqlID" : "gnwfm1jgqcfuu",
      "systemId" : "ocid1.dbsystem.oc1.eu-frankfurt-1.<unique_ID>",
      "creationTime" : "2021-05-14T13:29:28+00:00",
      "dbUniqueID" : "1558836122",
      "quarantineType" : "SQLID",
      "dbUniqueName" : "AB0503_FRA1S6",
      "description" : "SQL statement terminated by Oracle Database Resource Manager due to excessive consumption of CPU and/or I/O. The execution plan associated with the terminated SQL stmt is quarantined. Please find the sql identifier in sqlId field of this JSON payload. This feature protects an Oracle database from performance degradation. Please review the SQL statement. You can see the statement using the following commands: \"set serveroutput off\", \"select sql_id, sql_text from v$sqltext where sql_id =<sqlId>\", \"set serveroutput on\"",
      "quarantineReason" : "Manual",
      "asmClusterName" : "None",
      "component" : "storage",
      "infrastructureType" : "exadata",
      "name" : "143",
      "eventName" : "CloudExadataInfrastructure.SqlQuarantine",
      "comment" : "None",
      "quarantineMode" : "\"FULL Quarantine\"",
      "rpmVersion" : "OSS_20.1.8.0.0_LINUX.X64_210317",
      "cellsrvChecksum" : "14f73eb107dc1be0bde757267e931991",
      "quarantinePlan" : "SYSTEM"
    }
  },
  "eventID" : "<unique_ID>",
  "extensions" : {
    "compartmentId" : "ocid1.tenancy.oc1.<unique_ID>"
  }
}

Example: Information Event for Cloud Exadata Infrastructure Resource

{
  "eventType" : "com.oraclecloud.databaseservice.exadatainfrastructure.information",
  "cloudEventsVersion" : "0.1",
  "eventTypeVersion" : "2.0",
  "source" : "Exadata Storage",
  "eventTime" : "2021-12-17T19:14:42Z",
  "contentType" : "application/json",
  "data" : {
    "compartmentId" : "ocid1.tenancy.oc1..aaaaaaaao3lj36x6lwxyvc4wausjouca7pwyjfwb5ebsq5emrpqlql2gj5iq",
    "compartmentName" : "intexadatateam",
    "resourceId" : "ocid1.dbsystem.oc1.phx.abyhqljt5y3taezn7ug445fzwlngjfszbedxlcbctw45ykkaxyzc5isxoula",
    "availabilityDomain" : "phx-ad-2",
    "additionalDetails" : {
      "serviceType" : "exacs",
      "component" : "storage",
      "systemId" : "ocid1.dbsystem.oc1.phx.abyhqljt5y3taezn7ug445fzwlngjfszbedxlcbctw45ykkaxyzc5isxoula",
      "infrastructureType" : "exadata",
      "description" : "Flash Disk Failure has been detected. This is being investigated by Oracle Exadata team and the disk will be replaced if needed. No action needed from the customer.",
      "eventName" : "CloudExadataInfrastructure.FlashDiskFailure",
      "FLASH_1_1" : "S2T7NA0HC01251  failed",
      "otto-ingestion-time" : "2021-12-17T19:14:43.205Z",
      "otto-send-EventService-time" : "2021-12-17T19:14:44.198Z"
    }
  },
  "eventID" : "30130ab4-42fa-4285-93a7-47e49522c698",
  "extensions" : {
    "compartmentId" : "ocid1.tenancy.oc1..aaaaaaaao3lj36x6lwxyvc4wausjouca7pwyjfwb5ebsq5emrpqlql2gj5iq"
  }
}

Cloud Autonomous Exadata VM Cluster Critical, Warning, and Information Event Types

These events use the additionalDetails section of the event message to provide specific details about what is happening within the Autonomous Exadata VM Cluster resource emitting the event. In the additionalDetails section, the eventName field provides the name of the critical, warning, or information event.

In the tables below, you can read about the conditions and operations that trigger critical, warning, and information events. Each condition or operation is identified by a unique eventName value.

Autonomous Container Database Critical, Warning, and Information Event Types

These events use the additionalDetails section of the event message to provide specific details about what is happening within the Autonomous Container Database resource emitting the event. In the additionalDetails section, the eventName field provides the name of the critical, warning, or information event.

In the tables below, you can read about the conditions and operations that trigger critical, warning, and information events. Each condition or operation is identified by a unique eventName value.

Autonomous Database Event Types

Autonomous Database Critical, Warning, and Information Event Types

In the following example of a critical event, you can see within the additionalDetails section of the event message that this particular message concerns an "ADMIN password expired" condition that has just ended. The eventName and description fields provide information regarding the critical situation within the "adwfinance" database:

In the tables below, you can read about the conditions and operations that trigger critical, warning, and information events. Each condition or operation is identified by a unique eventName value.

The following table lists the event types for the old Autonomous Data Guard Associations model. These events are deprecated and replaced by new Autonomous Data Guard Groups model event types. See Autonomous Data Guard Models for more information.

Autonomous Data Guard associations emit critical event types. These event types allow you to receive notifications when your Autonomous Data Guard association needs urgent attention.

The eventType value for these events is com.oraclecloud.databaseservice.autonomous.container.database.dataguardassociation.critical

These events use the additionalDetails section of the event message to provide specific details about what is happening with the Autonomous Data Guard association emitting the event. In the additionalDetails section, the eventName field provides the name of the critical event.

In the table below, you can read about the conditions and operations that trigger critical events. Each condition or operation is identified by a unique eventName value.