Upgrading Oracle Database
Fleet Patching and Provisioning provides two options for upgrading Oracle Database. Both options are performed with a single command.
rhpctl upgrade database
command performs a traditional upgrade incurring downtime. The rhpctl zdtupgrade database
command performs an Oracle RAC or Oracle RAC One Node upgrade with minimal or no downtime.
You can use Fleet Patching and Provisioning to provision, scale, and patch Oracle Database 11g release 2 (11.2.0.4) and later releases. You can also upgrade Oracle Databases from 11g release 2 (11.2.0.4), 12c release 1 (12.1.0.2), 12c release 2 (12.2), and 18c to Oracle Database 19c. Refer to Oracle Database Upgrade Guide for information about Oracle Database direct upgrade paths.
Note:
The version of Oracle Grid Infrastructure on which the pre-upgrade database is running must be the same version or higher than the version of the database to which you are upgrading.Note:
You can delete the source working copy at any time after completing an upgrade. Once you delete the working copy, however, you cannot perform a rollback. Also, use therhpctl delete workingcopy
command (as opposed to rm
, for example) to remove the source working copy to keep the Fleet Patching and Provisioning inventory correct.
Oracle Database AutoUpgrade
The AutoUpgrade utility identifies issues before upgrades, performs pre- and post-upgrade actions, deploys upgrades, and starts the upgraded Oracle Database. AutoUpgrade is included with each release update (RU).
Oracle FPP runs the autoupgrade.jar
file that exists in
the Oracle home. However, before you create a gold image, Oracle strongly recommends
that you download the latest AutoUpgrade version. The most recent AutoUpgrade
version is always available from My Oracle Support Document 2485457.1.
Note:
A general Oracle Database upgrade requires you to run Oracle Database Upgrade Assistant (DBUA), but you can use theautoupg
option with the
rhpctl upgrade database
command to automate the upgrade.