Have you ever had to adjust your database patching or provisioning plans because the required database release was not available for selection in OCI?
On October 14, 2026, Oracle announced expanded software release update selection options for Oracle Database cloud services. This change provides greater flexibility to select older releases during supported lifecycle operations, while the latest available release remains the default and recommended option.
This announcement updates Oracle's June 2026 guidance on OCI Database software image availability for EBS customers. It introduces additional options when planning database provisioning, patching, migrations, and business continuity activities.
What Has Changed?
Where release selection is supported, Oracle generally provides the following options:
Latest available release (N): The default and recommended option.
Two preceding releases (N-1 and N-2): Available through self-service acknowledgment.
Earlier releases: Require an approved Service Request (SR), subject to applicable release limits.
The updated policy covers supported lifecycle operations for the following OCI database services:
Oracle Base Database Service
Oracle Exadata Database Service on Dedicated Infrastructure
Oracle Exadata Database Service on Exascale Infrastructure
Oracle Exadata Database Service on Cloud@Customer
Why Does This Matter to EBS Customers?
EBS environments often require coordinated testing, maintenance planning, and change management before database changes can be implemented in production.
For example, your project may require additional time to complete application testing and obtain production approval. The expanded release selection options provide greater flexibility to align database provisioning and patching with project timelines, provided the required release remains available under Oracle's policy.
However, release availability does not automatically mean that the database release is certified for your EBS environment. Always verify the applicable EBS certification and procedural requirements before proceeding.
Need an Earlier Database Release?
Although Oracle has expanded the available choices, certain restrictions still apply to older releases:
Oracle Database 19c: Approved exceptions are limited to release 19.25 or later. These exceptions enable the creation of a custom database software image for provisioning or updates.
Grid Infrastructure (GI): Releases earlier than N-2 are unavailable.
Exadata System Software: Exceptions are limited to the six most recent monthly maintenance releases within the active release.
Older custom images: Their selection is subject to additional controls.
If your project requires an older database release, review the applicable restrictions and exception requirements before raising a Service Request.
Key takeaway: Oracle's expanded release selection options provide EBS customers with greater flexibility in planning database lifecycle activities. Before provisioning or patching, verify release availability, EBS certification, and the applicable Oracle requirements to ensure that your database changes align with project needs.
No comments:
Post a Comment