Oracle Exadata Database Service on Dedicated Infrastructure Events
Exadata Cloud Infrastructure resources emit events, which are structured messages that indicate changes in resources.
- About Event Types on Exadata Cloud Infrastructure
Learn about the event types available for Exadata Cloud Infrastructure resources. - Prerequisites for Event Service
The following prerequisites are required for the Events to flow out of the VM Cluster. - Oracle Exadata Database Service on Dedicated Infrastructure Event Types
The events in this section are emitted by the cloud Exadata infrastructure resource - Oracle Exadata Database Service on Dedicated Infrastructure Maintenance Event Types
The events in this section are emitted by the cloud Exadata infrastructure resource for Maintenance Events - Exadata Cloud Infrastructure Critical and Information Event Types
Exadata Cloud Infrastructure infrastructure resources emit "critical" and "information" data plane events that allow you to receive notifications when your infrastructure resource needs attention. - Exadata Cloud Infrastructure VM Cluster Event Types
Review the list of events that can be emitted by VM Cluster - VM Node Subsetting Event Types
Review the list of event types that VM Node Subsetting emits. - Data Guard Event Types
Review the list of event types that Data Guard group and Data Guard Associations emit. - Oracle Database Home Event Types
Review the list of events emitted by Oracle Database Homes. - Database Event Types
These are the event types that Oracle Databases in Exadata Cloud Service instances emit. - Pluggable Database Event Types
These are the event types that Oracle pluggable databases in Oracle Cloud Infrastructure emit. - Database Service Events
The Database Service emits events, which are structured messages that indicate changes in resources. - Application VIP Event Types
These are the event types that Application VIPs in Oracle Cloud Infrastructure emit. - Interim Software Updates Event Types
These are the event types that Interim Software Updates in Oracle Cloud Infrastructure emit. - Serial Console Connection Event Types
Review the list of event types that serial console connection emits.
Parent topic: Reference Guides for Exadata Cloud Infrastructure
About Event Types on Exadata Cloud Infrastructure
Learn about the event types available for Exadata Cloud Infrastructure resources.
Exadata Cloud Infrastructure resources emit events, which are structured messages that indicate changes in resources. For more information about Oracle Cloud Infrastructure Events, see Overview of Events. You may subscribe to events and be notified when they occur using the Oracle Notification service, see Notifications Overview.
Related Topics
Prerequisites for Event Service
The following prerequisites are required for the Events to flow out of the VM Cluster.
The Event Service requires the following:
- Events on the VM Cluster depends on Oracle Trace File Analyzer (TFA) agent. Ensure that these components are up and running. AHF version 22.2.2 or higher is required for capturing events from the VM Cluster. To start, stop, or check the status of TFA, see Incident Logs and Trace Files . To enable AHF Telemetry for the VM Cluster using the dbcli ulitilty, see AHF Telemetry Commands
- The following network configurations are required.
- Egress rules for outgoing traffic: The default egress rules are
sufficient to enable the required network path : For more information, see
Default Security List .If you have
blocked the outgoing traffic by modifying the default egress rules on your
Virtual Cloud Network(VCN), you will need to revert the settings to allow
outgoing traffic. The default egress rule allowing outgoing traffic (as
shown in Security Rules for the Oracle Exadata
Database Service on Dedicated Infrastructure) is as follows:
- Stateless: No (all rules must be stateful)
- Destination Type: CIDR
-
Destination CIDR: All <region> Services in Oracle Services Network
-
IP Protocol: TCP
- Destination Port: 443 (HTTPS)
- Public IP or Service Gateway: The database server host must have
either a public IP address or a service gateway to be able to send database
server host metrics to the Monitoring service.
If the instance does not have a public IP address, set up a service gateway on the virtual cloud network (VCN). The service gateway lets the instance send database server host metrics to the Monitoring service without the traffic going over the internet. Here are special notes for setting up the service gateway to access the Monitoring service:
- When creating the service gateway, enable the service label called All <region> Services in Oracle Services Network. It includes the Monitoring service.
-
When setting up routing for the subnet that contains the instance, set up a route rule with Target Type set to Service Gateway, and the Destination Service set to All <region> Services in Oracle Services Network.
For detailed instructions, see Access to Oracle Services: Service Gateway.
- Egress rules for outgoing traffic: The default egress rules are
sufficient to enable the required network path : For more information, see
Default Security List .If you have
blocked the outgoing traffic by modifying the default egress rules on your
Virtual Cloud Network(VCN), you will need to revert the settings to allow
outgoing traffic. The default egress rule allowing outgoing traffic (as
shown in Security Rules for the Oracle Exadata
Database Service on Dedicated Infrastructure) is as follows:
Related Topics
Oracle Exadata Database Service on Dedicated Infrastructure Event Types
The events in this section are emitted by the cloud Exadata infrastructure resource
Exadata systems that use the old DB system resource model are deprecated and will be desupported in a future release. The DB system event are not described.
| Friendly Name | Event Type |
|---|---|
| Cloud Exadata Infrastructure - Create Begin | com.oraclecloud.databaseservice.createcloudexadatainfrastructure.begin |
| Cloud Exadata Infrastructure - Create End | com.oraclecloud.databaseservice.createcloudexadatainfrastructure.end |
| Cloud Exadata Infrastructure - Change Compartment Begin |
com.oraclecloud.databaseservice.changecloudexadatainfrastructurecompartment.begin
|
| Cloud Exadata Infrastructure - Change Compartment End |
com.oraclecloud.databaseservice.changecloudexadatainfrastructurecompartment.end
|
| Cloud Exadata Infrastructure - Critical
See Exadata Cloud Service Infrastructure Critical and Information Event Types for details |
com.oraclecloud.databaseservice.cloudexadatainfrastructure.critical
|
| Cloud Exadata Infrastructure - Delete Begin |
com.oraclecloud.databaseservice.deletecloudexadatainfrastructure.begin
|
| Cloud Exadata Infrastructure - Delete End |
com.oraclecloud.databaseservice.deletecloudexadatainfrastructure.end
|
| Cloud Exadata Infrastructure - Information
See Exadata Cloud Service Infrastructure Critical and Information Event Types for details |
com.oraclecloud.databaseservice.cloudexadatainfrastructure.information
|
| Cloud Exadata Infrastructure - Update Begin |
com.oraclecloud.databaseservice.updatecloudexadatainfrastructure.begin
|
| Cloud Exadata Infrastructure - Update End |
com.oraclecloud.databaseservice.updatecloudexadatainfrastructure.end
|
This is a reference event for a Cloud Exadata Infrastructure resource:
{
"cloudEventsVersion": "0.1",
"eventId": "<unique_ID>",
"eventType": "com.oraclecloud.databaseservice.cloudexadatainfrastructuremaintenance.end",
"source": "DatabaseService",
"eventTypeVersion": "1.0",
"eventTime": "2019-06-27T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1.<unique_ID>"
},
"data": {
"compartmentId": "ocid1.compartment.oc1.<unique_ID>",
"compartmentName": "example_name",
"resourceName": "my_exadata_infrastructure",
"resourceId": "ocid1.dbsystem.oc1.eu-frankfurt-1.<unique_ID>", ,
"availabilityDomain": "tXPJ:EU-FRANKFURT-1-AD-3",
"freeFormTags": {
"Department": "Finance"
},
"definedTags": {
"Operations": {
"CostCenter": "42"
}
},
"additionalDetails" : {
"subnetId" : "ocid1.subnet.oc1.eu-frankfurt-1.<unique_ID>",
"lifecycleState" : "MAINTENANCE_IN_PROGRESS",
"sshPublicKeys" : "...",
"cpuCoreCount" : 32,
"version" : "19.2.8.0.0.191119",
"nsgIds" : "null",
"backupSubnetId" : "ocid1.subnet.oc1.eu-frankfurt-1.<unique_ID>",
"licenseType" : "BRING_YOUR_OWN_LICENSE",
"dataStoragePercentage" : 80,
"patchHistoryEntries" : "null",
"lifecycleMessage" : "The underlying infrastructure of this system (cell storage) is being updated and this will not impact database
availability.",
"exadataIormConfig" : "ExadataIormConfigCache(lifecycleState=DISABLED, lifeCycleDetails=null, objective=Auto,
dbPlans=[DbIormConfigCache(dbName=default, share=null, flashCacheLimit=null), DbIormConfigCache(dbName=<my_database1>,
share=null, flashCacheLimit=null), DbIormConfigCache(dbName=<my_database2>, share=null, flashCacheLimit=null),
DbIormConfigCache(dbName=<my_database3>, share=null, flashCacheLimit=null), DbIormConfigCache(dbName=<my_database4>,
share=null, flashCacheLimit=null), DbIormConfigCache(dbName=<my_database5>, share=null, flashCacheLimit=null),
DbIormConfigCache(dbName=<my_database6>, share=null, flashCacheLimit=null), DbIormConfigCache(dbName=<my_database7>,
share=null, flashCacheLimit=null), DbIormConfigCache(dbName=<my_database8>, share=null, flashCacheLimit=null),
DbIormConfigCache(dbName=<my_database9>, share=null, flashCacheLimit=null), DbIormConfigCache(dbName=<my_database10>,
share=null, flashCacheLimit=null), DbIormConfigCache(dbName=<my_database11>, share=null, flashCacheLimit=null)],
undoData=null)"
}
},
"eventID" : "<unique_ID>",
"extensions" : {
"compartmentId" : "ocid1.compartment.oc1.<unique_ID>"
}
}This is a reference event for Cloud Exadata Infrastructure - Add Storage Capacity Begin:
{
"id": "ocid1.eventschema.oc1.phx.z1nzw5klc4r7ar1vkxunfvyfhtwmeaaylr0j5hjnu2j5uozwliexa53gwlk4",
"serviceName": "Database",
"displayName": "Cloud Exadata Infrastructure - Add Storage Capacity Begin",
"eventType": "com.oraclecloud.databaseservice.addstoragecapacitycloudexadatainfrastructure.begin",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2023-01-06T21:16:04.000Z",
"contentType": "application/json",
"additionalDetails": [
{
"name": "timeCreated",
"type": "string"
},
{
"name": "timeUpdated",
"type": "string"
},
{
"name": "lifecycleState",
"type": "string"
},
{
"name": "lifecycleDetails",
"type": [
"null",
"string"
]
},
{
"name": "shape",
"type": "string"
},
{
"name": "message",
"type": [
"null",
"string"
]
},
{
"name": "description",
"type": [
"null",
"string"
]
},
{
"name": "timeZone",
"type": [
"null",
"string"
]
},
{
"name": "maintenanceMode",
"type": [
"null",
"string"
]
},
{
"name": "maintenanceSubType",
"type": [
"null",
"string"
]
}
],
"exampleEvent": {
"eventType": "com.oraclecloud.databaseservice.addstoragecapacitycloudexadatainfrastructure.begin",
"cloudEventsVersion": "0.1",
"eventTypeVersion": "2.0",
"source": "databaseservice",
"eventID": "10274771-3706-4624-99d1-e036805a9ca7",
"eventTime": "2023-01-06T21:16:04.000Z",
"contentType": "application/json",
"data": {
"eventGroupingId": "csida87218404b4291914305ec7a5a86/d53ffb13f83244bbbfb8c7d0a8f0e2eb/FB95D76D5123C152C25DBF288489077F",
"eventName": "AddStorageCapacityCloudExadataInfrastructure",
"compartmentId": "ocid1.compartment.oc1.....unique_id",
"compartmentName": null,
"resourceName": "my_cloud_exadata_infrastructure",
"resourceId": "ocid1.cloudexadatainfrastructure.oc1.....unique_id",
"resourceVersion": null,
"availabilityDomain": "",
"tagSlug": "tag_slug",
"identity": {
"principalName": null,
"principalId": null,
"authType": null,
"callerName": null,
"callerId": null,
"tenantId": null,
"ipAddress": null,
"credentials": null,
"authZPolicies": null,
"userGroups": null,
"userAgent": null,
"consoleSessionId": null
},
"request": {
"id": "7e83c538-28bf-453d-9fb7-125bf70546c4",
"path": null,
"action": null,
"parameters": null,
"headers": null
},
"response": {
"status": null,
"responseTime": null,
"headers": null,
"payload": null,
"message": null
},
"stateChange": {
"previous": null,
"current": {
"lifecycleState": "AVAILABLE",
"shape": "Exadata.X9M",
"displayName": "my_display_name",
"freeTags": {},
"definedTags": {}
}
},
"additionalDetails": {
"timeCreated": "2023-01-06T21:16:04.000Z",
"timeUpdated": "2023-01-06T21:16:04.000Z",
"lifecycleState": "AVAILABLE",
"lifecycleDetails": null,
"description": null,
"message": null,
"shape": "Exadata.X9M",
"timeZone": null,
"maintenanceMode": null,
"maintenanceSubType": null
},
"internalDetails": {
"attributes": null
}
}
},
"timeCreated": "2023-01-06T21:16:04.000Z"
}This is a reference event for Cloud Exadata Infrastructure - Add Storage Capacity End:
{
"id": "ocid1.eventschema.oc1.phx.4aeklze2co1ynub2ojmu49shhduq9gh5qg6fvudm7h77w3og8sfkau6a3not",
"serviceName": "Database",
"displayName": "Cloud Exadata Infrastructure - Add Storage Capacity End",
"eventType": "com.oraclecloud.databaseservice.addstoragecapacitycloudexadatainfrastructure.end",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2023-01-06T21:16:04.000Z",
"contentType": "application/json",
"additionalDetails": [
{
"name": "timeCreated",
"type": "string"
},
{
"name": "timeUpdated",
"type": "string"
},
{
"name": "lifecycleState",
"type": "string"
},
{
"name": "lifecycleDetails",
"type": [
"null",
"string"
]
},
{
"name": "shape",
"type": "string"
},
{
"name": "message",
"type": [
"null",
"string"
]
},
{
"name": "description",
"type": [
"null",
"string"
]
},
{
"name": "timeZone",
"type": [
"null",
"string"
]
},
{
"name": "maintenanceMode",
"type": [
"null",
"string"
]
},
{
"name": "maintenanceSubType",
"type": [
"null",
"string"
]
}
],
"exampleEvent": {
"eventType": "com.oraclecloud.databaseservice.addstoragecapacitycloudexadatainfrastructure.end",
"cloudEventsVersion": "0.1",
"eventTypeVersion": "2.0",
"source": "databaseservice",
"eventID": "b12abcc0-110a-9120-aab5-9a34bc799e72",
"eventTime": "2023-01-06T21:16:04.000Z",
"contentType": "application/json",
"data": {
"eventGroupingId": "csida2cd1c8442f9b9fc16354a1f0912/95202d41125e4ce18e8dd52fa9f57f5e/545A43343BC1D5020A85AA2919C06E25",
"eventName": "AddStorageCapacityCloudExadataInfrastructure",
"compartmentId": "ocid1.compartment.oc1.....unique_id",
"compartmentName": null,
"resourceName": "my_cloud_exadata_infrastructure",
"resourceId": "ocid1.cloudexadatainfrastructure.oc1.....unique_id",
"resourceVersion": null,
"availabilityDomain": "",
"tagSlug": "tag_slug",
"identity": {
"principalName": null,
"principalId": null,
"authType": null,
"callerName": null,
"callerId": null,
"tenantId": null,
"ipAddress": null,
"credentials": null,
"authZPolicies": null,
"userGroups": null,
"userAgent": null,
"consoleSessionId": null
},
"request": {
"id": "111b9da5-a7a7-4aca-bd05-a51558f7df55",
"path": null,
"action": null,
"parameters": null,
"headers": null
},
"response": {
"status": null,
"responseTime": null,
"headers": null,
"payload": null,
"message": null
},
"stateChange": {
"previous": null,
"current": {
"lifecycleState": "AVAILABLE",
"shape": "Exadata.X9M",
"displayName": "my_display_name",
"freeTags": {},
"definedTags": {}
}
},
"additionalDetails": {
"timeCreated": "2023-01-06T21:16:04.000Z",
"timeUpdated": "2023-01-06T21:16:04.000Z",
"lifecycleState": "AVAILABLE",
"lifecycleDetails": null,
"description": null,
"message": null,
"shape": "Exadata.X9M",
"timeZone": null,
"maintenanceMode": null,
"maintenanceSubType": null
},
"internalDetails": {
"attributes": null
}
}
},
"timeCreated": "2023-01-06T21:16:04.000Z"
}This is a reference event for Cloud Exadata Infrastructure - Update Begin
{
"id": "ocid1.eventschema.oc1.phx.jlx9t3z6igwglicpbba6xs1uaewcb8txsegnuykc65n8rxl5tqd26ect7i3f",
"serviceName": "Database",
"displayName": "Cloud Exadata Infrastructure - Update Begin",
"eventType": "com.oraclecloud.databaseservice.updatecloudexadatainfrastructure.begin",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2019-06-27T21:16:04.000Z",
"contentType": "application/json",
"additionalDetails": [
{
"name": "id",
"type": "string"
},
{
"name": "defineTags",
"type": [
"null",
"Map<String, Map<String, Object>>"
]
},
{
"name": "freeFormTags",
"type": [
"null",
"Map<String, String>"
]
},
{
"name": "timeCreated",
"type": "string"
},
{
"name": "timeUpdated",
"type": "string"
},
{
"name": "lifecycleState",
"type": "string"
},
{
"name": "lifecycleDetails",
"type": [
"null",
"string"
]
},
{
"name": "compartmentId",
"type": [
"null",
"string"
]
},
{
"name": "availabilityDomain",
"type": [
"null",
"string"
]
},
{
"name": "description",
"type": [
"null",
"string"
]
},
{
"name": "tenantId",
"type": [
"null",
"string"
]
},
{
"name": "message",
"type": [
"null",
"string"
]
},
{
"name": "shape",
"type": [
"null",
"String"
]
},
{
"name": "timeZone",
"type": [
"null",
"string"
]
}
],
"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "b28fcda6-3d7b-4044-aa8e-7c21cde84b44",
"eventType": "com.oraclecloud.databaseservice.updatecloudexadatainfrastructure.begin",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2019-06-27T21:16:04.000Z",
"contentType": "application/json",
"data": {
"eventGroupingId": "4976b940-2c2d-4380-a669-1d70d071b187",
"eventName": "UpdateCloudExadataInfrastructure",
"compartmentName": "example_compartment",
"resourceName": "my_container_database",
"resourceId": "ocid1.cloudexadatainfrastructure.oc1.....unique_id",
"resourceVersion": null,
"additionalDetails": {
"availabilityDomain": "all",
"compartmentId": "ocid1.compartment.oc1.......unique_id",
"freeFormTags": {},
"definedTags": {},
"lifecycleState": "AVAILABLE"
}
}
},
"timeCreated": "2020-06-15T16:31:31.979Z"
}
This is a reference event for Cloud Exadata Infrastructure - Update End
{
"id": "ocid1.eventschema.oc1.phx.aq2fuvh1nh9h71bnyclhmsuj3bky7dr304xj7nejajjzwbnh2n40zy3tdand",
"serviceName": "Database",
"displayName": "Cloud Exadata Infrastructure - Update End",
"eventType": "com.oraclecloud.databaseservice.updatecloudexadatainfrastructure.end",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2019-06-27T21:16:04.000Z",
"contentType": "application/json",
"additionalDetails": [
{
"name": "id",
"type": "string"
},
{
"name": "defineTags",
"type": [
"null",
"Map<String, Map<String, Object>>"
]
},
{
"name": "freeFormTags",
"type": [
"null",
"Map<String, String>"
]
},
{
"name": "timeCreated",
"type": "string"
},
{
"name": "timeUpdated",
"type": "string"
},
{
"name": "lifecycleState",
"type": "string"
},
{
"name": "lifecycleDetails",
"type": [
"null",
"string"
]
},
{
"name": "compartmentId",
"type": [
"null",
"string"
]
},
{
"name": "availabilityDomain",
"type": [
"null",
"string"
]
},
{
"name": "description",
"type": [
"null",
"string"
]
},
{
"name": "tenantId",
"type": [
"null",
"string"
]
},
{
"name": "message",
"type": [
"null",
"string"
]
},
{
"name": "shape",
"type": [
"null",
"String"
]
},
{
"name": "timeZone",
"type": [
"null",
"string"
]
}
],
"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "b28fcda6-3d7b-4044-aa8e-7c21cde84b44",
"eventType": "com.oraclecloud.databaseservice.updatecloudexadatainfrastructure.end",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2019-06-27T21:16:04.000Z",
"contentType": "application/json",
"data": {
"eventGroupingId": "4976b940-2c2d-4380-a669-1d70d071b187",
"eventName": "UpdateCloudExadataInfrastructure",
"compartmentName": "example_compartment",
"resourceName": "my_container_database",
"resourceId": "ocid1.dbsystem-.....unique_id",
"resourceVersion": null,
"additionalDetails": {
"availabilityDomain": "all",
"compartmentId": "ocid1.compartment.oc1.......unique_id",
"freeFormTags": {},
"definedTags": {},
"lifecycleState": "AVAILABLE"
}
}
},
"timeCreated": "2020-06-15T16:31:31.979Z"
}
Oracle Exadata Database Service on Dedicated Infrastructure Maintenance Event Types
The events in this section are emitted by the cloud Exadata infrastructure resource for Maintenance Events
Exadata systems that use the old DB system resource model are deprecated and will be desupported in a future release. The DB system event are not described.
| Friendly Name | Event Type | Event Messages |
|---|---|---|
|
Cloud Exadata Infrastructure - Maintenance Reminder |
|
This is an Oracle Cloud Operations notification for quarterly maintenance update of your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> part of Maintenance Run <mr-display-name>, OCID <mr-ocid> in approximately You will get a notification on the start of the quarterly maintenance update. |
|
Cloud Exadata Infrastructure - Maintenance Begin |
|
This is an Oracle Cloud Operations notification for quarterly maintenance update of your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> part of Maintenance Run <mr-display-name>, OCID <mr-ocid>. Your maintenance update started at <start-time>. You will get a notification on the completion of the quarterly maintenance update. |
|
Cloud Exadata Infrastructure - Maintenance End |
|
Success: This is an Oracle Cloud Operations notification for quarterly maintenance update of your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> part of Maintenance Run <mr-display-name>, OCID <mr-ocid>. Your maintenance update started at <start-time> and was completed successfully at <end-time>. You have successfully completed maintenance updates for this window. Failed: This is an Oracle Cloud Operations notification for quarterly maintenance update of your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> part of Maintenance Run <mr-display-name>, OCID <mr-ocid>. Your maintenance update started at <start-time> and was failed to complete successfully as planned. Our operations team is evaluating the failure and will notify you of the next steps to complete the maintenance update for this quarter. Canceled: This is an Oracle Cloud Operations notification for quarterly maintenance update of your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> part of Maintenance Run <mr-display-name>, OCID <mr-ocid>. Your maintenance update started at <start-time>. Your maintenance has been canceled as requested. And a new window will be created according to the time given. Duration Exceeded: This is an Oracle Cloud Operations notification for quarterly maintenance update of your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> part of Maintenance Run <mr-display-name>, OCID<mr-ocid>. Your maintenance update started at <start-time>. Your window was configured for a Your maintenance is taking longer than the configured window duration. This window has duration enforcement enabled. Oracle automation will reschedule all updates that have not started to a future maintenance window. Please acknowledge the updates rescheduled to run in a future unplanned maintenance window created by Oracle. |
|
Cloud Exadata Infrastructure - Maintenance Custom action time Begin (ROLLING) |
|
This is an Oracle Cloud Operations notification for custom action time configured for your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> for Database Server <db-server-name>, OCID <db-server-ocid>. Your custom action time started at <start-time>. You will get a notification on the completion of the custom action time for the Database Server. |
|
Cloud Exadata Infrastructure - Maintenance Custom action time End (ROLLING) |
|
This is an Oracle Cloud Operations notification for custom action time configured for your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> for Database Server <db-server-name>, OCID <db-server-ocid>. Your custom action time started at <start-time> ended at <end-time>. |
|
Cloud Exadata Infrastructure - Maintenance Custom action time Begin (NONROLLING) |
|
This is an Oracle Cloud Operations notification for custom action time configured for your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> for Database Servers <db-server-name>, OCID <dbserver-ocid> | <db-server-name>, OCID <dbserver-ocid>. Your custom action time started at <start-time>. You will get a notification on the completion of the custom action time for the Database Servers. |
|
Cloud Exadata Infrastructure - Maintenance Custom action time End (NONROLLING) |
|
This is an Oracle Cloud Operations notification for custom action time configured for your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> for Database Servers <db-server-name>, OCID <dbserver-ocid> | <db-server-name>, OCID <dbserver-ocid>. Your custom action time started at <start-time> ended at <end-time>. |
|
Cloud Exadata Infrastructure - maintenance Storage servers Start |
|
This is an Oracle Cloud Operations notification for quarterly maintenance update of the Storage Servers of your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> for Storage Server(s) count <cell-count>. Your maintenance update started at <start-time>. You will get a notification on the completion of the quarterly maintenance update for the Storage Servers. |
|
Cloud Exadata Infrastructure - maintenance Storage servers End |
|
This is an Oracle Cloud Operations notification for quarterly maintenance update of the Storage Servers of your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> for Storage Server(s) count <cell-count>. Your maintenance update started at <start-time> and was completed successfully at <end-time>. |
|
Cloud Exadata Infrastructure - maintenance Database Servers Start (ROLLING) |
|
This is an Oracle Cloud Operations notification for quarterly maintenance update of the Database Server component of your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> for Database Server <db-server-name>, OCID <db-server-ocid>. Your maintenance update started at <start-time>. You will get a notification on the completion of the quarterly maintenance update for the Database Server. |
|
Cloud Exadata Infrastructure - maintenance Database Servers End (ROLLING) |
com.oraclecloud.databaseservice.cloudexadatainfrastructuremaintenancedbservers.end |
This is an Oracle Cloud Operations notification for quarterly maintenance update of the Database Server component of your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> for Database Server <db-server-name>, OCID <db-server-ocid>. Your maintenance update started at <start-time> and was completed successfully at <end-time>. |
|
Cloud Exadata Infrastructure - maintenance Database Servers Start (NONROLLING) |
|
This is an Oracle Cloud Operations notification for quarterly maintenance update of the Database Server component of your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> for Database Servers <db-server-name>, OCID <dbserver-ocid> | <db-server-name>, OCID <dbserver-ocid>. Your maintenance update started at <start-time>. You will get a notification on the completion of the quarterly maintenance update for the Database Servers. |
|
Cloud Exadata Infrastructure - maintenance Database Servers End (NONROLLING) |
com.oraclecloud.databaseservice.cloudexadatainfrastructuremaintenancedbservers.end |
This is an Oracle Cloud Operations notification for quarterly maintenance update of the Database Server component of your ExaDB-D Exadata Infrastructure <infra-name>, OCID <infra-ocid> for Database Servers <db-server-name>, OCID <dbserver-ocid> | <db-server-name>, OCID <dbserver-ocid>. Your maintenance update started at <start-time> and was completed successfully at <end-time>. |
Exadata Cloud Infrastructure Critical and Information Event Types
Exadata Cloud Infrastructure infrastructure resources emit "critical" and "information" data plane events that allow you to receive notifications when your infrastructure resource needs attention.
Exadata Cloud Service infrastructure resources emit "critical" and "information" data plane events that allow you to receive notifications when your infrastructure resource needs urgent attention ("critical" events), or notifications for events that are not critical, but which you may want to monitor ("information" events). The eventType values for these events are the following:
com.oraclecloud.databaseservice.exadatainfrastructure.criticalcom.oraclecloud.databaseservice.exadatainfrastructure.information
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" : "HEALTH.INFRASTRUCTURE.CELL.SQL_QUARANTINE",
"quarantineMode" : "\"FULL Quarantine\""
....
}
},
"eventID" : "<unique_ID>",
....
}
}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.
Critical events for Exadata Cloud Service infrastructure:
| Critical Event - EventName | Description |
|---|---|
HEALTH.INFRASTRUCTURE.CELL.SQL_QUARANTINE |
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:
|
Informational events for Exadata Cloud Service infrastructure:
| Information Event - EventName | Description |
|---|---|
HEALTH.INFRASTRUCTURE.CELL.FLASH_DISK_FAILURE |
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. |
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 SQL statement that was terminated by Oracle Database
Resource Manager because it was consuming excessive CPU or I/O resources. The
eventName and description fields within the
additionalDetails section provide information regarding the
critical situation:
{
"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" : "HEALTH.INFRASTRUCTURE.CELL.SQL_QUARANTINE",
"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>"
}
}In the following example of an "information" event, you can see within
the additionalDetails section of the event message that this
particular message concerns a flash disk failure that is being investigated by the
Oracle Exadata operations team. The eventName and
description fields within the
additionalDetails section provide information regarding the
event:
{
"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" : "HEALTH.INFRASTRUCTURE.CELL.FLASH_DISK_FAILURE",
"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"
}
}
Exadata Cloud Infrastructure VM Cluster Event Types
Review the list of events that can be emitted by VM Cluster
| Friendly Name | Event Type |
|---|---|
| Cloud VM Cluster - Change Compartment Begin | com.oraclecloud.databaseservice.changecloudvmclustercompartment.begin |
| Cloud VM Cluster - Change Compartment End | com.oraclecloud.databaseservice.changecloudvmclustercompartment.end |
| Cloud VM Cluster - Create Begin | com.oraclecloud.databaseservice.createcloudvmcluster.begin |
| Cloud VM Cluster - Create End | com.oraclecloud.databaseservice.createcloudvmcluster.end |
| Cloud VM Cluster - Delete Begin | com.oraclecloud.databaseservice.deletecloudvmcluster.begin |
| Cloud VM Cluster - Delete End | com.oraclecloud.databaseservice.deletecloudvmcluster.end |
| Cloud VM Cluster - Update Begin | com.oraclecloud.databaseservice.updatecloudvmcluster.begin |
| Cloud VM Cluster - Update End | com.oraclecloud.databaseservice.updatecloudvmcluster.end |
| Cloud VM Cluster - Update IORM Configuration Begin | com.oraclecloud.databaseservice.updatecloudvmclusteriormconfig.begin |
| Cloud VM Cluster - Update IORM Configuration End | com.oraclecloud.databaseservice.updatecloudvmclusteriormconfig.end |
| Cloud VM Cluster - Add Virtual Machine Begin | com.oraclecloud.databaseservice.cloudvmclusteraddvirtualmachine.begin |
| Cloud VM Cluster - Add Virtual Machine End | com.oraclecloud.databaseservice.cloudvmclusteraddvirtualmachine.end |
This is a reference event for a cloud VM cluster resource:
{
"cloudEventsVersion": "0.1",
"eventID": "<unique_ID>",
"eventType": "com.oraclecloud.databaseservice.updatecloudvmclusteriormconfig.begin",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2022-06-27T21:16:04.000Z",
"contentType": "application/json",
"data": {
"eventGroupingId": "<unique_ID>",
"eventName": "UpdateCloudVmClusterIormConfig",
"compartmentName": "example_compartment",
"resourceName": "my_container_database",
"resourceId": "ocid1.cloudvmcluster.oc1.<unique_ID>",
"resourceVersion": null,
"additionalDetails": {
"cloudExadataInfrastructureId": "ocid1.cloudexadatainfrastructure.oc1.<unique_ID>",
"freeFormTags": {},
"definedTags": {},
"licenseType": "BRING_YOUR_OWN_LICENSE",
"lifecycleState": "AVAILABLE",
"giVersion": "19.0.0.0.0",
"cpuCoreCount": 16
}
}
},
"timeCreated": "2022-06-15T16:31:31.979Z"
}This is a reference event for Add Virtual Machine Begin:
{
"id": "ocid1.eventschema.oc1.phx.n2p4ijm0jyuia5p6lzhps0axtqft2d2ueywaq4oxcr3ywlzt9jd689kvxazo",
"serviceName": "Database",
"displayName": "Cloud VM Cluster - Add Virtual Machine Begin",
"eventType": "com.oraclecloud.databaseservice.cloudvmclusteraddvirtualmachine.begin",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2023-01-06T21:16:04.000Z",
"contentType": "application/json",
"additionalDetails": [
{
"name": "timeCreated",
"type": "string"
},
{
"name": "timeUpdated",
"type": "string"
},
{
"name": "lifecycleState",
"type": "string"
},
{
"name": "lifecycleDetails",
"type": [
"null",
"string"
]
},
{
"name": "cloudExadataInfrastructureId",
"type": [
"null",
"string"
]
},
{
"name": "cpuCoreCount",
"type": [
"null",
"Integer"
]
},
{
"name": "ocpuCountFractional",
"type": [
"null",
"Float"
]
},
{
"name": "dataStorageSizeInTBs",
"type": [
"null",
"Integer"
]
},
{
"name": "dataStorageSizeInGBs",
"type": [
"null",
"Integer"
]
},
{
"name": "licenseType",
"type": [
"null",
"string"
]
},
{
"name": "giVersion",
"type": [
"null",
"string"
]
},
{
"name": "dbNodeIds",
"type": [
"null",
"string"
]
},
{
"name": "timeZone",
"type": [
"null",
"string"
]
}
],
"exampleEvent": {
"eventType": "com.oraclecloud.databaseservice.cloudvmclusteraddvirtualmachine.begin",
"cloudEventsVersion": "0.1",
"eventTypeVersion": "2.0",
"source": "databaseservice",
"eventID": "bc78609a-783a-9034-ccd1-12ab908df913",
"eventTime": "2023-01-06T23:18:04.000Z",
"contentType": "application/json",
"data": {
"eventGroupingId": "csid201fe4f3443a853d76e9cec3ef4a/3200918f142a44adb715d8aaf4f5ba99/DC62865A826A6E98699590E7F33C5064",
"eventName": "CloudVmClusterAddVirtualMachine",
"compartmentId": "ocid1.compartment.oc1.....unique_id",
"compartmentName": null,
"resourceName": "my_cloud_vm_cluster",
"resourceId": "ocid1.cloudvmcluster.oc1.....unique_id",
"resourceVersion": null,
"availabilityDomain": "",
"tagSlug": "tag_slug",
"identity": {
"principalName": null,
"principalId": null,
"authType": null,
"callerName": null,
"callerId": null,
"tenantId": null,
"ipAddress": null,
"credentials": null,
"authZPolicies": null,
"userGroups": null,
"userAgent": null,
"consoleSessionId": null
},
"request": {
"id": "01858321-0045-4bc5-b0d9-a917a6a40901",
"path": null,
"action": null,
"parameters": null,
"headers": null
},
"response": {
"status": null,
"responseTime": null,
"headers": null,
"payload": null,
"message": null
},
"stateChange": {
"previous": null,
"current": {
"licenseType": "BRING_YOUR_OWN_LICENSE",
"dataStorageSizeGb": 60,
"lifecycleState": "AVAILABLE",
"sshPublicKeys": "...",
"displayName": "my_cloud_vm_cluster",
"cpuCoreCount": 16,
"freeTags": {},
"definedTags": {},
"ocpuCountFractional": 16.0
}
},
"additionalDetails": {
"timeCreated": "2023-01-06T22:18:04.000Z",
"timeUpdated": "2023-01-06T22:20:04.000Z",
"lifecycleState": "AVAILABLE",
"lifecycleDetails": null,
"cloudExadataInfrastructureId": "ocid1.cloudexadatainfrastructure.oc1.....unique_id",
"cpuCoreCount": 16,
"ocpuCountFractional": 16.0,
"dataStorageSizeInTBs": 4,
"dataStorageSizeInGBs": 60,
"licenseType": "BRING_YOUR_OWN_LICENSE",
"giVersion": "19.0.0.0.0",
"dbNodeIds": "[ocid1.dbnode.oc1.....unique_id,...]",
"timeZone": "UTC"
},
"internalDetails": {
"attributes": null
}
}
},
"timeCreated": "2023-01-06T23:18:04.000Z"
}
This is a reference event for Add Virtual Machine End:
{
"id": "ocid1.eventschema.oc1.phx.v87pke1z9k9u6xaqo51taf6bunf0gc2wyhrbmjzbh3h1pjwakavmf2borxgb",
"serviceName": "Database",
"displayName": "Cloud VM Cluster - Add Virtual Machine End",
"eventType": "com.oraclecloud.databaseservice.cloudvmclusteraddvirtualmachine.end",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2023-01-06T21:16:04.000Z",
"contentType": "application/json",
"additionalDetails": [
{
"name": "timeCreated",
"type": "string"
},
{
"name": "timeUpdated",
"type": "string"
},
{
"name": "lifecycleState",
"type": "string"
},
{
"name": "lifecycleDetails",
"type": [
"null",
"string"
]
},
{
"name": "cloudExadataInfrastructureId",
"type": [
"null",
"string"
]
},
{
"name": "cpuCoreCount",
"type": [
"null",
"Integer"
]
},
{
"name": "ocpuCountFractional",
"type": [
"null",
"Float"
]
},
{
"name": "dataStorageSizeInTBs",
"type": [
"null",
"Integer"
]
},
{
"name": "dataStorageSizeInGBs",
"type": [
"null",
"Integer"
]
},
{
"name": "licenseType",
"type": [
"null",
"string"
]
},
{
"name": "giVersion",
"type": [
"null",
"string"
]
},
{
"name": "dbNodeIds",
"type": [
"null",
"string"
]
},
{
"name": "timeZone",
"type": [
"null",
"string"
]
}
],
"exampleEvent": {
"eventType": "com.oraclecloud.databaseservice.cloudvmclusteraddvirtualmachine.end",
"cloudEventsVersion": "0.1",
"eventTypeVersion": "2.0",
"source": "databaseservice",
"eventID": "ced78bb7-3903-acd8-ff78-5567aa01a912",
"eventTime": "2023-01-06T23:18:04.000Z",
"contentType": "application/json",
"data": {
"eventGroupingId": "csid89a04ef74ccb8b48340f56e656cf/729c99d3e5a34d548ddc31c054810454/634F086E8618E0A660946A6862C82A68",
"eventName": "CloudVmClusterAddVirtualMachine",
"compartmentId": "ocid1.compartment.oc1.....unique_id",
"compartmentName": null,
"resourceName": "my_cloud_vm_cluster",
"resourceId": "ocid1.cloudvmcluster.oc1.....unique_id",
"resourceVersion": null,
"availabilityDomain": "",
"tagSlug": "tag_slug",
"identity": {
"principalName": null,
"principalId": null,
"authType": null,
"callerName": null,
"callerId": null,
"tenantId": null,
"ipAddress": null,
"credentials": null,
"authZPolicies": null,
"userGroups": null,
"userAgent": null,
"consoleSessionId": null
},
"request": {
"id": "07197e12-b680-475e-851e-bb89fcd8376d",
"path": null,
"action": null,
"parameters": null,
"headers": null
},
"response": {
"status": null,
"responseTime": null,
"headers": null,
"payload": null,
"message": null
},
"stateChange": {
"previous": null,
"current": {
"licenseType": "BRING_YOUR_OWN_LICENSE",
"dataStorageSizeGb": 60,
"lifecycleState": "AVAILABLE",
"sshPublicKeys": "...",
"displayName": "my_cloud_vm_cluster",
"cpuCoreCount": 16,
"freeTags": {},
"definedTags": {},
"ocpuCountFractional": 16.0
}
},
"additionalDetails": {
"timeCreated": "2023-01-06T22:18:04.000Z",
"timeUpdated": "2023-01-06T22:20:04.000Z",
"lifecycleState": "AVAILABLE",
"lifecycleDetails": null,
"cloudExadataInfrastructureId": "ocid1.cloudexadatainfrastructure.oc1.....unique_id",
"cpuCoreCount": 16,
"ocpuCountFractional": 16.0,
"dataStorageSizeInTBs": 4,
"dataStorageSizeInGBs": 60,
"licenseType": "BRING_YOUR_OWN_LICENSE",
"giVersion": "19.0.0.0.0",
"dbNodeIds": "[ocid1.dbnode.oc1.....unique_id,...]",
"timeZone": "UTC"
},
"internalDetails": {
"attributes": null
}
}
},
"timeCreated": "2023-01-06T23:18:04.000Z"
}
This is a reference event for Cloud VM Cluster - Update Begin:
{
"id": "ocid1.eventschema.oc1.phx.ekmz1phzp4bl1k7m7tbygulbnakmjnrsi99eqjops3zvpt337pnnfmj6r79j",
"serviceName": "Database",
"displayName": "Cloud VM Cluster - Update Begin",
"eventType": "com.oraclecloud.databaseservice.updatecloudvmcluster.begin",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2019-06-27T21:16:04.000Z",
"contentType": "application/json",
"additionalDetails": [
{
"name": "id",
"type": "string"
},
{
"name": "defineTags",
"type": [
"null",
"Map<String, Map<String, Object>>"
]
},
{
"name": "freeFormTags",
"type": [
"null",
"Map<String, String>"
]
},
{
"name": "timeCreated",
"type": "string"
},
{
"name": "timeUpdated",
"type": "string"
},
{
"name": "lifecycleState",
"type": "string"
},
{
"name": "lifecycleDetails",
"type": [
"null",
"string"
]
},
{
"name": "cloudExadataInfrastructureId",
"type": "string"
},
{
"name": "cpuCoreCount",
"type": [
"null",
"Integer"
]
},
{
"name": "dataStorageSizeInGBs",
"type": [
"null",
"Integer"
]
},
{
"name": "licenseType",
"type": [
"null",
"string"
]
},
{
"name": "giVersion",
"type": [
"null",
"string"
]
},
{
"name": "dbNodeIds",
"type": [
"null",
"string"
]
},
{
"name": "timeZone",
"type": [
"null",
"string"
]
}
],
"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "b28fcda6-3d7b-4044-aa8e-7c21cde84b44",
"eventType": "com.oraclecloud.databaseservice.updatecloudvmcluster.begin",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2019-06-27T21:16:04.000Z",
"contentType": "application/json",
"data": {
"eventGroupingId": "4976b940-2c2d-4380-a669-1d70d071b187",
"eventName": "UpdateCloudVmCluster",
"compartmentName": "example_compartment",
"resourceName": "my_container_database",
"resourceId": "ocid1.cloudvmcluster.oc1.....unique_id",
"resourceVersion": null,
"additionalDetails": {
"cloudExadataInfrastructureId": "ocid1.cloudexadatainfrastructure.oc1.....unique_id",
"freeFormTags": {},
"definedTags": {},
"licenseType": "BRING_YOUR_OWN_LICENSE",
"lifecycleState": "AVAILABLE",
"giVersion": "19.0.0.0.0",
"cpuCoreCount": 16
}
}
},
"timeCreated": "2020-06-15T16:31:31.979Z"
}
This is a reference event for Cloud VM Cluster - Update End:
{
"id": "ocid1.eventschema.oc1.phx.svwkildsx63clp1q6phba7d6lns1rl92yc3uyc2ea5utjprqcwuhbgvht4we",
"serviceName": "Database",
"displayName": "Cloud VM Cluster - Update End",
"eventType": "com.oraclecloud.databaseservice.updatecloudvmcluster.end",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2019-06-27T21:16:04.000Z",
"contentType": "application/json",
"additionalDetails": [
{
"name": "id",
"type": "string"
},
{
"name": "defineTags",
"type": [
"null",
"Map<String, Map<String, Object>>"
]
},
{
"name": "freeFormTags",
"type": [
"null",
"Map<String, String>"
]
},
{
"name": "timeCreated",
"type": "string"
},
{
"name": "timeUpdated",
"type": "string"
},
{
"name": "lifecycleState",
"type": "string"
},
{
"name": "lifecycleDetails",
"type": [
"null",
"string"
]
},
{
"name": "cloudExadataInfrastructureId",
"type": "string"
},
{
"name": "cpuCoreCount",
"type": [
"null",
"Integer"
]
},
{
"name": "dataStorageSizeInGBs",
"type": [
"null",
"Integer"
]
},
{
"name": "licenseType",
"type": [
"null",
"string"
]
},
{
"name": "giVersion",
"type": [
"null",
"string"
]
},
{
"name": "dbNodeIds",
"type": [
"null",
"string"
]
},
{
"name": "timeZone",
"type": [
"null",
"string"
]
}
],
"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "b28fcda6-3d7b-4044-aa8e-7c21cde84b44",
"eventType": "com.oraclecloud.databaseservice.updatecloudvmcluster.end",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2019-06-27T21:16:04.000Z",
"contentType": "application/json",
"data": {
"eventGroupingId": "4976b940-2c2d-4380-a669-1d70d071b187",
"eventName": "UpdateCloudVmCluster",
"compartmentName": "example_compartment",
"resourceName": "my_container_database",
"resourceId": "ocid1.cloudvmcluster.oc1.....unique_id",
"resourceVersion": null,
"additionalDetails": {
"cloudExadataInfrastructureId": "ocid1.cloudexadatainfrastructure.oc1.....unique_id",
"freeFormTags": {},
"definedTags": {},
"licenseType": "BRING_YOUR_OWN_LICENSE",
"lifecycleState": "AVAILABLE",
"giVersion": "19.0.0.0.0",
"cpuCoreCount": 16
}
}
},
"timeCreated": "2020-06-15T16:31:31.979Z"
}
VM Node Subsetting Event Types
Review the list of event types that VM Node Subsetting emits.
Table 6-1 VM Node Subsetting Events
| Friendly Name | Event Type |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
Example 6-60 VM Node Subsetting Examples
"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.vmclusteraddvirtualmachine.begin",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2019-06-27T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"compartmentName": "example_name",
"resourceName": "my_database",
"resourceId": "Vmcluster-unique_ID",
"availabilityDomain": "all",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.id..oc1...unique_ID",
"lifecycleState": "AVAILABLE",
"timeCreated": "2019-09-03T12:00:00.000Z",
"timeUpdated": "2019-09-03T12:30:00.000Z",
"displayName": "testDisplayName",
"lifecycleDetails": "detail message",
"exadataInfrastructureId": "ExatraInfra-unique_ID",
"vmClusterNetworkId": "VmCluster-unique_ID",
"cpuCoreCount": 2,
"dataStorageSizeInTBs": 4,
"memorySizeInGBs": 30,
"dbNodeStorageSizeInGBs": 60,
"dbVersion": "19.0.0.0",
"licenseType": "BRING_YOUR_OWN_LICENSE",
"giVersion": "19.0.0.0",
"dbNodeIds": "[ocid1.dbnode.1, ocid1.dbnode.2,...]",
"dbServerIds": "[ocid1.dbserver.1, ocid1.dbserver.2,...]",
"timeZone": "US/Pacific"
}
}
}"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.vmclusteraddvirtualmachine.end",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2019-06-27T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"compartmentName": "example_name",
"resourceName": "my_database",
"resourceId": "Vmcluster-unique_ID",
"availabilityDomain": "all",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.id..oc1...unique_ID",
"lifecycleState": "AVAILABLE",
"timeCreated": "2019-09-03T12:00:00.000Z",
"timeUpdated": "2019-09-03T12:30:00.000Z",
"displayName": "testDisplayName",
"lifecycleDetails": "detail message",
"exadataInfrastructureId": "ExatraInfra-unique_ID",
"vmClusterNetworkId": "VmCluster-unique_ID",
"cpuCoreCount": 2,
"dataStorageSizeInTBs": 4,
"memorySizeInGBs": 30,
"dbNodeStorageSizeInGBs": 60,
"dbVersion": "19.0.0.0",
"licenseType": "BRING_YOUR_OWN_LICENSE",
"giVersion": "19.0.0.0",
"dbNodeIds": "[ocid1.dbnode.1, ocid1.dbnode.2,...]",
"dbServerIds": "[ocid1.dbserver.1, ocid1.dbserver.2,...]",
"timeZone": "US/Pacific"
}
}
}"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.vmclusterterminatevirtualmachine.begin",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2019-06-27T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"compartmentName": "example_name",
"resourceName": "my_database",
"resourceId": "Vmcluster-unique_ID",
"availabilityDomain": "all",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.id..oc1...unique_ID",
"lifecycleState": "AVAILABLE",
"timeCreated": "2019-09-03T12:00:00.000Z",
"timeUpdated": "2019-09-03T12:30:00.000Z",
"displayName": "testDisplayName",
"lifecycleDetails": "detail message",
"exadataInfrastructureId": "ExatraInfra-unique_ID",
"vmClusterNetworkId": "VmCluster-unique_ID",
"cpuCoreCount": 2,
"dataStorageSizeInTBs": 4,
"memorySizeInGBs": 30,
"dbNodeStorageSizeInGBs": 60,
"dbVersion": "19.0.0.0",
"licenseType": "BRING_YOUR_OWN_LICENSE",
"giVersion": "19.0.0.0",
"dbNodeIds": "[ocid1.dbnode.1, ocid1.dbnode.2,...]",
"dbServerIds": "[ocid1.dbserver.1, ocid1.dbserver.2,...]",
"timeZone": "US/Pacific"
}
}
}"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.vmclusterterminatevirtualmachine.end",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2019-06-27T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"compartmentName": "example_name",
"resourceName": "my_database",
"resourceId": "Vmcluster-unique_ID",
"availabilityDomain": "all",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.id..oc1...unique_ID",
"lifecycleState": "AVAILABLE",
"timeCreated": "2019-09-03T12:00:00.000Z",
"timeUpdated": "2019-09-03T12:30:00.000Z",
"displayName": "testDisplayName",
"lifecycleDetails": "detail message",
"exadataInfrastructureId": "ExatraInfra-unique_ID",
"vmClusterNetworkId": "VmCluster-unique_ID",
"cpuCoreCount": 2,
"dataStorageSizeInTBs": 4,
"memorySizeInGBs": 30,
"dbNodeStorageSizeInGBs": 60,
"dbVersion": "19.0.0.0",
"licenseType": "BRING_YOUR_OWN_LICENSE",
"giVersion": "19.0.0.0",
"dbNodeIds": "[ocid1.dbnode.1, ocid1.dbnode.2,...]",
"dbServerIds": "[ocid1.dbserver.1, ocid1.dbserver.2,...]",
"timeZone": "US/Pacific"
}
}
}Data Guard Event Types
Review the list of event types that Data Guard group and Data Guard Associations emit.
To receive events related to Data Guard actions on multiple standby databases, subscribe to the Data Guard group resource events. If you have not switched to the new model, you can continue to subscribe to the Data Guard Associations resource events. However, after switching to the new model, you will need to explicitly subscribe to the new Data Guard Group resource events.
Data Guard Event Types (Data Guard Group resource)
Review the list of event types that Data Guard groups emit.
| Friendly Name | Event Type |
|---|---|
| Change Protection Mode Begin |
com.oraclecloud.databaseservice.changeprotectionmode.begin
|
| Change Protection Mode End |
com.oraclecloud.databaseservice.changeprotectionmode.end
|
| Data Guard Create Standby Database - Create Begin | com.oraclecloud.databaseservice.createstandbydatabase.begin |
| Data Guard Create Standby Database - Create End | com.oraclecloud.databaseservice.createstandbydatabase.end |
| Data Guard Switchover - Begin | com.oraclecloud.databaseservice.dataguardswitchover.begin |
| Data Guard Switchover - End | com.oraclecloud.databaseservice.dataguardswitchover.end |
| Data Guard Failover - Begin | com.oraclecloud.databaseservice.dataguardfailover.begin |
| Data Guard Failover - End | com.oraclecloud.databaseservice.dataguardfailover.end |
| Data Guard Reinstate - Begin | com.oraclecloud.databaseservice.dataguardreinstate.begin |
| Data Guard Reinstate - End | com.oraclecloud.databaseservice.dataguardreinstate.end |
| Data Guard Update Config - Begin | com.oraclecloud.databaseservice.updatedataguardconfig.begin |
| Data Guard Update Config - End | com.oraclecloud.databaseservice.updatedataguardconfig.end |
Data Guard Event Types (Data Guard Associations resource)
Review the list of event types that Data Guard Associations emit.
Table 6-2 Data Guard Associations Events
| Friendly Name | Event Type |
|---|---|
| Change Protection Mode Begin | com.oraclecloud.databaseservice.changeprotectionmode.begin
|
| Change Protection Mode End | com.oraclecloud.databaseservice.changeprotectionmode.end
|
| Data Guard Association - Create Begin | com.oraclecloud.databaseservice.createdataguardassociation.begin
|
| Data Guard Association - Create End | com.oraclecloud.databaseservice.createdataguardassociation.end
|
| Data Guard Association - Failover Begin | com.oraclecloud.databaseservice.failoverdataguardassociation.begin
|
| Data Guard Association - Failover End | com.oraclecloud.databaseservice.failoverdataguardassociation.end
|
| Data Guard Association - Reinstate Begin | com.oraclecloud.databaseservice.reinstatedataguardassociation.begin
|
| Data Guard Association - Reinstate End | com.oraclecloud.databaseservice.reinstatedataguardassociation.end
|
| Data Guard Association - Switchover Begin | com.oraclecloud.databaseservice.switchoverdataguardassociation.begin
|
| Data Guard Association - Switchover End | com.oraclecloud.databaseservice.switchoverdataguardassociation.end
|
Oracle Database Home Event Types
Review the list of events emitted by Oracle Database Homes.
| Friendly Name | Event Type |
|---|---|
| DB Home - Create Begin | com.oraclecloud.databaseservice.createdbhome.begin |
| DB Home - Create End | com.oraclecloud.databaseservice.createdbhome.end |
| DB Home - Patch Begin | com.oraclecloud.databaseservice.patchdbhome.begin |
| DB Home - Patch End | com.oraclecloud.databaseservice.patchdbhome.end |
| DB Home - Terminate Begin | com.oraclecloud.databaseservice.deletedbhome.begin |
| DB Home - Terminate End | com.oraclecloud.databaseservice.deletedbhome.end |
| DB Home - Update Begin | com.oraclecloud.databaseservice.updatedbhome.begin |
| DB Home - Update End | com.oraclecloud.databaseservice.updatedbhome.end |
This is a reference event for Database Homes:
{
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.createdbhome.begin",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2019-08-29T21:16:04Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1.<unique_ID>"
},
"data": {
"compartmentId": "ocid1.compartment.oc1.<unique_ID>",
"compartmentName": "example_compartment",
"resourceName": "my_dbhome",
"resourceId": "DbHome-unique_ID",
"availabilityDomain": "all",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.id.oc1.<unique_ID>",
"lifecycleState": "PROVISIONING",
"timeCreated": "2019-08-29T12:00:00.000Z",
"timeUpdated": "2019-08-29T12:30:00.000Z",
"lifecycleDetails": "detail message",
"dbSystemId": "DbSystem-unique_ID",
"dbVersion": "19.0.0.0",
"recordVersion": 4,
"displayName": "example_display_name"
}
}
}Database Event Types
These are the event types that Oracle Databases in Exadata Cloud Service instances emit.
| Friendly Name | Event Type |
|---|---|
| Database - Automatic Backup Begin |
com.oraclecloud.databaseservice.automaticbackupdatabase.begin
|
| Database - Automatic Backup End |
com.oraclecloud.databaseservice.automaticbackupdatabase.end
|
| Database - Create Backup Begin |
com.oraclecloud.databaseservice.backupdatabase.begin
|
| Database - Create Backup End |
com.oraclecloud.databaseservice.backupdatabase.end
|
|
Database - Critical (see Database Service Event Types for more information) |
com.oraclecloud.databaseservice.database.critical
|
| Database - Information | com.oraclecloud.databaseservice.database.information |
| Database - Delete Backup Begin |
com.oraclecloud.databaseservice.deletebackup.begin
|
| Database - Delete Backup End |
com.oraclecloud.databaseservice.deletebackup.end
|
| Database - Migrate to KMS Key Begin |
com.oraclecloud.databaseservice.migratedatabasekmskey.begin
|
| Database - Migrate to KMS Key End |
com.oraclecloud.databaseservice.migratedatabasekmskey.end
|
| Database - Move Begin |
com.oraclecloud.databaseservice.movedatabase.begin
|
| Database - Move End |
com.oraclecloud.databaseservice.movedatabase.end
|
| Database - Restore Begin |
com.oraclecloud.databaseservice.restoredatabase.begin
|
| Database - Restore End |
com.oraclecloud.databaseservice.restoredatabase.end
|
| Database - Rotate KMS Key Begin |
com.oraclecloud.databaseservice.rotatedatabasekmskey.begin
|
| Database - Rotate KMS Key End |
com.oraclecloud.databaseservice.rotatedatabasekmskey.end
|
| Database - Terminate Begin |
com.oraclecloud.databaseservice.database.terminate.begin
|
| Database - Terminate End |
com.oraclecloud.databaseservice.database.terminate.end
|
| Database - Update Begin |
com.oraclecloud.databaseservice.updatedatabase.begin
|
| Database - Update End |
com.oraclecloud.databaseservice.updatedatabase.end
|
| Database - Upgrade Begin |
com.oraclecloud.databaseservice.upgradedatabase.begin
|
| Database - Upgrade End |
com.oraclecloud.databaseservice.upgradedatabase.end
|
This is a reference event for databases:
{
"eventType" : "com.oraclecloud.databaseservice.backupdatabase.begin",
udEventsVersion" : "0.1",
"eventTypeVersion" : "2.0",
"source" : "DatabaseService",
"eventTime" : "2020-01-08T17:31:43.666Z",
"contentType" : "application/json",
"data" : {
"compartmentId" : "ocid1.compartment.oc1.<unique_ID>",
"compartmentName": "example_compartment_name",
"resourceName": "my_backup",
"resourceId": "ocid1.dbbckup.oc1.<unique_ID>",
"availabilityDomain": "<availability_domain>",
"additionalDetails" : {
"timeCreated" : "2020-01-08T17:31:44Z",
"lifecycleState" : "CREATING",
"dbSystemId" : "ocid1.dbsystem.oc1.<unique_ID>",
"dbHomeId" : ocid1.dbhome.oc1.<unique_ID>",
"dbUniqueName" : DB1115_iad1dv",
"dbVersion" : "11.2.0.4.190716",
"databaseEdition" : "ENTERPRISE_EDITION_HIGH_PERFORMANCE",
"autoBackupsEnabled" : "false",
"backupType" : "FULL",
"databaseId" : "ocid1.database.oc1.<unique_ID>",
},
"definedTags" : {
"My_example_tag_name" :
{ "Example_key" : "Example_value" }
},
"eventID": "<unique_ID>",
"extensions" : {
"compartmentId": "ocid1.compartment.oc1.<unique_ID>"
}
}Pluggable Database Event Types
These are the event types that Oracle pluggable databases in Oracle Cloud Infrastructure emit.
| Friendly Name | Event Type |
|---|---|
| Pluggable Database - Create Begin |
com.oraclecloud.databaseservice.createpluggabledatabase.begin
|
| Pluggable Database - Create End |
com.oraclecloud.databaseservice.createpluggabledatabase.end
|
| Pluggable Database - Delete Begin |
com.oraclecloud.databaseservice.deletepluggabledatabase.begin
|
| Pluggable Database - Delete End |
com.oraclecloud.databaseservice.deletepluggabledatabase.end
|
| Pluggable Database - Local Clone Begin |
com.oraclecloud.databaseservice.localclonepluggabledatabase.begin
|
| Pluggable Database - Local Clone End |
com.oraclecloud.databaseservice.localclonepluggabledatabase.end
|
| Pluggable Database - Remote Clone Begin |
com.oraclecloud.databaseservice.remoteclonepluggabledatabase.begin
|
| Pluggable Database - Remote Clone End | com.oraclecloud.databaseservice.remoteclonepluggabledatabase.end |
| Start Pluggable Database - Begin |
com.oraclecloud.databaseservice.startpluggabledatabase.begin
|
| Start Pluggable Database - End |
com.oraclecloud.databaseservice.startpluggabledatabase.end
|
| Stop Pluggable Database - Begin |
com.oraclecloud.databaseservice.stoppluggabledatabase.begin
|
| Stop Pluggable Database - End |
com.oraclecloud.databaseservice.stoppluggabledatabase.end
|
| Pluggable Database - Convert to Regular Begin | com.oraclecloud.databaseservice.pluggabledatabase.converttoregular.begin |
| Pluggable Database - Convert to Regular End | com.oraclecloud.databaseservice.pluggabledatabase.converttoregular.end |
| Pluggable Database - Inplace Restore Begin | com.oraclecloud.databaseservice.pluggabledatabase.inplacerestore.begin |
| Pluggable Database - Inplace Restore End | com.oraclecloud.databaseservice.pluggabledatabase.inplacerestore.end |
| Pluggable Database - Refresh Begin | com.oraclecloud.databaseservice.pluggabledatabase.refresh.begin |
| Pluggable Database - Refresh End | com.oraclecloud.databaseservice.pluggabledatabase.refresh.end |
| Pluggable Database - Relocate Begin | com.oraclecloud.databaseservice.pluggabledatabase.relocate.begin |
| Pluggable Database - Relocate End | com.oraclecloud.databaseservice.pluggabledatabase.relocate.end |
This is a reference event for pluggable databases (PDBs):
{
"eventID": "unique_id",
"eventTime": "2021-03-23T00:49:14.123Z",
"extensions": {
"compartmentId": "ocid1.compartment.oc1.<unique_ID>"
},
"eventType": "com.oraclecloud.databaseservice.remoteclonepluggabledatabase.begin",
"eventTypeVersion": "2.0",
"cloudEventsVersion": "0.1",
"source": "databaseservice",
"contentType": "application/json",
"definedTags": {},
"data": {
"compartmentId": "ocid1.compartment.oc1.<unique_ID>",
"compartmentName": "MyCompartment",
"resourceName": "11092020_PKS_PDB1",
"resourceId": "ocid1.pluggabledatabases.oc1.phx.<unique_ID>",
"availabilityDomain": "XXIT:PHX-AD-1",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.pluggabledatabases.oc1.phx.<unique_ID>",
"timeCreated": "2021-03-13T21:15:59.000Z",
"timeUpdated": "2021-03-13T21:15:59.000Z",
"databaseId": "ocid1.database.oc1.<unique_ID>",
"lifecycleState": "AVAILABLE",
"lifecycleDetails": "Pluggable Database is available",
"displayName": "Pluggable Database - Remote Clone Begin"
}
}
}"exampleEvent": {
"eventID": "unique_id",
"eventTime": "2021-03-23T00:49:14.123Z",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_id"
},
"eventType": "com.oraclecloud.databaseservice.pluggabledatabase.converttoregular.begin",
"eventTypeVersion": "2.0",
"cloudEventsVersion": "0.1",
"source": "databaseservice",
"contentType": "application/json",
"definedTags": {},
"data": {
"compartmentId": "ocid1.compartment.oc1.......unique_id",
"compartmentName": "MyCompartment",
"resourceName": "11092020_PKS_PDB1",
"resourceId": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"availabilityDomain": "XXIT:PHX-AD-1",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"isRefreshableClone": true,
"timeCreated": "2021-03-13T21:15:59.000Z",
"timeUpdated": "2021-03-13T21:15:59.000Z",
"databaseId": "ocid1.database.oc1.....unique_id",
"lifecycleState": "UPDATING",
"displayName": "Pluggable Database - Convert to Regular Begin"
}
}
},
"activationTime": "2021-03-23T15:00:00.000Z",
"eventTypeVersion": "2.0"
}"exampleEvent": {
"eventID": "unique_id",
"eventTime": "2021-03-23T00:49:14.123Z",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_id"
},
"eventType": "com.oraclecloud.databaseservice.pluggabledatabase.converttoregular.end",
"eventTypeVersion": "2.0",
"cloudEventsVersion": "0.1",
"source": "databaseservice",
"contentType": "application/json",
"definedTags": {},
"data": {
"compartmentId": "ocid1.compartment.oc1.......unique_id",
"compartmentName": "MyCompartment",
"resourceName": "11092020_PKS_PDB1",
"resourceId": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"availabilityDomain": "XXIT:PHX-AD-1",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"isRefreshableClone": false,
"timeCreated": "2021-03-13T21:15:59.000Z",
"timeUpdated": "2021-03-13T21:15:59.000Z",
"databaseId": "ocid1.database.oc1.....unique_id",
"lifecycleState": "AVAILABLE",
"displayName": "Pluggable Database - Convert to Regular End"
}
}
},
"activationTime": "2021-03-23T15:00:00.000Z",
"eventTypeVersion": "2.0"
}"exampleEvent": {
"eventID": "unique_id",
"eventTime": "2021-03-23T00:49:14.123Z",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_id"
},
"eventType": "com.oraclecloud.databaseservice.pluggabledatabase.inplacerestore.begin",
"eventTypeVersion": "2.0",
"cloudEventsVersion": "0.1",
"source": "databaseservice",
"contentType": "application/json",
"definedTags": {},
"data": {
"compartmentId": "ocid1.compartment.oc1.......unique_id",
"compartmentName": "MyCompartment",
"resourceName": "11092020_PKS_PDB1",
"resourceId": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"availabilityDomain": "XXIT:PHX-AD-1",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"timeCreated": "2021-03-13T21:15:59.000Z",
"timeUpdated": "2021-03-13T21:15:59.000Z",
"databaseId": "ocid1.database.oc1.....unique_id",
"lifecycleState": "RESTORE_IN_PROGRESS",
"isRefreshableClone": false,
"displayName": "Pluggable Database - Inplace Restore Begin"
}
}
},
"activationTime": "2021-03-23T15:00:00.000Z",
"eventTypeVersion": "2.0"
}"exampleEvent": {
"eventID": "unique_id",
"eventTime": "2021-03-23T00:49:14.123Z",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_id"
},
"eventType": "com.oraclecloud.databaseservice.pluggabledatabase.inplacerestore.end",
"eventTypeVersion": "2.0",
"cloudEventsVersion": "0.1",
"source": "databaseservice",
"contentType": "application/json",
"definedTags": {},
"data": {
"compartmentId": "ocid1.compartment.oc1.......unique_id",
"compartmentName": "MyCompartment",
"resourceName": "11092020_PKS_PDB1",
"resourceId": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"availabilityDomain": "XXIT:PHX-AD-1",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"timeCreated": "2021-03-13T21:15:59.000Z",
"timeUpdated": "2021-03-13T21:15:59.000Z",
"databaseId": "ocid1.database.oc1.....unique_id",
"lifecycleState": "AVAILABLE",
"isRefreshableClone": false,
"lifecycleDetails": "Pluggable Database is available",
"displayName": "Pluggable Database - Inplace Restore End"
}
}
},
"activationTime": "2021-03-23T15:00:00.000Z",
"eventTypeVersion": "2.0"
}"exampleEvent": {
"eventID": "unique_id",
"eventTime": "2021-03-23T00:49:14.123Z",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_id"
},
"eventType": "com.oraclecloud.databaseservice.pluggabledatabase.refresh.begin",
"eventTypeVersion": "2.0",
"cloudEventsVersion": "0.1",
"source": "databaseservice",
"contentType": "application/json",
"definedTags": {},
"data": {
"compartmentId": "ocid1.compartment.oc1.......unique_id",
"compartmentName": "MyCompartment",
"resourceName": "11092020_PKS_PDB1",
"resourceId": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"availabilityDomain": "XXIT:PHX-AD-1",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"timeCreated": "2021-03-13T21:15:59.000Z",
"timeUpdated": "2021-03-13T21:15:59.000Z",
"isRefreshableClone": true,
"databaseId": "ocid1.database.oc1.....unique_id",
"lifecycleState": "AVAILABLE",
"lifecycleDetails": "Pluggable Database is available",
"displayName": "Pluggable Database - Refresh Begin"
}
}
},
"activationTime": "2021-03-23T15:00:00.000Z",
"eventTypeVersion": "2.0"
}"exampleEvent": {
"eventID": "unique_id",
"eventTime": "2021-03-23T00:49:14.123Z",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_id"
},
"eventType": "com.oraclecloud.databaseservice.pluggabledatabase.refresh.end",
"eventTypeVersion": "2.0",
"cloudEventsVersion": "0.1",
"source": "databaseservice",
"contentType": "application/json",
"definedTags": {},
"data": {
"compartmentId": "ocid1.compartment.oc1.......unique_id",
"compartmentName": "MyCompartment",
"resourceName": "11092020_PKS_PDB1",
"resourceId": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"availabilityDomain": "XXIT:PHX-AD-1",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"timeCreated": "2021-03-13T21:15:59.000Z",
"timeUpdated": "2021-03-13T21:15:59.000Z",
"databaseId": "ocid1.database.oc1.....unique_id",
"lifecycleState": "AVAILABLE",
"isRefreshableClone": true,
"lifecycleDetails": "Pluggable Database is available",
"displayName": "Pluggable Database - Refresh End"
}
}
},
"activationTime": "2021-03-23T15:00:00.000Z",
"eventTypeVersion": "2.0"
}"exampleEvent": {
"eventID": "unique_id",
"eventTime": "2021-03-23T00:49:14.123Z",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_id"
},
"eventType": "com.oraclecloud.databaseservice.pluggabledatabase.relocate.begin",
"eventTypeVersion": "2.0",
"cloudEventsVersion": "0.1",
"source": "databaseservice",
"contentType": "application/json",
"definedTags": {},
"data": {
"compartmentId": "ocid1.compartment.oc1.......unique_id",
"compartmentName": "MyCompartment",
"resourceName": "11092020_PKS_PDB1",
"resourceId": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"availabilityDomain": "XXIT:PHX-AD-1",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"timeCreated": "2021-03-13T21:15:59.000Z",
"timeUpdated": "2021-03-13T21:15:59.000Z",
"databaseId": "ocid1.database.oc1.....unique_id",
"lifecycleState": "AVAILABLE",
"isRefreshableClone": false,
"lifecycleDetails": "Pluggable Database is available",
"displayName": "Pluggable Database - Relocate Begin"
}
}
},
"activationTime": "2021-03-23T15:00:00.000Z",
"eventTypeVersion": "2.0"
}"exampleEvent": {
"eventID": "unique_id",
"eventTime": "2021-03-23T00:49:14.123Z",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_id"
},
"eventType": "com.oraclecloud.databaseservice.pluggabledatabase.relocate.end",
"eventTypeVersion": "2.0",
"cloudEventsVersion": "0.1",
"source": "databaseservice",
"contentType": "application/json",
"definedTags": {},
"data": {
"compartmentId": "ocid1.compartment.oc1.......unique_id",
"compartmentName": "MyCompartment",
"resourceName": "11092020_PKS_PDB1",
"resourceId": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"availabilityDomain": "XXIT:PHX-AD-1",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.pluggabledatabases.oc1.phx.unique_id",
"timeCreated": "2021-03-13T21:15:59.000Z",
"timeUpdated": "2021-03-13T21:15:59.000Z",
"databaseId": "ocid1.database.oc1.....unique_id",
"lifecycleState": "AVAILABLE",
"lifecycleDetails": "Pluggable Database is available",
"displayName": "Pluggable Database - Relocate End"
}
}
},
"activationTime": "2021-03-23T15:00:00.000Z",
"eventTypeVersion": "2.0"
}Database Service Events
The Database Service emits events, which are structured messages that indicate changes in resources.
- Overview of Database Service Events
- Receive Notifications about Database Service Events
Subscribe to the Database Service Events and get notified. - Database Service Event Types
Review the list of event types that the Database Service emits. - Temporarily Restrict Automatic Diagnostic Collections for Specific Events
Use thetfactl blackoutcommand to temporarily suppress automatic diagnostic collections. - Remediation
These topics cover some common issues you might run into and how to address them.
Overview of Database Service Events
Database Service Events feature implementation enables you to get notified about health issues with your Oracle Databases or other components on the Guest VM.
You are opting in with the understanding that the list of events can change in the future. You can opt-out of this feature at any time
Database Service Events feature implementation generates events for Guest VM operations and conditions, as well as Notifications for customers by leveraging the existing OCI Events service and Notification mechanisms in their tenancy. Customers can then create topics and subscribe to these topics through email, functions, or streams.
Events flow on Exadata Cloud Infrastructure depends on the following components: Oracle Trace File Analyzer (TFA), sysLens, and Oracle Database Cloud Service (DBCS) agent. Ensure that these components are up and running.
Manage Oracle Trace File Analyzer
- To check the run status of Oracle Trace File Analyzer, run the
tfactl statuscommand asrootor a non-root user:# tfactl status .-------------------------------------------------------------------------------------------------. | Host | Status of TFA | PID | Port | Version | Build ID | Inventory Status| +----------------+---------------+--------+------+------------+----------------------+------------+ | node1 | RUNNING | 41312 | 5000 | 22.1.0.0.0 | 22100020220310214615 | COMPLETE | | node2 | RUNNING | 272300 | 5000 | 22.1.0.0.0 | 22100020220310214615 | COMPLETE | '----------------+---------------+--------+------+------------+----------------------+------------' - To start the Oracle Trace File Analyzer daemon on the local node, run the
tfactl startcommand asroot:# tfactl start Starting TFA.. Waiting up to 100 seconds for TFA to be started.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Successfully started TFA Process.. . . . . . TFA Started and listening for commands - To stop the Oracle Trace File Analyzer daemon on the local node, run the
tfactl stopcommand asroot:# tfactl stop Stopping TFA from the Command Line Nothing to do ! Please wait while TFA stops Please wait while TFA stops TFA-00002 Oracle Trace File Analyzer (TFA) is not running TFA Stopped Successfully Successfully stopped TFA..
Manage sysLens
- If sysLens is running, then once every 15 minutes data is collected
in the local domU to discover the events to be reported. To check if sysLens is
running, run the
systemctl status syslenscommand asrootin the domU:# systemctl status syslens \u25cf syslens.service Loaded: loaded (/etc/systemd/system/syslens.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2022-03-16 18:08:59 UTC; 34s ago Main PID: 358039 (python3) Memory: 31.6M CGroup: /system.slice/syslens.service \u2514\u2500358039 /usr/bin/python3 /var/opt/oracle/syslens/bin/syslens_main.py --archive /var/opt/oracle/log/... Mar 16 18:08:59 node1 systemd[1]: Started syslens.service. Mar 16 18:09:09 node1 su[360495]: (to oracle) root on none Mar 16 18:09:09 node1 su[360539]: (to grid) root on none Mar 16 18:09:10 node1 su[360611]: (to grid) root on none Mar 16 18:09:11 node1 su[360653]: (to oracle) root on none - If the sysLens is enabled, when there is a reboot of the domU, then
sysLens starts automatically. To validate if sysLens is enabled to collect
telemetry, run the
systemctl is-enabled syslenscommand asrootin the domU:# systemctl is-enabled syslens enabled - To validate if sysLens is configured to notify events, run the
/usr/bin/syslens --config /var/opt/oracle/syslens/data/exacc.syslens.config --get-key enable_telemetrycommand asrootin the domU:# /usr/bin/syslens --config /var/opt/oracle/syslens/data/exacc.syslens.config --get-key enable_telemetry syslens Collection 2.3.3 on
Manage Database Service Agent
View the /opt/oracle/dcs/log/dcs-agent.log file to identify
issues with the agent.
- To check the status of the Database Service Agent, run the
systemctl statuscommand:# systemctl status dbcsagent.service dbcsagent.service Loaded: loaded (/usr/lib/systemd/system/dbcsagent.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2022-04-01 13:40:19 UTC; 6min ago Process: 9603 ExecStopPost=/bin/bash -c kill `ps -fu opc |grep "java.*dbcs-agent.*jar" |awk '{print $2}' ` (code=exited, status=0/SUCCESS) Main PID: 10055 (sudo) CGroup: /system.slice/dbcsagent.service β£ 10055 sudo -u opc /bin/bash -c umask 077; /bin/java -Doracle.security.jps.config=/opt/oracle/... - To start the agent if it is not running, run the
systemctl startcommand as therootuser:systemctl start dbcsagent.service
Receive Notifications about Database Service Events
Subscribe to the Database Service Events and get notified.
To receive notifications, subscribe to Database Service Events and get notified using the Oracle Notification service, see Notifications Overview. For more information about Oracle Cloud Infrastructure Events, see Overview of Events.
- Database - Critical
- DB Node - Critical
- DB Node - Error
- DB Node - Warning
- DB Node - Information
- DB System - Critical
Related Topics
Parent topic: Database Service Events
Database Service Event Types
Review the list of event types that the Database Service emits.
- Critical events are triggered due to several types of critical conditions and errors that cause disruption to the database and other critical components. For example, database hang errors, and availability errors for databases, database nodes, and database systems to let you know if a resource becomes unavailable.
- Information events are triggered when the database and other critical components work as expected. For example, a clean shutdown of CRS, CDB, client, or scan listener, or a startup of these components will create an event with the severity of INFORMATION.
- Threshold limits reduce the number of notifications customers will receive for similar incident events whilst at the same time ensuring they receive the incident events and are reminded in a timely fashion.
Table 6-3 Database Service Events
| Friendly Name | Event Name | Remediation | Event Type | Threshold |
|---|---|---|---|---|
|
Resource Utilization - Disk Usage |
This event is reported when VM guest file system free space falls
below 10% free, as determined by the operating system
df(1)
command, for the following file systems:
|
|
Critical threshold: 90% |
|
|
CRS status Up/Down |
An event of type CRITICAL is created when the Cluster Ready Service (CRS) is detected to be down. |
|
N/A |
|
|
An event of type INFORMATION is created once it is determined that the event for CRS down has cleared. |
N/A |
|
||
|
SCAN Listener Up/Down |
A DOWN event is created when a SCAN listener goes down. The event is
of type INFORMATION when a SCAN listener is shutdown due to user action, such as
with the Server Control Utility ( There are three SCAN listeners per cluster called LISTENER_SCAN[1,2,3]. |
|
N/A |
|
|
An event of type INFORMATION is created once it is determined that the event for SCAN Listener down has cleared. |
N/A |
|
||
|
Net Listener Up/Down |
A DOWN event is created when a client listener goes down. The event is
of type INFORMATION when a client listener is shutdown due to user action, such as
with the Server Control Utility ( There is one client listener per node, each called LISTENER. |
|
N/A |
|
|
An event of type INFORMATION is created once it is determined that the event for Client Listener down has cleared. |
N/A |
|
||
|
CDB Up/Down |
A DOWN event is created when a database instance goes down. The event
is of type INFORMATION when a database instance is shutdown due to user action, such
as with the SQL*Plus ( |
|
N/A |
|
|
An event of type INFORMATION is created once it is determined that the event for the CDB down has cleared. |
N/A |
|
||
| CRS Eviction | AVAILABILITY.DB_GUEST.CRS_INSTANCE.EVICTION An
event of type CRITICAL is created when the Cluster Ready Service (CRS) evicts a node
from the cluster. The CRS alert.log is parsed for the CRS-1632 error indicating that a
node is being removed from the cluster.
|
AVAILABILITY.DB_GUEST.CRS_INSTANCE.EVICTION |
An event of type CRITICAL is created when the Cluster Ready Service (CRS) evicts a node from the cluster. The CRS alert.log is parsed for the CRS-1632 error indicating that a node is being removed from the cluster. |
N/A |
|
Critical DB Errors |
Database corruption has been detected on your primary or standby database. The database alert.log is parsed for any specific errors that are indicative of physical block corruptions, logical block corruptions, or logical block corruptions caused by lost writes. |
|
N/A |
|
|
Other DB Errors |
An event of type CRITICAL is created if a CDB is either unable to archive the active online redo log or unable to archive the active online redo log fast enough to the log archive destinations. |
|
N/A |
|
|
An event of type CRITICAL is created when a process/session hang is detected in the CDB. |
||||
|
Backup Failures |
An event of type CRITICAL is created if there is a CDB backup with a
FAILED status reported in the |
|
N/A |
|
|
Disk Group Usage |
An event of type CRITICAL is created when an ASM disk group reaches space usage of 90% or higher. An event of type INFORMATION is created when the ASM disk group space usage drops below 90%. |
|
Critical threshold: 90% | |
|
Memory Usage |
An event of type CRITICAL is created when the amount of memory in the VM configured for HugePages is 90% or more of the total VM memory. |
|
90% |
|
|
sshd Configuration |
An event of type CRITICAL is created if unexpected values are set in the
|
|
N/A |
|
|
Disk Issues |
A Write-then-Read operation with a dummy file has failed for a file
system, typically indicating the operating system had detected an I/O error or
inconsistency (i.e. corruption) with the file system and changed the file system
mount mode from read-write to read-only. The following file systems are tested:
|
|
N/A |
|
|
Oracle EXAchk Reported Issues |
Oracle EXAchk is Exadata database platform's holistic health check that includes software, infrastructure and database configuration checks. CRITICAL check alerts should be addressed in 24 hours to maintain the maximum stability and availability of your system. This database service event alerts every 24 hours whenever there are any CRITICAL checks that are flagged in the most recent Oracle EXAchk report. The event will point to the latest Oracle EXAchk zip report. |
HEALTH.DB_CLUSTER.EXACHK.CRITICAL_ALERT |
|
N/A |
Example 6-61 Database Service DB Node Critical Events Examples
{
"eventType" : "com.oraclecloud.databaseservice.dbnode.critical",
"cloudEventsVersion" : "0.1",
"eventTypeVersion" : "2.0",
"source" : "SYSLENS/host_Name/DomU",
"eventTime" : "2022-03-04T18:19:42Z",
"contentType" : "application/json",
"data" : {
"compartmentId" : "compartment_ID",
"compartmentName" : "compartment_Name",
"resourceName" : "resource_Name",
"resourceId" : "resource_ID",
"additionalDetails" : {
"serviceType" : "EXACS",
"hostName" : "host_Name",
"description" : "The '/' filesystem is over 90% used.",
"eventName" : "HEALTH.DB_GUEST.FILESYSTEM.FREE_SPACE",
"status" : "online"
}
},
"eventID" : "a9752630-9be7-11ec-a203-00163eb980bb",
"extensions" : {
"compartmentId" : "compartment_ID"
}
}Parent topic: Database Service Events
Temporarily Restrict Automatic Diagnostic Collections for Specific Events
Use the tfactl blackout command to temporarily suppress
automatic diagnostic collections.
If you set blackout for a target, then Oracle Trace File Analyzer stops automatic diagnostic collections if it finds events in the alert logs for that target while scanning. By default, blackout will be in effect for 24 hours.
You can also restrict automatic diagnostic collection at a granular level, for example, only for ORA-00600 or even only ORA-00600 with specific arguments.
Syntax
tfactl blackout add|remove|print
-targettype host|crs|asm|asmdg|database|dbbackup|db_dataguard|db_tablespace|pdb_tablespace|pdb|listener|service|os
-target all|name
[-container name]
[-pdb pdb_name]
-event all|"event_str1,event_str2"|availability
[-timeout nm|nh|nd|none]
[-c|-local|-nodes "node1,node2"]
[-reason "reason for blackout"]
[-docollection]Parameters
Table 6-4 tfactl blackout Command Parameters
| Parameter | Description |
|---|---|
|
|
Adds, removes, or prints blackout conditions. |
|
Target type:
|
Limits blackout only to the specified target type.
|
|
|
Specify the target for blackout. You can specify a comma-delimited list of targets. By default, the target is set to |
|
|
Specify the database container
name ( |
|
|
Specify the PDB where the blackout
will take effect (for
|
|
|
Limits blackout only to the availability events, or event strings, which should not trigger auto collections, or be marked as blacked out in telemetry JSON.
string: Blackout for incidents where any part of the line contains the strings specified. Specify a comma-delimited list of strings. |
|
|
Specify the duration for blackout in number of hours or days before timing out. By default, the timeout is set to 24 hours (24h). |
|
|
Specify if blackout should be set to cluster-wide or local. By default, blackout is set to |
|
|
Specify a descriptive reason for the blackout. |
|
|
Use this option to do an automatic diagnostic collection even if a blackout is set for this target. |
Example 6-62 tfactl blackout
- To blackout event: ORA-00600 on target
type: database, target:
mydb
tfactl blackout add -targettype database -target mydb -event "ORA-00600" - To blackout event: ORA-04031 on target
type: database, target:
all
tfactl blackout add -targettype database -target all -event "ORA-04031" -timeout 1h - To blackout db backup events on target
type: dbbackup, target:
mydb
tfactl blackout add -targettype dbbackup -target mydb - To blackout db dataguard events on target
type: db_dataguard, target:
mydb
tfactl blackout add -targettype db_dataguard -target mydb -timeout 30m - To blackout db tablespace events on
target type: db_tablespace, target:
system, container:
mydb
tfactl blackout add -targettype db_tablespace -target system -container mydb -timeout 30m - To blackout ALL events on target
type: host, target:
all
tfactl blackout add -targettype host -event all -target all -timeout 1h -reason "Disabling all events during patching" - To print blackout
details
tfactl blackout print.-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------. | myhostname | +---------------+---------------------+-----------+------------------------------+------------------------------+--------+---------------+--------------------------------------+ | Target Type | Target | Events | Start Time | End Time | Status | Do Collection | Reason | +---------------+---------------------+-----------+------------------------------+------------------------------+--------+---------------+--------------------------------------+ | HOST | ALL | ALL | Thu Mar 24 16:48:39 UTC 2022 | Thu Mar 24 17:48:39 UTC 2022 | ACTIVE | false | Disabling all events during patching | | DATABASE | MYDB | ORA-00600 | Thu Mar 24 16:39:03 UTC 2022 | Fri Mar 25 16:39:03 UTC 2022 | ACTIVE | false | NA | | DATABASE | ALL | ORA-04031 | Thu Mar 24 16:39:54 UTC 2022 | Thu Mar 24 17:39:54 UTC 2022 | ACTIVE | false | NA | | DB_DATAGUARD | MYDB | ALL | Thu Mar 24 16:41:38 UTC 2022 | Thu Mar 24 17:11:38 UTC 2022 | ACTIVE | false | NA | | DBBACKUP | MYDB | ALL | Thu Mar 24 16:40:47 UTC 2022 | Fri Mar 25 16:40:47 UTC 2022 | ACTIVE | false | NA | | DB_TABLESPACE | SYSTEM_CDBNAME_MYDB | ALL | Thu Mar 24 16:45:56 UTC 2022 | Thu Mar 24 17:15:56 UTC 2022 | ACTIVE | false | NA | '---------------+---------------------+-----------+------------------------------+------------------------------+--------+---------------+--------------------------------------' - To remove blackout for event: ORA-00600 on
target type: database, target:
mydb
tfactl blackout remove -targettype database -event "ORA-00600" -target mydb - To remove blackout for db backup events on
target type: dbbackup, target:
mydb
tfactl blackout remove -targettype dbbackup -target mydb - To remove blackout for db tablespace events
on target type: db_tablespace, target: system,
container:
mydb
tfactl blackout remove -targettype db_tablespace -target system -container mydb - To remove blackout for host events on
target type: host, target:
all
tfactl blackout remove -targettype host -event all -target all
Parent topic: Database Service Events
Remediation
These topics cover some common issues you might run into and how to address them.
- HEALTH.DB_GUEST.FILESYSTEM.FREE_SPACE
- AVAILABILITY.DB_GUEST.CRS_INSTANCE.DOWN
- AVAILABILITY.DB_CLUSTER.SCAN_LISTENER.DOWN
- AVAILABILITY.DB_GUEST.CLIENT_LISTENER.DOWN
- AVAILABILITY.DB_GUEST.CDB_INSTANCE.DOWN
- AVAILABILITY.DB_GUEST.CRS_INSTANCE.EVICTION
- HEALTH.DB_CLUSTER.CDB.CORRUPTION
- HEALTH.DB_CLUSTER.CDB.ARCHIVER_HANG
- HEALTH.DB_CLUSTER.CDB.DATABASE_HANG
- HEALTH.DB_CLUSTER.CDB.BACKUP_FAILURE
- HEALTH.DB_CLUSTER.DISK_GROUP.FREE_SPACE
- Managing the Log and Diagnostic Files on Oracle Exadata Database Service on Dedicated Infrastructure
- CONFIGURATION.DB_GUEST.MEMORY.HUGEPAGES_TOO_LARGE
- CONFIGURATION.DB_GUEST.SSHD.INVALID
- HEALTH.DB_GUEST.FILESYSTEM.CORRUPTION
- HEALTH.DB_CLUSTER.EXACHK.CRITICAL_ALERT
Parent topic: Database Service Events
HEALTH.DB_GUEST.FILESYSTEM.FREE_SPACE
Problem Statement: One or more VM guest file systems has free space below 10% free.
Risk: Insufficient VM guest file system free space can cause disk space allocation failure, which can result in wide-ranging errors and failures in Oracle software (Database, Clusterware, Cloud, Exadata).
Action:
Oracle Cloud and Exadata utilities run automatically to purge old log files and trace files created by Oracle software to reclaim file system space.
If the automatic file system space reclamation utilities cannot sufficiently purge old files to clear this event, then perform the following actions:
- Remove unneeded files and/or directories created manually or by customer-installed
applications or utilities. Files created by customer-installed software are outside
the scope of Oracle's automatic file system space reclamation utilities. The
following operating system command, run as the
opcuser, is useful for identifying directories consuming excessive disk space:$ sudo du -hx file-system-mount-point | sort -hrOnly remove files or directories you are certain can be safely removed.
- Reclaim
/u02file system disk space by removing Database Homes that have no databases. For more information about managing Database Homes, see Manage Oracle Database Homes on Exadata Database Service on Exadata Cloud Infrastructure Instance. - Open service request to receive additional guidance about reducing file system space use.
Parent topic: Remediation
AVAILABILITY.DB_GUEST.CRS_INSTANCE.DOWN
Problem Statement: The Cluster Ready Stack is in an offline state or has failed.
Risk: If the Cluster Ready Service is offline on a node, then the node cannot provide database services for the application.
Action:
- Check if CRS was stopped by your administrator, as part of a planned maintenance
event, or a scale up or down of local storage.
- The following patching events will stop CRS:
- GRID Patching
- Exadata VM patching of Guest
- Exadata VM Patching of Host
- The following patching events will stop CRS:
- If CRS has stopped unexpectedly, then the current status can be checked by issuing
the
crsctl check crscommand.- If the node is not responding, then the VM node may be rebooting. Wait for
the node reboot to finish, CRS will normally be started through the
initprocess.
- If the node is not responding, then the VM node may be rebooting. Wait for
the node reboot to finish, CRS will normally be started through the
- If CRS is still down, then investigate the cause of the failure by referring to the
alert.logfound in/u01/app/grid/diag/crs/<node_name>/crs/trace.Review the log entries corresponding to the date/time of the down event. Act on any potential remediation.
- Restart the CRS, by issuing the
crsctl start crscommand. - A successful restart of CRS will generate the clearing event:
AVAILABILITY.DB_GUEST.CRS_INSTANCE.DOWN_CLEARED.
Parent topic: Remediation
AVAILABILITY.DB_CLUSTER.SCAN_LISTENER.DOWN
Problem Statement: A SCAN listener is down and unable to accept application connections.
Risk: If all SCAN listeners are down, then application connections to the database through the SCAN listener will fail.
Action:
Start the SCAN listener to receive the DOWN_CLEARED event.
DOWN event of type INFORMATION
- If the event was caused by an Oracle Cloud maintenance action, such as performing a Grid Infrastructure software update, then no action is required. The affected SCAN listener will automatically failover to an available instance.
- If the event was caused by user action, then start the SCAN listener at the next opportunity.
DOWN event of type CRITICAL
Check SCAN status and restart the SCAN listener.
- Login to the VM as
opcuser andsudoto thegriduser:sudo su - grid - Check the SCAN listener status on any
node:
srvctl status scan_listener - Start the SCAN
listener:
srvctl start scan_listener - Recheck the SCAN listeners status on any node:
If the
scan_listeneris still down, then investigate the cause of the scan listener failure:- Collect both the CRS and operating system logs 30 minutes prior
and 10 minutes for the <
hostName>indicated in the log. Note the time in the event payload is always provided in UTC. Fortfactlcollection, adjust the time to the timezone of the VM Cluster. As the grid user:tfactl diagcollect -crs -os -node <hostName> βfrom "<eventTime adjusted for local vm timezone> - 30 minute " -to "<eventTime adjusted for local vm timezone> + 10 minutes" - Review the SCAN listener log located under
/u01/app/grid/diag/tnslsnr/<hostName>/<listenerName>/trace
- Collect both the CRS and operating system logs 30 minutes prior
and 10 minutes for the <
Parent topic: Remediation
AVAILABILITY.DB_GUEST.CLIENT_LISTENER.DOWN
Problem Statement: A client listener is down and unable to accept application connections.
- If the node's client listener is down, then the database instances on the node cannot provide services for the application.
- If the client listener is down on all nodes, then any application that connects to any database using the SCAN or VIP will fail.
Action:
Start the client listener to receive the DOWN_CLEARED
event.
DOWN event of type INFORMATION
- If the event was caused by an Oracle Cloud maintenance action, such as performing a Grid Infrastructure software update, then no action is required. The affected client listener will automatically restart when maintenance affecting the grid instance is complete.
- If the event was caused by user action, then start the client listener at the next opportunity.
DOWN event of type CRITICAL
Check the client listener status and then restart the client listener.
- Login to the VM as
opcuser andsudoto thegriduser:[opc@vm ~] sudo su - grid - Check the client listener status on any
node:
[grid@vm ~] srvctl status listener - Start the client
listener:
[grid@vm ~] srvctl start listener - Recheck the client listener status on any node:
If the client listener is still down, then investigate the cause of the client listener failure:
- Use tfactl to collect both the CRS and operating system logs 30
minutes prior and 10 minutes for the
<
hostName> indicated in the log. Note the time in the event payload is always provided in UTC. For tfactl collection, adjust the time to the timezone of the VM Cluster.[grid@vm ~] tfactl diagcollect -crs -os -node <hostName> βfrom "<eventTime adjusted for local vm timezone> - 30 minute " -to "<eventTime adjusted for local vm timezone> + 10 minutes" - Review the listener log located under
/u01/app/grid/diag/tnslsnr/<hostName>/<listenerName>/trace
- Use tfactl to collect both the CRS and operating system logs 30
minutes prior and 10 minutes for the
<
Parent topic: Remediation
AVAILABILITY.DB_GUEST.CDB_INSTANCE.DOWN
Problem Statement: A database instance has gone down.
Risk: A database instance has gone down, which may result in reduced performance if database instances are available on other nodes in the cluster, or complete downtime if database instances on all nodes are down.
Action:
Start the database instance to receive the DOWN_CLEARED
event.
- If the event was caused by an Oracle Cloud maintenance action, such as performing a Database Home software update, then no action is required. The affected database instance will automatically restart when maintenance affecting the instance is complete.
- If the event was caused by user action, then start the affected database instance at the next opportunity.
DOWN event of type CRITICAL
- Check database status and restart the down database instance.
- Login to the VM as
oracleuser: - Set the
environment:
[oracle@vm ~] . <dbName>.env - Check the database
status:
[oracle@vm ~] srvctl status database -db <dbName> - Start the database
instance:
[oracle@vm ~] srvctl start instance -db <dbName> -instance <instanceName>
- Login to the VM as
- Investigate the cause of the database instance failure.
- Review Trace File Analyzer (TFA) events for the
database:
[oracle@vm ~] tfactl events -database <dbName> -instance <instanceName> - Review the database alert log located at
$ORACLE_BASE/diag/rdbms/<dbName>/<instanceName>/trace/alert_<instanceName>.log
- Review Trace File Analyzer (TFA) events for the
database:
Parent topic: Remediation
AVAILABILITY.DB_GUEST.CRS_INSTANCE.EVICTION
Problem Statement: The Oracle Clusterware is designed to perform a node eviction by removing one or more nodes from the cluster if some critical problem is detected. A critical problem could be a node not responding via a network heartbeat, a node not responding via a disk heartbeat, a hung or severely degraded machine, or a hung ocssd.bin process. The purpose of this node eviction is to maintain the overall health of the cluster by removing impaired members.
Risks: During the time it takes to restart the evicted node, the node cannot provide database services for the application.
Action: CRS node eviction could be caused by OCSSD (CSS daemon), CSSDAGENT, or CSSDMONITOR processes. This requires determining which process was responsible for the node eviction and reviewing the relevant log files. Common causes of OCSSD eviction are network failures/latencies, IO issues with CSS voting disks, a member kill escalation. CSSDAGENT or CSSDMONITOR evictions could be OS scheduler problem or a hung thread within CSS daemon.
Log files to review include:
- clusterware alert log
- cssdagent log
- cssdmonitor log
- ocssd log
- lastgasp log
/var/log/messages- CHM/OS Watcher data
opatch lsinventorydetail
For more information on collecting together most of the files, see Autonomous Health Framework (AHF) - Including TFA and ORAchk/EXAchk (Doc ID 2550798.1).
For more information on troubleshooting CRS node eviction, see Troubleshooting Clusterware Node Evictions (Reboots) (Doc ID 1050693.1).
HEALTH.DB_CLUSTER.CDB.CORRUPTION
Problem Statement: Corruptions can lead to application or database errors and in worse case result in significant data loss if not addressed promptly.
- In a physical block corruption, which is also called a media corruption, the database does not recognize the block at all; the checksum is invalid or the block contains all zeros. An example of a more sophisticated block corruption is when the block header and footer do not match.
- In a logical block corruption, the contents of the block are physically sound and pass the physical block checks; however, the block can be logically inconsistent. Examples of logical block corruption include incorrect block type, incorrect data or redo block sequence number, corruption of a row piece or index entry, or data dictionary corruptions.
For more information, see Physical and Logical Block Corruptions. All you wanted to know about it. (Doc ID 840978.1).
- In an intrablock corruption, the corruption occurs in the block itself and can be either a physical or a logical block corruption.
- In an interblock corruption, the corruption occurs between blocks and can only be a logical block corruption.
alert.log:
- ORA-01578
- ORA-00752
- ORA-00753
- ORA-00600 [3020]
- ORA-00600 [kdsgrp1]
- ORA-00600 [kclchkblk_3]
- ORA-00600 [13013]
- ORA-00600 [5463]
Risk: A data corruption outage occurs when a hardware, software, or network component causes corrupt data to be read or written. The service-level impact of a data corruption outage may vary, from a small portion of the application or database (down to a single database block) to a large portion of the application or database (making it essentially unusable). If remediation action is not taken promptly, then potential downtime and data loss can increase.
Action:
The current event notification currently triggers on physical block corruptions (ORA-01578), lost writes (ORA-00752, ORA-00753 and ORA-00600 with first argument 3020), and logical corruptions (typical detected from ORA-00600 with first argument of kdsgrp1, kdsgrp1, kclchkblk_3, 13013 OR 5463).
- Confirm that these corruptions were reported in the alert.log trace file. Log a Service Request (SR) with latest EXAchk report, excerpt of the alert.log and trace file containing the corruption errors, any history of recent application, database or software changes and any system, clusterware and database logs for the same time period. For all these cases, a TFA collection should be available and should be attached to the SR.
- For repair recommendations, refer to Handling Oracle Database Corruption Issues (Doc ID 1088018.1).
- Doc ID 1578.1 : OERR: ORA-1578 "ORACLE data block corrupted (file # %s, block # %s)" Primary Note
- Doc ID 472231.1 : How to identify all the Corrupted Objects in the Database reported by RMAN
- Doc ID 819533.1 : How to identify the corrupt Object reported by ORA-1578 / RMAN / DBVERIFY
- Depending on the object that has the corruption, follow the guidance in Doc ID 1088018.1. Note RMAN can be used to recover one or many data block that are physically corrupted. Also using Active Data Guard with real time apply, auto block repair of physical data corruptions would have occurred automatically.
- Follow the guidance, follow Doc ID 1088018.1.
- If you have a standby and lost write corruption on the primary or standby, refer to Resolving ORA-00752 or ORA-00600 [3020] During Standby Recovery (Doc ID 1265884.1)
- Follow the guidance, follow Doc ID 1088018.1 for specific guidance on the error that was detected.
- If you have a standby and logical corruption on the primary, refer to Resolving Logical Block Corruption Errors in a Physical Standby Database (Doc ID 2821699.1)
Related Topics
- Physical and Logical Block Corruptions. All you wanted to know about it. (Doc ID 840978.1)
- OERR: ORA-1578 "ORACLE data block corrupted (file # %s, block # %s)" Primary Note (Doc ID 1578.1)
- How to identify all the Corrupted Objects in the Database with RMAN (Doc ID 472231.1)
- How to identify the corrupt Object reported by ORA-1578 / RMAN / DBVERIFY (Doc ID 819533.1)
- Resolving ORA-00752 or ORA-600 [3020] During Standby Recovery (Doc ID 1265884.1)
- Resolving Logical Block Corruption Errors in a Physical Standby Database (Doc ID 2821699.1)
Parent topic: Remediation
HEALTH.DB_CLUSTER.CDB.ARCHIVER_HANG
Problem Statement: CDB RAC Instance may temporarily or permanently stall due to the log writer's (LGWR) inability to write the log buffers to an online redo log. This occurs because all online logs need archiving. Once the archiver (ARC) can archive at least one online redo log, LGWR will be able to resume writing the log buffers to online redo logs and the application impact will be alleviated.
Risk: If the archiver hang is temporary, then this can result in a small application brown out or stall for application processes attempting to commit their database changes. If the archiver is not unblocked, applications can experience extended delay in processing.
- See, Script To Find Redo log Switch History And Find Archivelog Size For Each instance In RAC (Doc ID 2373477.1) to determine the hourly frequency for each thread/instance.
- If any hourly bucket is greater than 12, then consider resizing the online redo logs. See item 2 below for resizing steps.
- If the database hangs are temporary, then the archiver may be unable to keep up
with the redo log generated. Check the
alert.log,$ORACLE_BASE/diag/rdbms/<dbName>/<instanceName>/trace/alert_<instanceName>.log, for "All online logs need archiving", multiple events in a short period can indicate 2 possible solutions.- If the number of redo logs groups per thread is less than 4, then consider adding additional logs groups to reach 4, see item 1 below for add redo log steps.
- The other possible solution is to resize the redo logs, see item 2 below for resizing steps.
- For Data Guard and Non Data Guard review the Configure Online Redo Logs Appropriately of section Oracle Database High Availability Overview and Best Practices for sizing guidelines.
- Add a redo log group for each thread. The additional redo log should equal the
current log size.
- Use the following
query:
select max(group#) Ending_group_number, thread#, count(*) number_of_groups_per_thread, bytes redo_size_in_bytes from v$log group by thread#,bytes - Add one new group per thread using the same size as the current redo
logs.
alter database add logfile thread <thread_number> Group <max group + 1> ('<DATA_DISKGROUP>') size <redo_size_in_bytes>
- Use the following
query:
- Resize the online redo logs by adding larger redo logs and dropping the
current smaller redo logs.
- Use the following
query:
select max(group#) Ending_group_number, thread#, count(*) number_of_groups_per_thread, bytes redo_size_in_bytes from v$log group by thread#,bytes - Add the same number of redo logs for each thread
<number_of_groups_per_thread> that currently
exist. The <new_redo_size_in_bytes> should be based
on Configure Online Redo Logs Appropriately of section Oracle
Database High Availability Overview and Best Practices.
-
alter database add logfile thread <thread_number> Group <max group + 1> ('<DATA_DISKGROUP>') size <new_redo_size_in_bytes> - The original smaller redo logs should be deleted. A
redo log can only be deleted if its status is inactive.
To determine the status of a redo logs issue:
select group#, thread#, status, bytes from v$log order by bytes, group#, thread#;To delete the original smaller redo logs:alter database drop logfile <group#>
-
- Use the following
query:
- If the database is hung, the primary log archive destination and alternate may be full. Review the HEALTH.DB_CLUSTER.DISK_GROUP.FREE_SPACE for details on freeing space in RECO and DATA disk groups.
HEALTH.DB_CLUSTER.CDB.DATABASE_HANG
Problem Statement: Hang management detected a process hang and generated a ORA-32701 error message. Additionally, this event may be raised if Diagnostic Process (DIA0) process detects a hang in a critical database process.
Risk: A hang can indicate resource, operating system, or application coding related issues.
Action:
- Review TFA events for the database for the following message patterns
corresponding to the date/time of the event: ORA-32701, "DIA0 Critical Database
Process Blocked" or "DIA0 Critical Database Process As
Root".
[oracle@vm ~] tfactl events -database <dbName> -instance <instanceName> - Review the
alert.logfile.$ORACLE_BASE/diag/rdbms/<dbName>/<instanceName>/trace/alert_<instanceName>.log - For ora-32701: An overloaded system can cause slow progress, which can be
interpreted as a hang.
The hang manager may attempt to resolve the hang by terminating the final blocker process.
- For DIA0 Critical Database Process messages: Review the related diagnostic lines indicating the process and the reason for the hang.
Parent topic: Remediation
HEALTH.DB_CLUSTER.CDB.BACKUP_FAILURE
Problem Statement: A daily incremental BACKUP of the CDB failed.
Risk: A failure of the backup can compromise the ability to use the backups for restore/recoverability of the database. Recoverability Point Object (RPO) and the Recoverability Time Object (RTO) can be impacted.
Action:
Review the RMAN logs corresponding to the date/time of the event. Note the event time stamp <eventTime> is in UTC, adjust as necessary for the VM's timezone.
- For Exadata Cloud Infrastructure Oracle
Managed Backups or User Configured Backups under
dbaascli:- RMAN output can be found at
/var/opt/oracle/log/<DB_NAME>/obkup.Daily incremental logs have the following format
obkup_yyyy-mm-dd_24hh:mm:ss.zzzzzzzzzzzz.logwithin theobkupdirectory. The logs are located on the lowest active node/instance of the database when the backup was initiated. - Review the log for any failures:
- If the failure is due to an external event outside of RMAN, for example the backup location was full or a networking issue, resolve the external issue.
-
For other RMAN script errors, collect the diagnostic logs and open a Service Request. See DBAAS Tooling: Using dbaascli to Collect Cloud Tooling Logs and Perform a Cloud Tooling Health Check.
-
If the issue is transient or is resolved, take a new incremental backup: See dbaascli database backup.
- RMAN output can be found at
- For Customer owned and managed backup taken through RMAN:
- Review the RMAN logs for the backup.
HEALTH.DB_CLUSTER.DISK_GROUP.FREE_SPACE
Problem Statement: ASM disk group space usage is at or exceeds 90%.
Risk: Insufficient ASM disk group space can cause database creation failure, tablespace and data file creation failure, automatic data file extension failure, or ASM rebalance failure.
Action:
[opc@node ~] sudo su - grid
[grid@node ~] sqlplus / as sysasm
SQL> select 'ora.'||name||'.dg', total_mb, free_mb, round ((1-(free_mb/total_mb))*100,2) pct_used from v$asm_diskgroup;
NAME TOTAL_MB FREE_MB PCT_USED
------------------------------ ---------- ---------- ----------
ora.DATAC1.dg 75497472 7408292 90.19
ora.RECOC1.dg 18874368 17720208 6.11ASM disk group capacity can be increased in the following ways:
- Scale Exadata VM Cluster storage to add more ASM disk group capacity. See Scaling an Exadata Cloud Infrastructure Instance.
- Scale Exadata Infrastructure storage to add more ASM disk group capacity. See Scaling Exadata X8M and X9M Compute and Storage.
DATA disk group space use can be reduced in the following ways:
- Drop unused data files and temp files from databases. See Dropping Data Files.
- Terminate unused databases (e.g. test databases). See Using the Console to Terminate a Database.
RECO disk group space use can be reduced in the following ways:
- Drop unnecessary Guaranteed Restore Points. See Using Normal and Guaranteed Restore Points.
- Delete archived redo logs or database backups already backed up outside the Flash Recovery Area (FRA). See Maintaining the Fast Recovery Area.
SPARSE disk group space use can be reduced in the following ways:
- Move full copy test master databases to another disk group (e.g. DATA).
- Drop unused snapshot databases or test master databases. See Managing Exadata Snapshots.
For more information about managing the log and diagnostic files, see Managing the Log and Diagnostic Files on Oracle Exadata Database Service on Dedicated Infrastructure.
Related Topics
- Scaling Exadata X8M, X9M, and X11M Compute and Storage
- Dropping Data Files
- To terminate a database
- Using Normal and Guaranteed Restore Points
- Maintaining the Fast Recovery Area
- Managing Exadata Snapshots
- Managing the Log and Diagnostic Files on Oracle Exadata Database Service on Dedicated Infrastructure
Parent topic: Remediation
Managing the Log and Diagnostic Files on Oracle Exadata Database Service on Dedicated Infrastructure
The software components in Oracle Exadata Database Service on Dedicated Infrastructure generate a variety of log and diagnostic files, and not all these files are automatically archived and purged. Thus, managing the identification and removal of these files to avoid running out of file storage space is an important administrative task.
Database deployments on ExaDB-D include
the cleandblogs script to simplify this administrative task. The script
runs daily as a cron job on each compute node to archive key files and
remove old log and diagnostic files.
The cleandblogs script operates by using the adrci
(Automatic Diagnostic Repository [ADR] Command Interpreter) tool to identify and purge
target diagnostic folders and files for each Oracle Home listed in
/etc/oratab. It also targets Oracle Net Listener logs, audit files,
and core dumps.
On ExaDB-D, the script is run separately
as the oracle user to clean log and diagnostic files that are
associated with Oracle Database, and as the grid user to clean log and
diagnostic files that are associated with Oracle Grid Infrastructure.
The cleandblogs script uses a configuration file to determine how long
to retain each type of log or diagnostic file. You can edit the file to change the
default retention periods. The file is located at
/var/opt/oracle/cleandb/cleandblogs.cfg on each compute node.
Configure an optimal retention period for each type of log or diagnostic file. An insufficient retention period will hinder root cause analysis and problem investigation.
| Parameter | Description and Default Value |
|---|---|
|
|
Alert log ( Default value: 14 |
|
|
Listener log ( Default value: 14 |
|
|
Database audit ( Default value: 1 |
|
|
Core dump/files ( Default value: 7 |
|
|
Trace file ( Default value: 7 |
|
|
Data designated in the Automatic Diagnostic Repository (ADR) as
having a long life (the Default value: 14 |
|
|
Data designated in the Automatic Diagnostic Repository (ADR) as
having a short life (the Default value: 7 |
|
|
Log file retention in days for files under
Default value: 14 |
|
|
Default value: 14 |
|
|
Temporary file retention in days for files under
Default value: 7 |
Archiving Alert Logs and Listener Logs
cleandblogs first archives
and compresses the logs, operating as follows:
- The current log file is copied to an archive file that ends with a date stamp.
- The current log file is emptied.
- The archive file is compressed using
gzip. - Any existing compressed archive files older than the retention period are deleted.
Running the cleandblogs Script Manually
The cleandblogs script automatically runs daily on each compute
node, but you can also run the script manually if the need arises.
- Connect to the compute node as the
oracleuser to clean log and diagnostic files that are associated with Oracle Database, or connect as thegriduser to clean log and diagnostic files that are associated with Oracle Grid Infrastructure.For detailed instructions, see Connecting to a Virtual Machine with SSH.
Change to the directory containing the cleandblogs script:$ cd /var/opt/oracle/cleandb - Run the
cleandblogsscript:$ ./cleandblogs.plWhen running the script manually, you can specify an alternate configuration file to use instead ofcleandblogs.cfgby using the--pfileoption:$ ./cleandblogs.pl --pfile config-file-name - Close your connection to the compute node:
$ exit
Parent topic: Remediation
CONFIGURATION.DB_GUEST.MEMORY.HUGEPAGES_TOO_LARGE
Problem Statement: Too much VM memory is allocated for HugePages use.
Risk: Excessive memory allocated to HugePages may result in poor database performance, or the system running out of memory, experiencing excessive swapping, or having crucial system services fail, causing system crash or node eviction.
Action:
- Reduce HugePages memory use. To determine the proper setting for operating system parameter vm.nr_hugepages, see My Oracle Support document 361323.1.
- Scale up VM memory. For more information about scaling VM memory, see Introduction to Scale Up or Scale Down Operations.
Related Topics
Parent topic: Remediation
CONFIGURATION.DB_GUEST.SSHD.INVALID
Problem Statement: SSHD configuration is unexpected.
| SSHD Configuration Setting | Expected Value |
|---|---|
|
|
yes |
|
|
This file must exist in |
|
|
no |
|
|
yes |
|
|
yes |
|
|
no |
|
|
no |
|
|
no |
|
|
no |
|
|
yes |
|
|
no |
|
|
yes |
|
|
no |
|
|
delayed |
|
|
100 |
|
|
Must contain one of the following:
|
|
|
sftp
|
|
|
2 |
|
|
|
Risk: SSHD configuration is unexpected which may cause Oracle Cloud automation failure or prevent customer SSH access to the VM.
Action: Change SSHD to match expected configuration.
- Verify SSHD service is
active.
$ sudo systemctl is-active sshd.service activeIf SSHD service is inactive, then start it.
$ sudo systemctl start sshd.service - Verify SSHD service is
enabled.
$ sudo /opt/oracle.cellos/host_access_control ssh-service --status [INFO] [IMG-SEC-1201] Service sshd is enabled {1}If SSHD service is disabled, then enable it.
$ sudo /opt/oracle.cellos/host_access_control ssh-service --enable - Change SSHD configuration to match the expected values according to the table shown
in the Problem Statement section above.
SSHD Configuration Setting How to Change Current setting Ciphers/opt/oracle.cellos/host_access_control sshciphers --helpMACs/opt/oracle.cellos/host_access_control ssh-macs --helpPermitRootLogin/opt/oracle.cellos/host_access_control rootssh --helpClientAliveInterval/opt/oracle.cellos/host_access_control idle-timeout --helpClientAliveCountMax/opt/oracle.cellos/host_access_control idle-timeout --helpListenAddress/opt/oracle.cellos/host_access_control ssh-listen --helpALL OTHER PARAMETERS
- Edit
/etc/ssh/sshd_config. - Restart
sshd.service.$ sudo systemctl restart sshd.service
- Edit
Parent topic: Remediation
HEALTH.DB_GUEST.FILESYSTEM.CORRUPTION
Problem Statement: A file system that is expected to be read-write can no longer be written to.
Risk: Oracle software (Linux, Database, Clusterware, Cloud, Exadata) requires write access to file systems to operate correctly.
Action:
/u01 and /u02 file systems:
- Stop running services, if any, that are using the file system, such as Oracle Clusterware, Trace File Analyzer (TFA), and Enterprise Manager (EM) agent.
- Unmount the file system.
- Run file system check and repair.
- ext4: Refer to Checking and Repairing a File System.
- xfs: Refer to Checking and Repairing an XFS File System.
- If the file system cannot be repaired then open a service request with Oracle Support for assistance.
- Mount the file system.
- Start the services.
/ (root) file system:
Open a service request with Oracle Support for assistance.
- If there is VM access, then collect full
dmesg(1)command output and provide it to Oracle Support. - Note that
/(root) file system repair is possible only with console access.
Parent topic: Remediation
HEALTH.DB_CLUSTER.EXACHK.CRITICAL_ALERT
Problem Statement: A CRITICAL Exachk check failed and should be reviewed and addressed as soon as possible.
Risk: A CRITICAL check is expected to impact a large number of customers AND should be addressed immediately (for example, within 24 hours) AND meets one or more of the following criteria:
- On-disk corruption or data loss
- Intermittent wrong results with Exadata feature usage (e.g. smart scan)
- System wide availability impact
- Severe system wide performance impact seriously affecting application service Service Level Agreements (SLAs)
- Compromised redundancy and inability to restore redundancy
- Inability to update software in a rolling manner
- Configuration error that could lead to an unexpected or unknown impact
Action:
Recommend that you bring up the EXAchk HTML report from the latest EXAchk zip file and click "view" on each CRITICAL check and follow the recommendation guidance that contains: Benefit/Impact, Risk, and Action/Repair guidance. Once the CRITICAL check is addressed, the next EXAchk run will pass that check. For more information about Oracle EXAchk, see Oracle Exadata Database Machine Exachk (Doc ID 1070954.1).
root user, you can re-run EXAchk command by
issuing:/usr/bin/exachk -profile exatier1 -noupgrade -dballIf the check results are returning false data, then log a Service Request.
If there is a CRITICAL check that needs to be temporarily excluded, then follow the "Skipping Specific Best Practice Checks in Exadata Cloud" section of Oracle Exadata Database Machine Exachk (Doc ID 1070954.1).
Related Topics
Parent topic: Remediation
Application VIP Event Types
These are the event types that Application VIPs in Oracle Cloud Infrastructure emit.
| Friendly Name | Event Type |
|---|---|
| Application Virtual IP (VIP) - Create Begin |
com.oraclecloud.databaseservice.createapplicationvip.begin
|
| Application Virtual IP (VIP) - Create End | com.oraclecloud.databaseservice.createapplicationvip.end |
| Application Virtual IP (VIP) - Delete Begin | com.oraclecloud.databaseservice.deleteapplicationvip.begin |
| Application Virtual IP (VIP) - Delete End | com.oraclecloud.databaseservice.deleteapplicationvip.end |
Application VIP Event Types Examples:
{
"id": "ocid1.eventschema.oc1.phx.5ur5er8bddumnu9r84rtt2c3282s5no31vsthibyqvvsisotnwpcsg9idv6q",
"serviceName": "Database",
"displayName": "Application Virtual IP (VIP) - Create Begin",
"eventType": "com.oraclecloud.databaseservice.createapplicationvip.begin",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2022-12-15T21:16:04.000Z",
"contentType": "application/json",
"additionalDetails": [
{
"name": "id",
"type": "string"
},
{
"name": "definedTags",
"type": [
"null",
"Map<String, Map<String, Object>>"
]
},
{
"name": "freeFormTags",
"type": [
"null",
"Map<String, String>"
]
},
{
"name": "timeCreated",
"type": "string"
},
{
"name": "timeUpdated",
"type": "string"
},
{
"name": "lifecycleState",
"type": "string"
},
{
"name": "lifecycleDetails",
"type": [
"null",
"string"
]
},
{
"name": "hostnameLabel",
"type": [
"null",
"string"
]
},
{
"name": "cloudVmClusterId",
"type": [
"null",
"string"
]
},
{
"name": "compartmentId",
"type": [
"null",
"string"
]
},
{
"name": "vcnIpId",
"type": [
"null",
"string"
]
},
{
"name": "ipAddress",
"type": [
"null",
"string"
]
},
{
"name": "subnetId",
"type": [
"null",
"string"
]
},
{
"name": "networkType",
"type": [
"null",
"string"
]
}
],
"exampleEvent": {
"eventType": "com.oraclecloud.databaseservice.createapplicationvip.begin",
"cloudEventsVersion": "0.1",
"eventTypeVersion": "2.0",
"source": "databaseservice",
"contentType": "application/json",
"eventID": "ab2ac219-b435-1045-aaf3-13cd909ec106",
"eventTime": "2022-12-16T21:16:04.000Z",
"data": {
"resourceId": "ocid1.applicationvip.oc1.....unique_id",
"resourceName": "my_application_vip",
"tagSlug": null,
"compartmentId": "ocid1.compartment.oc1.....unique_id",
"request": {
"id": "4260c9fd-d36b-4bc8-866e-c2dd53f34b2f",
"path": null,
"action": null,
"parameters": null,
"headers": null
},
"response": {
"status": null,
"responseTime": null,
"headers": null,
"payload": null,
"message": ""
},
"stateChange": {
"previous": null,
"current": {
"lifecycleState": "PROVISIONING",
"hostnameLabel": "my_application_vip",
"freeTags": {},
"definedTags": {}
}
},
"eventGroupingId": "csid74237ee84398b60cf1b834c81602/f43a881dc99542318d46fa9285bdf2c5/6AC9F7641E1A5AD5C27D1650CB17E822",
"eventName": "CreateApplicationVip",
"availabilityDomain": "",
"resourceVersion": null,
"additionalDetails": {
"id": "ocid1.applicationvip.oc1.....unique_id",
"freeformTags": {},
"definedTags": {},
"timeCreated": "2022-12-15T21:17:59.000Z",
"timeUpdated": "2022-12-15T21:18:04.389Z",
"lifecycleState": "PROVISIONING",
"lifecycleDetails": "",
"hostnameLabel": "my_application_vip",
"cloudVmClusterId": "ocid1.cloudvmcluster.oc1.....unique_id",
"compartmentId": "ocid1.compartment.oc1.....unique_id",
"vcnIpId": "ocid1.privateip.oc1.....unique_id",
"ipAddress": "10.0.0.0",
"subnetId": "ocid1.subnet.oc1.....unique_id",
"networkType": "CLIENT"
}
}
},
"timeCreated": "2022-12-15T16:31:31.979Z"
}{
"id": "ocid1.eventschema.oc1.phx.c1ok1948lwge4il6m85ta4jdlbnh1yjrjltrabujyv52calb0elp263oyqrm",
"serviceName": "Database",
"displayName": "Application Virtual IP (VIP) - Create End",
"eventType": "com.oraclecloud.databaseservice.createapplicationvip.end",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2022-12-15T21:16:04.000Z",
"contentType": "application/json",
"additionalDetails": [
{
"name": "id",
"type": "string"
},
{
"name": "definedTags",
"type": [
"null",
"Map<String, Map<String, Object>>"
]
},
{
"name": "freeFormTags",
"type": [
"null",
"Map<String, String>"
]
},
{
"name": "timeCreated",
"type": "string"
},
{
"name": "timeUpdated",
"type": "string"
},
{
"name": "lifecycleState",
"type": "string"
},
{
"name": "lifecycleDetails",
"type": [
"null",
"string"
]
},
{
"name": "hostnameLabel",
"type": [
"null",
"string"
]
},
{
"name": "cloudVmClusterId",
"type": [
"null",
"string"
]
},
{
"name": "compartmentId",
"type": [
"null",
"string"
]
},
{
"name": "vcnIpId",
"type": [
"null",
"string"
]
},
{
"name": "ipAddress",
"type": [
"null",
"string"
]
},
{
"name": "subnetId",
"type": [
"null",
"string"
]
},
{
"name": "networkType",
"type": [
"null",
"string"
]
}
],
"exampleEvent": {
"eventType": "com.oraclecloud.databaseservice.createapplicationvip.end",
"cloudEventsVersion": "0.1",
"eventTypeVersion": "2.0",
"source": "databaseservice",
"contentType": "application/json",
"eventID": "bc122d87-ac42-8731-ccd1-09ab320eef11",
"eventTime": "2022-12-16T21:16:04.000Z",
"data": {
"resourceId": "ocid1.applicationvip.oc1.....unique_id",
"resourceName": "my_application_vip",
"tagSlug": null,
"compartmentId": "ocid1.compartment.oc1.....unique_id",
"request": {
"id": "195eb9b5-b5a0-474d-a1c3-86189d8eeb2c",
"path": null,
"action": null,
"parameters": null,
"headers": null
},
"response": {
"status": null,
"responseTime": null,
"headers": null,
"payload": null,
"message": ""
},
"stateChange": {
"previous": null,
"current": {
"lifecycleState": "AVAILABLE",
"hostnameLabel": "my_application_vip",
"freeTags": {},
"definedTags": {}
}
},
"eventGroupingId": "6CEB05B6C81E4B19855AD716E90F5BC3/070ECF4976BDD89B16849A92B95564A6/1418EDD7590B8D5DDFF947FC3161F358",
"eventName": "CreateApplicationVip",
"availabilityDomain": "",
"resourceVersion": null,
"additionalDetails": {
"id": "ocid1.applicationvip.oc1.....unique_id",
"freeformTags": {},
"definedTags": {},
"timeCreated": "2022-12-15T21:17:59.000Z",
"timeUpdated": "2022-12-15T21:18:04.389Z",
"lifecycleState": "AVAILABLE",
"lifecycleDetails": "",
"hostnameLabel": "my_application_vip",
"cloudVmClusterId": "ocid1.cloudvmcluster.oc1.....unique_id",
"compartmentId": "ocid1.compartment.oc1.....unique_id",
"vcnIpId": "ocid1.privateip.oc1.....unique_id",
"ipAddress": "10.0.0.0",
"subnetId": "ocid1.subnet.oc1.....unique_id",
"networkType": "CLIENT"
}
}
},
"timeCreated": "2022-12-15T16:31:31.979Z"
}{
"id": "ocid1.eventschema.oc1.phx.m2gheil6f1nfzb9ggpkkv17wdomdks8zin9nntqlghui6bckh17yu0m5jcqt",
"serviceName": "Database",
"displayName": "Application Virtual IP (VIP) - Delete Begin",
"eventType": "com.oraclecloud.databaseservice.deleteapplicationvip.begin",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2022-12-15T21:16:04.000Z",
"contentType": "application/json",
"additionalDetails": [
{
"name": "id",
"type": "string"
},
{
"name": "definedTags",
"type": [
"null",
"Map<String, Map<String, Object>>"
]
},
{
"name": "freeFormTags",
"type": [
"null",
"Map<String, String>"
]
},
{
"name": "timeCreated",
"type": "string"
},
{
"name": "timeUpdated",
"type": "string"
},
{
"name": "lifecycleState",
"type": "string"
},
{
"name": "lifecycleDetails",
"type": [
"null",
"string"
]
},
{
"name": "hostnameLabel",
"type": [
"null",
"string"
]
},
{
"name": "cloudVmClusterId",
"type": [
"null",
"string"
]
},
{
"name": "compartmentId",
"type": [
"null",
"string"
]
},
{
"name": "vcnIpId",
"type": [
"null",
"string"
]
},
{
"name": "ipAddress",
"type": [
"null",
"string"
]
},
{
"name": "subnetId",
"type": [
"null",
"string"
]
},
{
"name": "networkType",
"type": [
"null",
"string"
]
}
],
"exampleEvent": {
"eventType": "com.oraclecloud.databaseservice.deleteapplicationvip.begin",
"cloudEventsVersion": "0.1",
"eventTypeVersion": "2.0",
"source": "databaseservice",
"contentType": "application/json",
"eventID": "e32cb1fe-123d-8341-de13-2be5f18ab31e",
"eventTime": "2022-12-16T21:16:04.000Z",
"data": {
"resourceId": "ocid1.applicationvip.oc1.....unique_id",
"resourceName": "my_application_vip",
"tagSlug": null,
"compartmentId": "ocid1.compartment.oc1.....unique_id",
"request": {
"id": "23a08e08-6b1e-40f0-a027-f2601dfd44ea",
"path": null,
"action": null,
"parameters": null,
"headers": null
},
"response": {
"status": null,
"responseTime": null,
"headers": null,
"payload": null,
"message": ""
},
"stateChange": {
"previous": null,
"current": {
"lifecycleState": "TERMINATING",
"hostnameLabel": "my_application_vip",
"freeTags": {},
"definedTags": {}
}
},
"eventGroupingId": "csidb3f42d234534bc8bc8849b892e84/fbd51970d2a2486f94671614b5ea0571/9DFE1BEB5433FF69BABCCB7E34F2EAF4",
"eventName": "DeleteApplicationVip",
"availabilityDomain": "",
"resourceVersion": null,
"additionalDetails": {
"id": "ocid1.applicationvip.oc1.....unique_id",
"freeformTags": {},
"definedTags": {},
"timeCreated": "2022-12-15T21:17:59.000Z",
"timeUpdated": "2022-12-15T21:18:04.389Z",
"lifecycleState": "TERMINATING",
"lifecycleDetails": "",
"hostnameLabel": "my_application_vip",
"cloudVmClusterId": "ocid1.cloudvmcluster.oc1.....unique_id",
"compartmentId": "ocid1.compartment.oc1.....unique_id",
"vcnIpId": "ocid1.privateip.oc1.....unique_id",
"ipAddress": "10.0.0.0",
"subnetId": "ocid1.subnet.oc1.....unique_id",
"networkType": "CLIENT"
}
}
},
"timeCreated": "2022-12-15T16:31:31.979Z"
}{
"id": "ocid1.eventschema.oc1.phx.9d1tjgkavhn0rq4qdlmofrjro9npvugu73dp07uht0igxs9732x6yar1m5l5",
"serviceName": "Database",
"displayName": "Application Virtual IP (VIP) - Delete End",
"eventType": "com.oraclecloud.databaseservice.deleteapplicationvip.end",
"source": "databaseservice",
"eventTypeVersion": "2.0",
"eventTime": "2022-12-15T21:16:04.000Z",
"contentType": "application/json",
"additionalDetails": [
{
"name": "id",
"type": "string"
},
{
"name": "definedTags",
"type": [
"null",
"Map<String, Map<String, Object>>"
]
},
{
"name": "freeFormTags",
"type": [
"null",
"Map<String, String>"
]
},
{
"name": "timeCreated",
"type": "string"
},
{
"name": "timeUpdated",
"type": "string"
},
{
"name": "lifecycleState",
"type": "string"
},
{
"name": "lifecycleDetails",
"type": [
"null",
"string"
]
},
{
"name": "hostnameLabel",
"type": [
"null",
"string"
]
},
{
"name": "cloudVmClusterId",
"type": [
"null",
"string"
]
},
{
"name": "compartmentId",
"type": [
"null",
"string"
]
},
{
"name": "vcnIpId",
"type": [
"null",
"string"
]
},
{
"name": "ipAddress",
"type": [
"null",
"string"
]
},
{
"name": "subnetId",
"type": [
"null",
"string"
]
},
{
"name": "networkType",
"type": [
"null",
"string"
]
}
],
"exampleEvent": {
"eventType": "com.oraclecloud.databaseservice.deleteapplicationvip.end",
"cloudEventsVersion": "0.1",
"eventTypeVersion": "2.0",
"source": "databaseservice",
"contentType": "application/json",
"eventID": "17619ca1-07ae-4e2d-a818-5b5f1fcd4f70",
"eventTime": "2022-12-16T21:16:04.000Z",
"data": {
"resourceId": "ocid1.applicationvip.oc1.....unique_id",
"resourceName": "my_application_vip",
"tagSlug": null,
"compartmentId": "ocid1.compartment.oc1.....unique_id",
"request": {
"id": "1b0d242b-b3cd-4d61-9779-2de23e0e6742",
"path": null,
"action": null,
"parameters": null,
"headers": null
},
"response": {
"status": null,
"responseTime": null,
"headers": null,
"payload": null,
"message": ""
},
"stateChange": {
"previous": null,
"current": {
"lifecycleState": "TERMINATED",
"hostnameLabel": "my_application_vip",
"freeTags": {},
"definedTags": {}
}
},
"eventGroupingId": "csid80b16d4d459eaaa60ad25a9829d8/b3e19f76a81549e6b7bf1d8619f7c191/C683214FCB0BF3CEC1C8B23C2FEE983E",
"eventName": "DeleteApplicationVip",
"availabilityDomain": "",
"resourceVersion": null,
"additionalDetails": {
"id": "ocid1.applicationvip.oc1.....unique_id",
"freeformTags": {},
"definedTags": {},
"timeCreated": "2022-12-15T21:17:59.000Z",
"timeUpdated": "2022-12-15T21:18:04.389Z",
"lifecycleState": "TERMINATED",
"lifecycleDetails": "",
"hostnameLabel": "my_application_vip",
"cloudVmClusterId": "ocid1.cloudvmcluster.oc1.....unique_id",
"compartmentId": "ocid1.compartment.oc1.....unique_id",
"vcnIpId": "ocid1.privateip.oc1.....unique_id",
"ipAddress": "10.0.0.0",
"subnetId": "ocid1.subnet.oc1.....unique_id",
"networkType": "CLIENT"
}
}
},
"timeCreated": "2022-12-15T16:31:31.979Z"
}Interim Software Updates Event Types
These are the event types that Interim Software Updates in Oracle Cloud Infrastructure emit.
| Friendly Name | Event Type |
|---|---|
| Oneoff Patch - Create Begin |
com.oraclecloud.databaseservice.createoneoffpatch.begin
|
| Oneoff Patch - Create End | com.oraclecloud.databaseservice.createoneoffpatch.end |
| Oneoff Patch - Delete Begin | com.oraclecloud.databaseservice.deleteoneoffpatch.begin |
| Oneoff Patch - Delete End | com.oraclecloud.databaseservice.deleteoneoffpatch.end |
| Oneoff Patch - Download Begin | com.oraclecloud.databaseservice.downloadoneoffpatch.begin |
| Oneoff Patch - Download End | com.oraclecloud.databaseservice.downloadoneoffpatch.end |
Interim Software Updates Event Types Examples:
{
"id": "ocid1.eventschema.oc1.phx.abyhqljrsllp7rfneajgq2knxbqopwux24za7qzoe3mfj2bzfxtnwqcxpbcq",
"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b59a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.createoneoffpatch.begin",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2020-06-27T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"compartmentName": "example_name",
"resourceName": "my_oneoffpatch",
"resourceId": "OneOffPatch-unique_ID",
"availabilityDomain": "all",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.id..oc1...unique_ID",
"lifecycleState": "AVAILABLE",
"timeCreated": "2020-08-26T12:00:00.000Z",
"displayName": "testDisplayName",
"databaseVersion": "19.6.0.0",
"patchSet": "test_patch_set"
}
}
},
"serviceName": "Database",
"displayName": "Oneoff Patch - Create Begin",
"eventType": "com.oraclecloud.databaseservice.createoneoffpatch.begin",
"additionalDetails": [
{ "name": "id", "type": "string" },
{ "name": "lifecycleState", "type": "string" },
{ "name": "timeCreated", "type": "string" },
{ "name": "displayName", "type": "string" },
{ "name": "dbVersion", "type": "string" },
{ "name": "patchType", "type": "string" },
{ "name": "patchShapeFamily", "type": "string" },
{ "name": "releaseUpdate", "type": "string" }
],
"timeCreated": "2020-06-26T13:31:31.979Z"
}{
"id": "ocid1.eventschema.oc1.phx.abyhqljrj4vvuph4qvj5eateeel6axblhkq3caqndgmjvwl3sldpgb255j2q",
"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b59a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.createoneoffpatch.end",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2020-06-27T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"compartmentName": "example_name",
"resourceName": "my_oneoffpatch",
"resourceId": "OneOffPatch-unique_ID",
"availabilityDomain": "all",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.id..oc1...unique_ID",
"lifecycleState": "AVAILABLE",
"timeCreated": "2020-08-26T12:00:00.000Z",
"displayName": "testDisplayName",
"databaseVersion": "19.6.0.0",
"patchSet": "test_patch_set"
}
}
},
"serviceName": "Database",
"displayName": "Oneoff Patch - Create End",
"eventType": "com.oraclecloud.databaseservice.createoneoffpatch.end",
"additionalDetails": [
{ "name": "id", "type": "string" },
{ "name": "lifecycleState", "type": "string" },
{ "name": "timeCreated", "type": "string" },
{ "name": "displayName", "type": "string" },
{ "name": "dbVersion", "type": "string" },
{ "name": "patchType", "type": "string" },
{ "name": "patchShapeFamily", "type": "string" },
{ "name": "releaseUpdate", "type": "string" }
],
"timeCreated": "2020-06-26T13:31:31.979Z"
}{
"id": "ocid1.eventschema.oc1.phx.abyhqljrdripga5rryplwmv4ws6hqzr3pjyl7wfvoaqutvg2ey2vtycn5onq",
"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b59a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.deleteoneoffpatch.begin",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2020-06-27T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"compartmentName": "example_name",
"resourceName": "my_oneoffpatch",
"resourceId": "OneOffPatch-unique_ID",
"availabilityDomain": "all",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.id..oc1...unique_ID",
"lifecycleState": "AVAILABLE",
"timeCreated": "2020-08-26T12:00:00.000Z",
"displayName": "testDisplayName",
"databaseVersion": "19.6.0.0",
"patchSet": "test_patch_set"
}
}
},
"serviceName": "Database",
"displayName": "Oneoff Patch - Delete Begin",
"eventType": "com.oraclecloud.databaseservice.deleteoneoffpatch.begin",
"additionalDetails": [
{ "name": "id", "type": "string" },
{ "name": "lifecycleState", "type": "string" },
{ "name": "timeCreated", "type": "string" },
{ "name": "displayName", "type": "string" },
{ "name": "dbVersion", "type": "string" },
{ "name": "patchType", "type": "string" },
{ "name": "patchShapeFamily", "type": "string" },
{ "name": "releaseUpdate", "type": "string" }
],
"timeCreated": "2020-06-26T13:31:31.979Z"
}{
"id": "ocid1.eventschema.oc1.phx.abyhqljrgwk2gvx5lmx6fiwotgdy32mdmrnkyzznz37dpb4mmehgzt37vl7a",
"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b59a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.deleteoneoffpatch.end",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2020-06-27T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"compartmentName": "example_name",
"resourceName": "my_oneoffpatch",
"resourceId": "OneOffPatch-unique_ID",
"availabilityDomain": "all",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.id..oc1...unique_ID",
"lifecycleState": "AVAILABLE",
"timeCreated": "2020-08-26T12:00:00.000Z",
"displayName": "testDisplayName",
"databaseVersion": "19.6.0.0",
"patchSet": "test_patch_set"
}
}
},
"serviceName": "Database",
"displayName": "Oneoff Patch - Delete End",
"eventType": "com.oraclecloud.databaseservice.deleteoneoffpatch.end",
"additionalDetails": [
{ "name": "id", "type": "string" },
{ "name": "lifecycleState", "type": "string" },
{ "name": "timeCreated", "type": "string" },
{ "name": "displayName", "type": "string" },
{ "name": "dbVersion", "type": "string" },
{ "name": "patchType", "type": "string" },
{ "name": "patchShapeFamily", "type": "string" },
{ "name": "releaseUpdate", "type": "string" }
],
"timeCreated": "2020-06-26T13:31:31.979Z"
}{
"id": "ocid1.eventschema.oc1.phx.abyhqljr3vkb7klt5hkbsnqzjaxmszsqomanlbqmr2tsrcq7xafcv2c74l2q",
"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b59a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.downloadoneoffpatch.begin",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2020-06-27T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"compartmentName": "example_name",
"resourceName": "my_oneoffpatch",
"resourceId": "OneOffPatch-unique_ID",
"availabilityDomain": "all",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.id..oc1...unique_ID",
"lifecycleState": "AVAILABLE",
"timeCreated": "2020-08-26T12:00:00.000Z",
"displayName": "testDisplayName",
"databaseVersion": "19.6.0.0",
"patchSet": "test_patch_set"
}
}
},
"serviceName": "Database",
"displayName": "Oneoff Patch - Download Begin",
"eventType": "com.oraclecloud.databaseservice.downloadoneoffpatch.begin",
"additionalDetails": [
{ "name": "id", "type": "string" },
{ "name": "lifecycleState", "type": "string" },
{ "name": "timeCreated", "type": "string" },
{ "name": "displayName", "type": "string" },
{ "name": "dbVersion", "type": "string" },
{ "name": "patchType", "type": "string" },
{ "name": "patchShapeFamily", "type": "string" },
{ "name": "releaseUpdate", "type": "string" }
],
"timeCreated": "2020-06-26T13:31:31.979Z"
}{
"id": "ocid1.eventschema.oc1.phx.abyhqljrn2lruez55ah56kqksi5qfg6m7igvven7o2qkahlk5tkwrj5ll3oa",
"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b59a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.downloadoneoffpatch.end",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2020-06-27T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"compartmentName": "example_name",
"resourceName": "my_oneoffpatch",
"resourceId": "OneOffPatch-unique_ID",
"availabilityDomain": "all",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.id..oc1...unique_ID",
"lifecycleState": "AVAILABLE",
"timeCreated": "2020-08-26T12:00:00.000Z",
"displayName": "testDisplayName",
"databaseVersion": "19.6.0.0",
"patchSet": "test_patch_set"
}
}
},
"serviceName": "Database",
"displayName": "Oneoff Patch - Download End",
"eventType": "com.oraclecloud.databaseservice.downloadoneoffpatch.end",
"additionalDetails": [
{ "name": "id", "type": "string" },
{ "name": "lifecycleState", "type": "string" },
{ "name": "timeCreated", "type": "string" },
{ "name": "displayName", "type": "string" },
{ "name": "dbVersion", "type": "string" },
{ "name": "patchType", "type": "string" },
{ "name": "patchShapeFamily", "type": "string" },
{ "name": "releaseUpdate", "type": "string" }
],
"timeCreated": "2020-06-26T13:31:31.979Z"
}Serial Console Connection Event Types
Review the list of event types that serial console connection emits.
Table 6-5 Serial Console Connection Events
| Friendly Name | Event Type |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example 6-63 Serial Console Connection Event Types Examples
"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.createdbnodeconsoleconnection.begin",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2019-08-29T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"resourceId": "ocid1.dbnodeconsoleconnection.oc1..unique_ID",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.dbnodeconsoleconnection.oc1..unique_ID",
"lifecycleState": "CREATING",
"timeCreated": "2019-08-29T12:00:00.000Z",
"timeUpdated": "2019-08-29T12:30:00.000Z",
"lifecycleDetails": "detail message",
"dbnodeId": "ocid1.dbnode.oc1..unique_ID",
"tenantId": "ocid1.tenant.oc1..unique_ID",
"compartmentId": "ocid1.compartment.oc1..unique_ID"
}
}
}"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.createdbnodeconsoleconnection.end",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2019-08-29T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"resourceId": "ocid1.dbnodeconsoleconnection.oc1..unique_ID",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.dbnodeconsoleconnection.oc1..unique_ID",
"lifecycleState": "ACTIVE",
"timeCreated": "2019-08-29T12:00:00.000Z",
"timeUpdated": "2019-08-29T12:30:00.000Z",
"lifecycleDetails": "detail message",
"dbnodeId": "ocid1.dbnode.oc1..unique_ID",
"tenantId": "ocid1.tenant.oc1..unique_ID",
"compartmentId": "ocid1.compartment.oc1..unique_ID"
}
}
}"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.deletedbnodeconsoleconnection.begin",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2019-08-29T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"resourceId": "ocid1.dbnodeconsoleconnection.oc1..unique_ID",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.dbnodeconsoleconnection.oc1..unique_ID",
"lifecycleState": "DELETING",
"timeCreated": "2019-08-29T12:00:00.000Z",
"timeUpdated": "2019-08-29T12:30:00.000Z",
"lifecycleDetails": "detail message",
"dbnodeId": "ocid1.dbnode.oc1..unique_ID",
"tenantId": "ocid1.tenant.oc1..unique_ID",
"compartmentId": "ocid1.compartment.oc1..unique_ID"
}
}
}"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.deletedbnodeconsoleconnection.end",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2019-08-29T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"resourceId": "ocid1.dbnodeconsoleconnection.oc1..unique_ID",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.dbnodeconsoleconnection.oc1..unique_ID",
"lifecycleState": "DELETED",
"timeCreated": "2019-08-29T12:00:00.000Z",
"timeUpdated": "2019-08-29T12:30:00.000Z",
"lifecycleDetails": "detail message",
"dbnodeId": "ocid1.dbnode.oc1..unique_ID",
"tenantId": "ocid1.tenant.oc1..unique_ID",
"compartmentId": "ocid1.compartment.oc1..unique_ID"
}
}
}"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.updatedbnodeconsoleconnection",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2019-08-29T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"resourceId": "ocid1.dbnodeconsoleconnection.oc1..unique_ID",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.dbnodeconsoleconnection.oc1..unique_ID",
"lifecycleState": "ACTIVE",
"timeCreated": "2019-08-29T12:00:00.000Z",
"timeUpdated": "2019-08-29T12:30:00.000Z",
"lifecycleDetails": "detail message",
"dbnodeId": "ocid1.dbnode.oc1..unique_ID",
"tenantId": "ocid1.tenant.oc1..unique_ID",
"compartmentId": "ocid1.compartment.oc1..unique_ID"
}
}
}"exampleEvent": {
"cloudEventsVersion": "0.1",
"eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57",
"eventType": "com.oraclecloud.databaseservice.updatedbnode",
"source": "databaseservice",
"eventTypeVersion": "1.0",
"eventTime": "2019-06-27T21:16:04.000Z",
"contentType": "application/json",
"extensions": {
"compartmentId": "ocid1.compartment.oc1..unique_ID"
},
"data": {
"compartmentId": "ocid1.compartment.oc1..unique_ID",
"compartmentName": "example_name",
"resourceName": "my_dbnode",
"resourceId": "DbNode-unique_ID",
"availabilityDomain": "all",
"freeFormTags": {},
"definedTags": {},
"additionalDetails": {
"id": "ocid1.id..oc1...unique_ID",
"lifecycleState": "AVAILABLE",
"timeCreated": "2019-08-26T12:00:00.000Z",
"timeUpdated": "2019-08-26T12:30:00.000Z",
"dbSystemId": "ocid1.dbsystem.oc1.phx.unique_ID",
"lifecycleDetails": "detail message",
"vmClusterId": "VmCluster-unique_ID",
"dbHostId": "dbHost-unique_ID",
"nodeNumber": 2,
"powerAction": "HardReset",
"hostName": "testHostName"
}
}
}- Viewing Audit Log Events
Oracle Cloud Infrastructure Audit service provides records of API operations performed against supported services as a list of log events.
Viewing Audit Log Events
Oracle Cloud Infrastructure Audit service provides records of API operations performed against supported services as a list of log events.
An audit event is generated when you connect to the serial console using a Secure Shell
(SSH) connection. Navigate to Audit in the Console and search for
VmConsoleConnected. When you navigate to Audit in the Console, a list of
results is generated for the current compartment. Audit logs are organized by compartment,
so if you are looking for a particular event, you must know which compartment the event
occurred in. You can filter the list in the following ways:
- Date and time
- Request Action Types (operations)
- Keywords
For more information, see Viewing Audit Log Events.
Example 6-64 Serial Console Connection Audit Event Example
{
"eventType": "VmConsoleConnected",
"cloudEventsVersion": "0.1",
"eventTypeVersion": "2.0",
"source": "VmConsoleConnectionAPI",
"eventId": "2367d627-cff8-11ed-bfd3-02001714f979",
"eventTime": "2023-03-31T19:13:37.120Z",
"contentType": "application/json",
"data": {
"eventGroupingId": "2367d62d-cff8-11ed-bfd3-02001714f979",
"eventName": "VmConsoleConnected",
"compartmentId": "ocid1.compartment.oc1..<TRUNCATED>aaaaxxxxx",
"compartmentName": "exacc-dev",
"resourceName": "",
"resourceId": "ocid1.dbnodeconsoleconnection.oc1.iad.<TRUNCATED>aaaaaaxxxxx",
"availabilityDomain": null,
"freeformTags": null,
"definedTags": null,
"identity": {
"principalName": "dsaes",
"principalId": "ocid1.user.oc1..<TRUNCATED>aaaaaaaaaxxxxxxxxxx",
"authType": "Native",
"callerName": null,
"callerId": null,
"tenantId": "ocid1.tenancy.oc1..<TRUNCATED>aaaaaaxxxxx",
"ipAddress": null,
"credentials": null,
"userAgent": null,
"consoleSessionId": null
},
"request": {
"id": "",
"path": "",
"action": "",
"parameters": null,
"headers": null
},
"response": {
"status": "",
"responseTime": "0001-01-01T00:00:00.000Z",
"headers": null,
"payload": null,
"message": ""
},
"stateChange": null,
"additionalDetails": {
"DBNodeId": "ocid1.dbnode.oc1.iad.<TRUNCATED>aaaaaxxxxxxx"
}
}
}Parent topic: Serial Console Connection Event Types