Flexible Software Release Selection for Base Database Service

Oracle applies release selection controls to Database and Grid Infrastructure release updates that you can select for lifecycle operations.

By default, lifecycle operations use or offer the latest available release update or maintenance release (N). This helps ensure that newly created or updated resources use software containing the latest applicable security fixes.

For lifecycle operations that support release selection, you can select an older release update or maintenance release within the supported self-service range after acknowledging the message displayed. The supported self-service range is generally N-1 and N-2 for Database and Grid Infrastructure release updates. Releases earlier than the applicable self-service range require approval through a Service Request.

The availability of release selection depends on the service and lifecycle operation.

Note:

Use the following guidelines to determine which Oracle Database (DB) releases you can request for. These guidelines are subject to change.

• Recommended: The latest Oracle AI Database 26ai Release Update.
• Available through self-service acknowledgment: The two previous DB Release Updates.
• Older releases: Require an SR with an approved exception. Oracle Database 19c requests are limited to release 19.27 or later. Once approved, the requested release is enabled only for creating a custom database software image, which customers must use for provisioning or updates.

How Release Selection Controls Work:

Release selection controls apply when a lifecycle operation creates a new Database Home, provisions a new DB system, or updates or upgrades Database or Grid Infrastructure software to a selected release update.

The following principle generally applies:

• N: The latest approved release update or maintenance release is available by default and is the recommended release.

• N-1 and N-2: Where supported, you can select either of the two preceding release updates or maintenance releases after reviewing and acknowledging the message displayed.

• Releases earlier than N-2: Submit a Service Request to request access to the required release update or maintenance release.

Release selection controls can apply to operations such as:

• Creating Database and Grid Infrastructure custom software images.
• Creating DB systems or Database Homes when a release update is selected.
• Creating databases when the operation creates a new Database Home.
• Updating Database Homes.
• Updating or upgrading the Grid Infrastructure of a DB system.

Operations That Use Existing Database Homes:

Lifecycle operations that use an existing Database Home aren’t subject to the new release selection restrictions.

For example, this principle applies when:

• Creating a database in an existing Database Home.
• Restoring a database to an existing Database Home.
• Creating a Data Guard standby in an existing Database Home, where applicable.
• Moving a database to an existing Database Home, subject to the requirements for the move operation.

If the selected Database Home is running a Database Release Update earlier than the latest approved Release Update, the Console displays a message indicating that an older release update is in use. You can continue the operation using the existing Database Home.

Selecting an Older Release Update or Maintenance Release:

When a lifecycle operation supports self-service selection of older releases, you can select either of the two release updates or maintenance releases preceding the latest available release.

When you select an eligible older release update or maintenance release, the Console displays a message. Review and acknowledge the message to continue.

If the required release update or maintenance release is earlier than those available for self-service selection, submit a Service Request to request access.

Acknowledgment Messages for Older Releases:

When you select an eligible older release update or maintenance release, the Console displays a message recommending the latest approved release update or maintenance release. Review and acknowledge the message to continue.

For guidance on older Database or Grid Infrastructure Release Updates, see Recommendations to Help Protect Oracle Databases from Emerging AI-enabled Security Threats.

For lifecycle operations that support self-service selection of older release updates or maintenance releases, you must acknowledge the displayed message before proceeding.

For operations that use an existing Database Home, release selection restrictions don’t apply. If the selected Database Home is running a Database Release Update earlier than the latest approved Release Update, the Console displays a message indicating that an older release update is in use. You can continue the operation using that Database Home.

Older Custom Software Images:

The release updates available for custom software image selection depend on the lifecycle operation and applicable release selection controls.

For operations where an older custom software image isn’t available for self-service selection, the image isn’t displayed as an available selection. To use an older custom software image that isn’t available, submit a Service Request.

Oracle recommends using custom software images based on the latest applicable Release Update to receive the most recent security fixes. For more information, see Recommendations to Help Protect Oracle Databases from Emerging AI-enabled Security Threats.

Existing Resources:

These release selection controls don’t automatically upgrade existing databases, Database Homes, DB systems, or other existing resources that are running older Database or Grid Infrastructure release updates.

Existing resources can continue to operate according to the applicable support and lifecycle policies. When you perform a lifecycle operation on an existing resource, the release selection controls depend on the operation. For example, an operation that creates a new Database Home is subject to the applicable release update selection rules, while an operation that uses an existing Database Home isn’t restricted based solely on the release update installed in that home.

Acknowledging Older Release Updates and Maintenance Releases in API Requests

Some lifecycle operations allow you to use older Database and Grid Infrastructure release updates instead of the latest eligible releases.

When an operation requires acknowledgment for an older release update or maintenance release, set the isOlderVersionAcknowledged property to true in the request.

Request Parameter:

Use the following request property when you select or apply an older Database or Grid Infrastructure release update:

• isOlderVersionAcknowledged

Set isOlderVersionAcknowledged to true to acknowledge the use of the older release update or maintenance release and continue with the operation.

This property applies to supported create, update, and apply operations where you can select or apply an older release update or maintenance release.

The property doesn’t apply to operations that don’t select or apply a release update or maintenance release, including:

• Retrieving resource details
• Viewing patch, update, or upgrade history
• Deleting resources
• Updating only tags
• Generating software image PAR URLs
• Changing compartments

Response Attribute:

For applicable release-list and other read operations, the response can include the following attribute:

• isOlderVersionAcknowledgmentRequired

This attribute indicates whether acknowledgment is required when you select an older release update or maintenance release.

When isOlderVersionAcknowledgmentRequired indicates that acknowledgment is required, set isOlderVersionAcknowledged to true in the corresponding create, update, or apply request to use the older release update or maintenance release.

Applicable Operations:

Acknowledgment for older release updates or maintenance releases applies to supported lifecycle operations such as:

• Creating Database or Grid Infrastructure software images
• Creating Database Homes
• Patching a Database Home or applying a custom Database software image
• Creating or updating DB Systems
• Applying Grid Infrastructure release updates to DB systems
• Performing database operations that select or move to a target release update or Database Home
• Creating a Data Guard association when the operation creates a new standby Database Home or DB System

For applicable release and update list operations, use the isOlderVersionAcknowledgmentRequired response attribute to determine whether acknowledgment is required before submitting the corresponding lifecycle request.

Using the Acknowledgment Property:

When an operation requires acknowledgment:

1. Retrieve or select the target Database or Grid Infrastructure release update, patch, or software image.
2. Check whether acknowledgment is required for the selected release update or maintenance release.
3. In the create, update, or apply request, set isOlderVersionAcknowledged to true.
4. Submit the request.

The acknowledgment applies to the target release update, maintenance release, patch, or software image selected for the lifecycle operation.