Upgrading Databases using AutoUpgrade

Starting with Enterprise Manger 13.5 Release Update 18 (13.5.0.18) AutoUpgrade will be the default tool used for upgrading databases using Fleet Maintenance. With AutoUpgrade, Enterprise Manager automatically upgrades Software Library subscribed single instance or RAC databases version 12.2 and above images.

Should you prefer to use the Database Upgrade Assistant (DBUA) for upgrades, you will need to set the oms property oracle.sysman.db.upgrade_using_autoupgrade_tool to false. Use the following sample code:
emctl set property -name oracle.sysman.db.upgrade_using_autoupgrade_tool -sysman_pwd <EM_SYSMAN_PASSWORD> -value false

Prerequisites for using AutoUpgrade

To use AutoUpgrade with Enterprise Manger Fleet Maintenance managed databases the following prerequisites must be met:
  • Data Collections must be added and running. For more information see: Extending Configuration Data Collections.
  • Upload the latest Autoupgrade.jar to the software library (either in the default location, or a custom location: to use during upgrades. To download the most recent version of AutoUpgrade see: My Oracle Support Document 2485457.1.
  • The Fast Recovery Area (FRA) should be set for all databases that will update automatically, AutoUpgrade will create the Guaranteed Restore Point (GRP) by default. If FRA is not setup AutoUpgrade will not proceed.

    For more information on FRA see: About the Fast Recovery Area and the Fast Recovery Area Disk Group.

  • The database must be in ARCHIVELOG mode for AutoUpgrade to be able to create the GRP by default. If the database is in NOARCHIVELOG mode a warning will be shown during the prerequisite checks. You can pass the flag isEnableArchiveLog as true to enable it as part of an upgrade deployment procedure.

    When using the Fleet Maintenance UI this flag will be always passed as true.

  • For TDE (Transparent Data Encryption) configured database, the wallet should be in AUTOLOGIN mode. If the wallet is a PASSWORD type you will see a warning during the prerequisite checks. Pass the flag isConvertToAutoLoginWallet as true to convert it to AUTOLOGIN as part of an upgrade deployment procedure.

    When using the Fleet Maintenance UI this flag will be always passed as true .

For more information on Oracle AutoUpgrade see: Using AutoUpgrade for Oracle Database Upgrades .

AutoUpgrade JAR Location

The AutoUpgrade jar will be used from the default component location in the software library, located at Fleet Maintenance, then Tools, and click on AutoUpgrade. It is recommended to always use the latest version of the autoupgrade.jar file, the file must be maintained and managed by you.

In the Fleet Maintenance UI the source of AutoUpgrade utility will always be auto populated and modifiable. You can provide a custom component location from the software library for the autoupgrade.jar with the parameter autoUpgradeToolPath.

You can run the AutoUpgrade jar from a Destination Oracle home with the parameter isAutoUpgradeToolFromOracleHome as true.

If you have not passed the jar location, and the default component location for the AutoUpgrade jar doesn't exist in the software library, then AutoUpgrade jar will be used from the destination Oracle home.

Users can pass all options supported by AutoUpgrade using the parameter autoUpgradeAdditionalOptions, for example:
autoUpgradeAdditionalOptions= {"restoration":"no","catctl_options":"-n 64"}
For a complete list of AutoUpgrade utility configuration files, parameters and options see: AutoUpgrade Utility Configuration Files Parameters and Options.