Overview of RDS for Oracle engine upgrades
Before upgrading your RDS for Oracle DB instance, familiarize yourself with the following concepts.
Topics
Major and minor version upgrades
Major versions are major releases of Oracle Database that occur every 1-2 years. Examples of major releases are Oracle Database 19c and Oracle Database 21c.
Minor versions, which are also called Release Updates (RUs), are typically released by Oracle every quarter. Minor versions contain small feature enhancements and bug fixes. Examples of minor versions are 21.0.0.0.ru-2022-10.rur-2022-10.r1 and 19.0.0.0.ru-2022-10.rur-2022-10.r1. For more information, see Release notes for Amazon Relational Database Service (Amazon RDS) for Oracle.
RDS for Oracle supports the following upgrades to a DB instance.
| Upgrade type | Application compatibility | Upgrade methods | Sample upgrade path |
|---|---|---|---|
| Major version | A major version upgrade can introduce changes that aren't compatible with existing applications. | Manual only | From Oracle Database 19c to Oracle Database 21c |
| Minor version | A minor version upgrade includes only changes that are backward-compatible with existing applications. | Automatic or manual | From 21.0.0.0.ru-2022-07.rur-2022-07.r1 to 21.0.0.0.ru-2022-10.rur-2022-10.r1 |
Important
When you upgrade your DB engine, an outage occurs. The duration of the outage depends on your engine version and DB instance size.
Make sure that you thoroughly test any upgrade to verify that your applications work correctly before applying the upgrade to your production databases. For more information, see Testing an Oracle DB upgrade.
Expected support dates for RDS for Oracle major releases
RDS for Oracle major versions remain available at least until the end of support date for the corresponding Oracle Database release version. You can use the following dates to plan your testing and upgrade cycles. These dates represent the earliest date that an upgrade to a newer version might be required. If Amazon extends support for an RDS for Oracle version for longer than originally stated, we plan to update this table to reflect the later date.
| Oracle Database major release version | Expected date for upgrading to a newer version |
|---|---|
|
Oracle Database 19c |
April 30, 2024 without Extended Support or an Unlimited License Agreement April 30, 2027 with Extended Support or an Unlimited License Agreement |
|
Oracle Database 21c |
April 30, 2024 |
Before we ask you to upgrade to a newer major version, we remind you at least 12 months in advance. We detail the upgrade process, including the timing of important milestones, the impact on your DB instances, and recommended actions. You should thoroughly test your applications with new RDS for Oracle versions before you upgrade to a major version.
After this advance notification period, an automatic upgrade to the subsequent major version might be applied to any RDS for Oracle DB instance still running the older version. If so, the upgrade is started during scheduled maintenance windows.
Oracle engine version management
With DB engine version management, you control when and how the database engine is patched and upgraded. You get the flexibility to maintain compatibility with database engine patch versions. You can also test new patch versions of RDS for Oracle to ensure they work with your application before deploying them in production. In addition, you upgrade the versions on your own terms and timelines.
Note
Amazon RDS periodically aggregates official Oracle database patches using an Amazon RDS-specific DB engine version. To see a list of which Oracle patches are contained in an Amazon RDS Oracle-specific engine version, go to Amazon RDS for Oracle Release Notes.
Automatic snapshots during engine upgrades
During upgrades of an Oracle DB instance, snapshots offer protection against upgrade issues. If the backup retention period for your DB instance is greater than 0, Amazon RDS takes the following DB snapshots during the upgrade:
-
A snapshot of the DB instance before any upgrade changes have been made. If the upgrade fails, you can restore this snapshot to create a DB instance running the old version.
-
A snapshot of the DB instance after the upgrade completes.
Note
To change your backup retention period, see Modifying an Amazon RDS DB instance.
After an upgrade, you can't revert to the previous engine version. However, you can create a new Oracle DB instance by restoring the pre-upgrade snapshot.
Oracle upgrades in a Multi-AZ deployment
If your DB instance is in a Multi-AZ deployment, Amazon RDS upgrades both the primary and standby replicas. If no operating system updates are required, the primary and standby upgrades occur simultaneously. The instances are not available until the upgrade completes.
If operating system updates are required in a Multi-AZ deployment, Amazon RDS applies the updates when you request the DB upgrade. Amazon RDS performs the following steps:
-
Updates the operating system on the standby DB instance.
-
Upgrades the standby DB instance.
-
Fails over the primary instance to the standby DB instance.
-
Upgrades the operating system on the new standby DB instance, which was formerly the primary instance.
-
Upgrades the new standby DB instance.
Oracle upgrades of read replicas
The Oracle DB engine version of the source DB instance and all of its read replicas must be the same. Amazon RDS performs the upgrade in the following stages:
-
Upgrades the source DB instance. The read replicas are available during this stage.
-
Upgrades the read replicas in parallel, regardless of the replica maintenance windows. The source DB is available during this stage.
For major version upgrades of cross-Region read replicas, Amazon RDS performs additional actions:
-
Generates an option group for the target version automatically
-
Copies all options and option settings from the original option group to the new option group
-
Associates the upgraded cross-Region read replica with the new option group
Oracle upgrades of micro DB instances
We don't recommend upgrading databases running on micro DB instances. Because these instances have limited CPU, the upgrade can take hours to complete.
You can upgrade micro DB instances with small amounts of storage (10–20 GiB) by copying your data using Data Pump. Before you migrate your production DB instances, we recommend that you test by copying data using Data Pump.