Viewing the maintenance history of Autonomous Exadata Infrastructure (AEI) requires navigating the

OCI console correctly. The correct path is:

Under Solutions and Platforms then Platform Services then Autonomous Exadata (C): In the OCI

console, AEI is categorized under “Solutions and Platforms” (a section for integrated services), then

“Platform Services” (covering cloud platform offerings), and finally “Autonomous Exadata.” Here, you

select your AEI instance (e.g., by name or OCID), and the details page displays a “Maintenance

History” section listing past events (e.g., patching dates, durations, and statuses like “Completed on

2025-03-01”). For example, a quarterly RU applied on January 15 might show “Patch Applied: RU

23.1” with start/end times. This path reflects AEI’s role as a dedicated platform supporting

Autonomous Container Databases (ACDs) and Autonomous Databases (ADBs).

The incorrect options are:

Under Core Infrastructure then Compute then Autonomous Exadata (A): “Core Infrastructure” >

“Compute” is for virtual machines or bare metal hosts, not Exadata infrastructure. AEI isn’t a

compute instance; it’s a database platform.

Under Database then Autonomous Transaction Processing then Autonomous Exadata (B): “Database”

> “Autonomous Transaction Processing” focuses on ATP instances, not the underlying Exadata

infrastructure. AEI maintenance is separate from specific ADB types.

Under Core Infrastructure then Autonomous Exadata (D): “Core Infrastructure” doesn’t directly list

AEI; it’s too broad and lacks the “Platform Services” context needed for Exadata-specific

management.

This navigation ensures you access AEI-specific maintenance details efficiently.

Reference: Oracle Cloud Infrastructure Documentation - Managing Autonomous Exadata

Infrastructure