Autoupgrade – Myths and Methods

“Autoupgrade is only for large environments.” “Configuration is time-consuming and challenging.”

“It doesn’t work with non-container databases.”

Get the truth about Autoupgrade and learn why it’s the best, most reliable tool for upgrading Oracle databases! You may have heard about Autoupgrade—how it can upgrade dozens or hundreds of databases; run unattended or scheduled upgrades; identify and automatically fix problems; and automate pre- and post-upgrade steps. You may have also heard things like:

* “Autoupgrade is only for large environments and it’s too much trouble for fewer than ten databases.”

* “Configuration is time-consuming and challenging.”

* “It only supports multiple, simultaneous upgrades.”

* “Only a few, limited upgrade paths are supported.”

* “It’s hard to use and slow.”

* “It can’t migrate non-container databases and forces you to use pluggable databases.”

* “Stick with proven, mature tools like Database Upgrade Assistant!”

The truth is, Autoupgrade simplifies and streamlines the upgrade of even a single database. It’s easy to use and configure, fast and flexible. If Autoupgrade encounters a problem it can’t fix automatically, the process of identifying, fixing and resuming an upgrade is straightforward. In this session I share best practices and recommendations based on multiple real-world customer upgrades, including:

* Why Autoupgrade is the method of choice for upgrading to 12cR2, 18c, 19c and beyond

* Planning and preparing for an Autoupgrade

* Preparing a configuration for a single database in under a minute

* Autoupgrade capabilities demonstrated, from simple to complex

* Dealing with the unexpected, fixing issues, resuming jobs and recovering from a failed upgrade.