Oracle Cloud Infrastructure Documentation

Expanded Software Release Update Choices

Oracle applies release selection controls to Database and Grid Infrastructure release updates, and Exadata System Software maintenance releases 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 associated risks. The supported self-service range is generally N-1 and N-2 for Database and Grid Infrastructure release updates, and Exadata System Software maintenance releases. 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.

How Release Selection Controls Work

Release selection controls apply when a lifecycle operation creates a new software home, provisions a new resource, or updates an existing resource to a selected release update or maintenance release.

The following behavior 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 associated security risks.
  • Releases earlier than N-2: Submit a Service Request to request access to the required release update or maintenance release.

For Exadata System Software, N represents the latest approved maintenance release within the applicable major release.

Release selection controls can apply to operations such as:

  • Creating Database and Grid Infrastructure custom software images.
  • Creating Database Homes and Grid Infrastructure Homes.
  • Creating databases when the operation creates a new Database Home.
  • Patching Database Homes and Grid Infrastructure Homes.
  • Provisioning VM clusters where Exadata System Software maintenance release or Grid Infrastructure release update selection is supported.
  • Updating or upgrading Guest VM OS/Exadata System Software.

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 behavior 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 about the risks associated with using the older release update. 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 information about the associated security risks. Review the information and acknowledge the risks 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.

Risk Messages for Older Releases

When you select an eligible older release update or maintenance release, the Console displays a message about the associated security risks and recommends using the latest approved release update or maintenance release.

The message and referenced My Oracle Support note depend on the software being selected:

For lifecycle operations that support self-service selection of older release updates or maintenance releases, you must acknowledge the associated risks before you can proceed.

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 risk information, but 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, Grid Infrastructure Homes, VM clusters, or other existing resources that are running older Database or Grid Infrastructure release updates, or Exadata System Software maintenance releases.

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.

Parent topic: How-to Guides

Acknowledging Older Release Updates and Maintenance Releases in API Requests

Some lifecycle operations allow you to use older Database and Grid Infrastructure release updates, and Exadata System Software maintenance releases 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, or Exadata System Software maintenance release:

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 when a release update is selected
  • Creating VM Clusters
  • Applying Grid Infrastructure release updates or Exadata System Software maintenance releases to VM Clusters
  • 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
  • Creating Grid Infrastructure Homes

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, Exadata System Software maintenance release, 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.