Observe Autonomous AI Database on Dedicated Exadata Infrastructure Resource Logs with OCI Logging Service

The Oracle Cloud Infrastructure Logging service is a highly scalable and fully managed single pane of glass for all the logs in your tenancy.

Oracle Autonomous AI Database on Dedicated Exadata Infrastructure is an Oracle Cloud Infrastructure service that emits service logs, and you can enable or disable capturing these logs using the OCI Logging Service.

Logging provides access to logs from Oracle Cloud Infrastructure resources. These logs include critical diagnostic information that describes how resources are performing and being accessed. Refer to the OCI Logging Service for more details.

Required Privileges to View Autonomous AI Database Resource Logs

• For an Autonomous Container Database (ACD), the user must have the AUTONOMOUS_CONTAINER_DATABASE_INSPECT privilege.

• For an Autonomous AI Database, the user must have the AUTONOMOUS_DATABASE_CONTENT_READ privilege.

• For an Autonomous VM Cluster on Oracle Public Cloud deployments, the user must have the CLOUD_AUTONOMOUS_VM_CLUSTER_INSPECT privilege.

• For an Autonomous VM Cluster on Exadata Cloud@Customer deployments, the user must have the AUTONOMOUS_VM_CLUSTER_INSPECT privilege.

List of Autonomous AI Database on Dedicated Exadata Infrastructure Logs

Log	Scope	Description
Unified audit Logs	Autonomous Container Database (ACD)	In Autonomous AI Database, unified audit records are periodically collected from the UNIFIED_AUDIT_TRAIL view at ten-minute intervals and written to an audit log file. This log file is then transmitted by the log transmitter service to an Oracle Cloud Infrastructure (OCI) Object Storage bucket. The audit logs are subsequently ingested into OCI Logging, making the audit data available for centralized monitoring, search, and analysis. Unified audit logs are JSON formatted files and can be extracted from the following path /var/opt/oracle/log/unified_audit_logs/ You can view the sample log files for Unified audit logs
Attention Logs	Autonomous Container Database (ACD)	Note: Attention Logs are available on Oracle Database version 26ai or later. The attention log is a JSON formatted file to capture critical events, making system diagnostics easier. There is a single attention log for each ACD. The attention log is extracted from the following path : $ORACLE_BASE/diag/rdbms//$ORACLE_SID/log/attention.log
Alert Logs	Autonomous Container Database (ACD)	Alert logs contain important information about error messages and exceptions that occur during database operations. There is a single alert log for each ACD. The alert log is extracted from the following path: $ORACLE_BASE/diag/rdbms//$ORACLE_SID/alert_$ORACLE_SID.log
Migration Logs	Autonomous AI Database	The migration logs are the logs for Oracle Data Pump export and import operations. The data pump export and import logs are extracted from the following path: /u02/data/dbfs/$CDB_NAME/$PDBGUID/import*.log "/u02/data/dbfs/$CDB_NAME/$PDBGUID/export*.log
ORDS Connection Logs	Autonomous VM Cluster (AVMC)	The ORDS connection log is for monitoring operations related to connecting your Autonomous AI Database to Oracle REST Data Services. The ORDS connection log is extracted from the following path: /u02/app/oracle/product/ords/log/access/
Mongo Connection	Autonomous VM Cluster (AVMC)	The Mongo connection log is for monitoring operations related to connecting to your Autonomous AI Database via Oracle Database API for MongoDB. The Mongo connection log is extracted from the following path: /u02/app/oracle/product/ords/log/mongo/
Network Logs	Autonomous VM Cluster (AVMC)	Network logs include Listener Logs and Scan Listener logs to monitor network activity. Network logs are extracted from the following paths: $ORACLE_BASE/diag/tnslsnr/$HOSTNAME/listener/trace/listener.log $ORACLE_BASE/diag/tnslsnr/$HOSTNAME/listener_scan2/trace/listener_scan2.log $ORACLE_BASE/diag/tnslsnr/$HOSTNAME/listener_scan3/trace/listener_scan3.log

Note: Attention Logs and Alert logs are collectively known as Database Logs.

You can view the sample log files for Database Logs and Migration Logs.

For more information on using Oracle Data Pump to export data from Oracle Autonomous AI Database on Dedicated Exadata Infrastructure, See Export Data Using Oracle Data Pump. For more information on the logs generated at the Autonomous Exadata VM Cluster and Exadata Infrastructure levels, See Auditing Capabilities in Autonomous AI Database.

Prerequisites to Enable OCI Logs

To enable service logs in a resource, a user must be granted manage access in the log group and access to the resource. In general, inspect access for the resource is enough, but check for specific resources. Inspect access provides permission to update the resource and permission for the log group that contains the log. In addition to the permissions to work with the log group, you must have the update permission for the resource, to add service logs to a resource. See Required IAM Policy for more details.

Enable Logging for an Autonomous AI Database Resource

You can enable logging for an AVMC, ACD, or an Autonomous AI Database. The procedure to enable logs for an ACD or Autonomous AI Database is the same as the procedure followed for any OCI resource. See Enabling Logging for a Resource for more details.

• From the Logs section in the Logging service, click Enable Service Log.

• Choose your compartment, select Autonomous AI Database Dedicated as the service, and choose the corresponding resource (the specific ACD or Autonomous AI Database).

• For ACD the Log Category must be Database Logs and for an Autonomous AI Database it must be Migration Logs.

• Provide a name for your log file.

For an AVMC resource, you can create a Connection log or a Network log, which includes Listener and Scan logs. For an ACD resource on database versions 26ai onwards, you can create a database log which consists of an Attention log and an Alert log. For an ACD resource on database versions 18c, 19c, 21c, and 23c the database log consists of only an Alert log. For an Autonomous AI Database, you can create a migration log which consists of data pump logs.

Note: Attention logs are available from database versions 26ai onwards.

Viewing Logs for an Autonomous AI Database Resource

You can search and filter the Database logs and Migration logs of your Autonomous AI Database resource from the OCI console.

• Open the navigation menu and select Observability & Management. Under Logging, select Search.

• You can use custom filters. Additionally, you can search for logs based on their type. You can also filter and limit logs based on time.

• The log data in the Explore and Visualize tabs is reloaded according to your filter settings. See Search Logs using the OCI console for more details.