Effective June 16, 2026, only the latest Oracle Database 19c and Oracle Database 26ai Release Updates (RUs), Grid Infrastructure (GI) RUs, and applicable Exadata guest operating system releases will be available for new provisioning and update operations performed through Oracle Cloud Infrastructure (OCI).

This change is part of Oracle’s updated release policy described in FAQ7792, FAQ: Oracle Database, Grid Infrastructure, and Exadata System Software Release Policy Update.

For Oracle E-Business (EBS) customers using Oracle Database cloud services, including Exadata Database Service and Base Database Service on OCI, this policy introduces important considerations for database patching, provisioning, upgrades, migrations, business continuity operations, and other lifecycle management activities that create a new Database Oracle Home.

What Has Changed?

Beginning June 16, 2026, OCI provisioning and update workflows only allow use of the latest available Database Software Image (Release Update).

This applies to:

  • New database deployments
  • Database update operations
  • Database lifecycle management activities that create a new Database Oracle Home
  • Provisioning workflows performed through the OCI Console or APIs

Earlier Database Software Images will no longer be available as selectable options by default.

Exadata Infrastructure Updates

For Exadata Database Service environments, provisioning and update operations must use the latest available Exadata system software release and applicable guest operating system release.

What Has Not Changed?

The policy applies only to new provisioning and update operations. Existing systems can continue to run their current release levels subject to normal Oracle support policies.

However, EBS administrators should be aware that many common lifecycle management procedures including upgrades, migrations, standby creation, and business continuity activities often create a new Database Oracle Home. As a result, these operations may be affected even when the target environment itself is not being upgraded.

Why This Matters to EBS Customers

EBS environments often have strict certification, compatibility, and operational requirements. Organizations may have automation, deployment standards, or maintenance procedures that depend on specific database release levels.

Because OCI will now default to the latest available Database Software Image, administrators should review planned lifecycle activities and ensure that provisioning workflows, scripts, and operational processes align with the new policy.

Need an Older Release?

Some customers may require an older Database Software Image because of:

  • Application certification requirements
  • Operational or change-management considerations
  • Internal testing and validation schedules

In these situations, Oracle Support can grant an exception.

Customers should submit a Service Request (SR) at least seven days before the planned provisioning or update activity to allow sufficient time for processing.

Note for Cloud Manager Users:

By default, EBS Cloud Manager provisioning and standby creation workflows will list only the latest available Database Software Image for selection.

If a customer obtains an approved exception and Oracle updates the tenancy with older Database Software Images, those images are automatically propagated to EBS Cloud Manager and become available for selection through the Cloud Manager user interface.

Recommended Actions

To prepare for this policy change, Oracle recommends that EBS customers:

  1. Plan new deployments, updates, and lifecycle management activities that require creation of a new Database Oracle Home to use the latest available Oracle Database 19c or 26ai RU or Database Software Image whenever possible.
  2. Plan Exadata environments to use the latest available Exadata guest operating system release.
  3. Review automation scripts, Terraform configurations, deployment pipelines, and operational procedures that reference older release levels.
  4. Evaluate upcoming patching, upgrade, migration, disaster recovery, and business continuity projects for potential impacts.
  5. Submit a Service Request with Oracle Support at least seven days before the planned activity if an older release is required.

For additional details and the information required when requesting an exception, refer to My Oracle Support Note FAQ7792, FAQ: Oracle Database, Grid Infrastructure, and Exadata System Software Release Policy Update.

Documentation Updates

EBS documentation covering database patching, upgrades, migrations, business continuity, and related lifecycle management procedures on OCI will be updated to reflect this policy change.

Customers should monitor the relevant EBS documentation and certification resources for the latest guidance.

References

Related Articles