We are pleased to announce the General Availability (GA) of Database Upgrade to 19c on Exadata Cloud@Customer Gen2. With this release, you have a simple way to upgrade your 11.2, 12.1, 12.2, or 18c databases to Oracle 19c using cloud automation through OCI. As Oracle Database 11.2 is nearing the end of support, this capability will enable you to easily upgrade your databases to the next long-term support release - Oracle 19c.
Key Customer Benefits
With the Database Upgrade to 19c capability, you can now
1. Upgrade existing databases to Oracle 19c by moving the database to a 19c Oracle home within the same VM Cluster
2. Plan the upgrade by running a precheck and address any compatibility issues in advance to prepare the target 19c home for an upgrade
3. Perform a rollback in case the upgrade flow encounters an issue and needs mitigation
4. Receive notifications about databases running a version nearing the end of support* through the OCI console with a recommendation to upgrade to 19c
Since Exadata Cloud@Customer service supports sharing an Oracle Database Home across databases, upgrade to a 19c database requires a target 19c Oracle Home within the same VM Cluster. You can provision the target home with the standard Oracle published 19c software image or a custom database software image built with the 19c version. Existing databases running the 11.2 or 18c versions will have a notification banner in the OCI console reminding customers of the end of support and the option to upgrade to the 19c database version.
OCI Console Experience
We will go over the following user journeys for database upgrade to 19c using the OCI console
◉ Run Precheck for Database Upgrade to 19c
◉ Upgrade Database to 19c
1. Run Precheck for Database Upgrade to 19c
From the database details page, you can initiate an upgrade to the 19c version. If your database version is older than 19c, the upgrade eligibility is part of the toot tip next to the database version and recommends an upgrade. For database versions nearing the end of support like 11.2 and 18c, an additional banner at the top of the database details page reminds you to upgrade to 19c before the support for your version runs out.
As part of the upgrade flow, you can select a target database home running 19c database version. If a database upgrade precheck was never done for this target database home, you will get a warning message to run a precheck as part of the upgrade workflow. If you have already run a precheck using this target home, the workflow will show the successful precheck timestamp as you prepare to upgrade. If your prior precheck failed, you get a warning message to address issues identified by the precheck and run precheck again before upgrading your database.
Running a successful precheck before a database upgrade to 19c is not mandatory but is highly recommended. Running a precheck does not incur any downtime and does not affect the availability of the running database workloads.
You can view the results of the precheck through the update history of your database. A successful precheck helps ensure the target home is compatible and ready for the database to upgrade and move. In case of a failure, you can take corrective action to resolve the issues found during precheck before proceeding with an upgrade.
Note: Database lifecycle management actions are briefly unavailable from the console while the precheck is running.
2. Upgrade Database to 19c
Once the precheck is successful (recommended but not required), you can upgrade the database using the selected 19c target database home. The upgrade will incur a database downtime, and you need to acknowledge this impact before proceeding with the upgrade.
All database lifecycle actions are unavailable while upgrading. The database home field shows the database moving to a different home with the target home name and version displayed in the status tooltip while the upgrade is in progress.
Note: The upgrade flow always runs an implicit precheck to ensure compatibility and sets up a guaranteed restore point before running the Oracle Database Upgrade Assistant (DBUA) to upgrade. These details are visible through the work request for the upgrade flow.
After the upgrade is complete, the database is now available to perform regular lifecycle operations. The database home and version are updated to reflect the upgrade to 19c. You will see a new timestamp for the last update performed on the database. You can view details of all the upgrade-related operations performed on this database through the update history accessible via a hyperlink next to the last updated timestamp field.
Note: In case of an upgrade failure, you can use the rollback capability to undo the upgrade, which internally uses the guaranteed restore point automatically set up by the workflow before starting the upgrade. The workflow will automatically drop the guaranteed restore point on a successful upgrade.
Considerations
◉ Database upgrade requires VM clusters to run Exadata System Software with Oracle Linux 7. Exadata Software 20.1.x.0.0 is the best upgrade target for customers who want to move to Oracle Linux 7.
◉ Database upgrade will incur downtime, and Oracle recommends planning your upgrade by taking a backup, running precheck, and addressing compatibility issues reported by the precheck to prepare the target database home for an upgrade.
◉ Upgrade to 19c is not supported for databases configured with Data Guard association for this release.
Availability
The support for database upgrade to 19c is now available on Exadata Cloud@Customer Gen2 in all OCI commercial regions.
Source: oracle.com
Posts
0 comments:
Post a Comment