3 Using AutoUpgrade for Oracle Database Upgrades

Learn how to use AutoUpgrade to simplify your upgrade tasks.

• About Oracle Database AutoUpgrade
  The AutoUpgrade utility is designed to automate the upgrade process, both before starting upgrades, during upgrade deployments, and during postupgrade checks and configuration migration
• Examples of How to Use AutoUpgrade
  To guide your upgrade, use the AutoUpgrade workflow example that matches your upgrade use case.
• AutoUpgrade Messages and Process Description Terms
  To understand how your upgrade checks and operations are proceeding, learn about the AutoUpgrade utility messages that are generated as the utility runs.
• About AutoUpgrade Processing Modes
  The four AutoUpgrade processing modes (Analyze, Fixup, Deploy, and Upgrade) characterize the actions that AutoUpgrade performs as it runs.
• Understanding AutoUpgrade Workflows and Stages
  The AutoUpgrade workflow automates each step of a typical upgrade process. The stages that run depend on the processing mode that you select.
• Understanding Non-CDB to PDB Upgrades with AutoUpgrade
  You can upgrade and convert a non-CDB to a PDB in a new CDB in a single operation, or upgrade and then convert a Non-CDB database to a PDB in a pre-existing CDB.
• Understanding Unplug-Plug Upgrades with AutoUpgrade
  AutoUpgrade can perform an unplug of a pluggable database (PDB) from an earlier release source container database (CDB), plug it into a later release target CDB, and then complete all the steps required to upgrade the PDB to the target CDB release.
• AutoUpgrade Command-Line Parameters and Options
  Review the AutoUpgrade parameters and select the parameters and options for your Oracle Database upgrade use case.
• Understanding AutoUpgrade Utility Configuration Files Parameters and Options
  AutoUpgrade configuration files (also referred to as config files) contain all the information required to perform Oracle Database upgrades and software maintenance operations.
• Common Parameters for the AutoUpgrade Configuration File (Upgrade and Patch)
  You can use common parameters for the AutoUpgrade configuration file (config) with both upgrade and software maintenance -patch operations.
• Upgrade Parameters for the AutoUpgrade Configuration File
  The upgrade parameters for the AutoUpgrade configuration file (config) are used only with upgrade operations.
• Patch Parameters for the AutoUpgrade Configuration File
  The patch parameters for the AutoUpgrade configuration file (config) are only used with software maintenance -patch operations.
• AutoUpgrade and Oracle Database Configuration Options
  When you run AutoUpgrade, it determines the type of database (Oracle Database, Oracle Database Standalone with Oracle ASM, or Oracle RAC), and performs an upgrade for that type of database
• AutoUpgrade Patching
  AutoUpgrade has enhanced capability that enables it to automate all of the necessary steps in the database patching process, including optional downloading of patches.
• AutoUpgrade Configuration File Examples
  Use these examples to understand how you can modify your own AutoUpgrade configuration files to perform a variety of configuration actions during the upgrade.
• AutoUpgrade Internal Settings Configuration File
  Internal configuration settings control how AutoUpgrade runs.
• AutoUpgrade Log File Structure
  The AutoUpgrade utility produces a log file structure that includes job status and configuration files.
• Enabling Full Deployments for AutoUpgrade
  To enable a guaranteed restore point (GRP) so that you can flashback an upgrade, you must set up archive logging, and you should complete other tasks to enable AutoUpgrade to complete the upgrade.
• Examples of How to Use the AutoUpgrade Console
  The AutoUpgrade console provides a set of commands to monitor the progress of AutoUpgrade jobs. The console starts by default when you run the AutoUpgrade utility, and is enabled or disabled by the parameters console and noconsole.
• Known Restrictions for AutoUpgrade
  If you encounter issues with your upgrade, review the known restrictions to find solutions.
• Proper Management of AutoUpgrade Database Changes
  AutoUpgrade is a powerful utility, which requires that you use it responsibly. Review and avoid using AutoUpgrade in ways that put the database at risk.
• How to Override Default Fixups
  You can use the RUNFIX column entry to disable automated fixups, except in cases where disabling the fixup violates security or Oracle policy.
• Local Configuration File Parameter Fixups Checklist Example
  To include or exclude specific fixups for individual databases during upgrades, use the local configuration file checklist.
• AutoUpgrade and Microsoft Windows ACLs and CLIs
  When running AutoUpgrade on Microsoft Windows systems, Oracle recommends additional best practices with access control lists (ACLs) and command-line interfaces (CLIs).