Review this topic to use Database Upgrade Assistant (DBUA) for multitenant architecture and non-CDB Oracle Database upgrades.

If Oracle Database Vault is enabled, then review the topic “Requirement for Upgrading Oracle Databases That Use Oracle Database Vault”.

So that DBUA can perform preupgrade checks, you must download and install the most recent AutoUpgrade utility.

You can use DBUA to upgrade multitenant architecture container databases (CDB), pluggable databases (PDBs), and non-CDB databases. The procedures are the same, but the choices you must make and the behavior of DBUA are different, depending on the type of upgrade:

• Download the latest preupgrade.jar version from My Oracle Support Document 884522.1. Download the file into the Oracle Database 19c Oracle home, under Oracle_home/rdbms/admin, and unzip the file in that location. Then follow the instructions in this guide, in "Pre-Upgrade Information Tool (preupgrade.jar) Command"
• To use guaranteed restore points, ensure that the database ARCHIVE LOG and FLASHBACK modes are on during upgrade. You can confirm that they are on by entering the following SQL command:

  SQL> select log_mode,flashback_on from v$database;

• If the database instance is not running, then DBUA tries to start the instance. If the instance is up and running, then DBUA connects to it.

• If you restore your database manually (not using DBUA), then before starting DBUA, remove the Welcome_SID.txt file, which is located in the directory ORACLE_HOME/cfgtoollogs/dbua/logs/. If DBUA finds this file, then DBUA starts in a re-run operation.

• Restore scripts generally enable you to restore your database (Non-CDB single instance, high availability, or Oracle RAC) back to the earlier release and earlier Oracle home location. However, if you have registered your database with Oracle Internet Directory (OID), then the restore script cannot unregister Oracle Internet Directory. You must log in as an authorized user, and unregister the later release database manually.

You must complete an upgrade manually if you stop DBUA.

If you stop the upgrade, but do not restore the database, then you cannot continue to upgrade using DBUA. You must instead continue the upgrade using the manual (command line) upgrade procedure. You cannot go back to the original Oracle Database server unless you restore your database.

You can start DBUA as part of the database software installation, or you can start it manually after installing the software.

If you install the new Oracle Database software, and you specify that you are upgrading an existing Oracle database, then DBUA starts automatically. You can also start DBUA independently after the installation is completed.

While the upgrade is in process, DBUA shows the upgrade progress for each component. DBUA writes detailed trace and log files and produces a complete HTML report for later reference. To enhance security, DBUA automatically locks new user accounts in the upgraded database. DBUA then proceeds to create new configuration files (parameter and listener files) in the new Oracle home.

DBUA does not begin the upgrade process until all the pre-upgrade steps are completed.

During the upgrade, DBUA automatically runs the appropriate upgrade scripts to automate the upgrade and minimize downtime.

During the prerequisite phase, DBUA runs AutoUpgrade using the preupgrade parameter (autoupgrade.jar -preupgrade -mode), which runs database checks and preupgrade fixups that fix most issues before you start an upgrade.

DBUA uses the following logic to modify or create new required tablespaces:

• If the data files are auto-extensible and have enough disk space to grow, then DBUA continues with the upgrade.
• If the data files are not auto-extensible, then DBUA prompts you and makes the files auto-extensible.
• If the tablespaces are auto-extensible and the MAXSIZE initialization parameter needs adjustment, then DBUA prompts you to for this adjustment, and adjusts the MAXSIZE parameter.
• If there is not enough disk space to grow, then DBUA prompts you to create space by adding more data files. DBUA does not automatically add new data files, because DBUA cannot determine where to create the files.

DBUA addresses many issues found during the prerequisite phase. For example, DBUA can ensure that the correct time zone file is used, and make ACL adjustments for network access control lists.

During the upgrade phase, DBUA runs catctl.pl, which runs the upgrade processes in parallel instead of serially. Parallel runs optimize utilization of CPU resources to hasten the upgrade and minimize downtime.

Use this procedure to migrate Oracle Databases to another Oracle Database 18c or later home.

With Oracle Database 18c and later releases, you can use Database Upgrade Assistant (DBUA) to migrate Oracle Database databases from an existing Oracle home to another Oracle home.

1. Start DBUA.

   DBUA opens the Select Database window.

   All databases on the server are listed. DBUA indicates the type of operation that you can perform for each database (upgrade, move, in place), depending on the database release and location.

   
   Description of the illustration dbua_11.png

   Select a database that you want to move to the new Oracle home. If you have not enabled operating system authentication for the database, then provide the SYSDBA user name and password for the database that you select.

   Click Next. The Move Database Options window appears.

2. In the Select Move Options window, you can specify custom SQL scripts that you want to run after moving the database, and identify where the files are located.

   
   Description of the illustration dbua_12.png

   Click Next. The Configure Network window appears.

3. On single-instance systems, you can either select an existing listener, or create a new listener. If you create a new listener, then you must provide a listener name, and a port number for the listener.

   
   Description of the illustration dbua3mvnetwork.png

   Click Next. The Database Move Summary window appears.

4. Review the summary for the move operation and click Next.

5. The Setup window appears, which shows DBUA processes as it moves the database.

6. When the move operation completes, click Finish.

7. The Results window appears. You can review the source and target database information, and check move steps, or check log files. When you are finished with your review, click Close.

To upgrade a database using the DBUA graphical user interface, perform these steps from within the new Oracle home.

On Microsoft Windows systems (Windows), run DBUA either as an Oracle Database administrative user (a user with the operating system-assigned ORA_DBA role), or as the Oracle installation owner account.

1. Start Oracle Database Upgrade Assistant (DBUA) from the Oracle home where the new database software is installed. The dbua executable is located in the directory path ORACLE_HOME/bin.

   • On Linux or Unix platforms, log in as a user with SYSDBA privileges, and enter the following command at a system prompt in the new home for Oracle Database 19c:

     ./dbua

   • On Windows operating systems, select Start, then Programs, then Oracle HOME_NAME, then Configuration and Migration Tools, and then Database Upgrade Assistant.

2. The Select Database window displays. If you have earlier release Oracle Database installations, then these installations are listed as available to upgrade.
   
   Description of the illustration dbua_1.png

   If you need help on any DBUA window, or if you want to consult more documentation about DBUA, then click Help to open the online help.

   If needed, enter the SYSDBA user name and password for the database that you select.

   If you run DBUA from a user account that does not have SYSDBA privileges, or if the source database does not have operating system authentication, then you must enter the user name and password credentials to enable SYSDBA privileges for the selected database. If the user account you use has SYSDBA privileges, or you used operating system authentication, then you do not need to enter the user name and password.

   Click Next after making your selection.

   Note:

   • You can select only one database at a time.

   • With single-instance upgrades, if the database does not appear in the list, then check to see if an entry with the database name exists in /etc/oratab. If the database is not listed there, then direct DBUA to upgrade particular databases:

     • If your single-instance database is not listed in /etc/oratab, and DBUA can connect to the database, then you can direct DBUA to upgrade that database explicitly by starting DBUA using the command-line arguments -sid Oracle_SID, -oracleHome Oracle_home, and sysDBAPassword password as a command-line argument. For example:

       dbua -sid Oracle_SID –oracleHome /u01/app/oracle/18.1.0/dbhome1 -sysDBAUserName SYS -sysDBAPassword password

   • If your account does not have SYSDBA privileges, or you do not have operating system authentication set up, then you can use the following syntax to connect, where mydb is your Oracle Database SID, username is a user name with SYSDBA privileges, and password is that user name’s password:

     dbua -sid mydb –oracleHome /u01/app/oracle/18.1.0/dbhome1 -sysDBAUserName - username -sysDBAPassword - password

   • Oracle Real Application Clusters (Oracle RAC) upgrades: If the database does not appear on the list, then enter the following crsctl command to check for Oracle RAC instances:

     crsctl status resource -t

     You can also enter the following command to check for a particular Oracle RAC database, where db_name is the Oracle RAC database name:

     crsctl status resource ora.db_name.db

   • On Microsoft Windows, the following security changes affect authentication and user accounts:

     • For security reasons, Windows NTS authentication using the NTLM protocol is no longer supported. Kerberos authentication is the only supported authentication. In this release, NTS does not work either in Windows NT domains, or in domains with Windows NT controllers.

     • Oracle uses standard Microsoft Windows user accounts instead of the Windows LocalSystem account to run Oracle database services. Reducing the account access privileges for the Oracle installation owner provides better security on Microsoft Windows.

3. If the selected database is a multitenant container database (CDB), then DBUA displays the Pluggable Databases window. The Pluggable Databases window lists the pluggable databases contained in the CDB. The listed PDBs are upgraded as part of the upgrade for the selected CDB.

   
   Description of the illustration dbua_2.png

   You can select the upgrade priority for PDBs. Click in the priority column for each PDB, and enter a numeric value for upgrade priority, where 1 is upgraded first, 2 is upgraded second, and so on.

   By default, CDB$ROOT, PDB$SEED, and all PDBs that are plugged into the CDB are upgraded. If you do not want some PDBs to be upgraded now, then unplug those PDBs.

   When you have completed selecting PDBs and upgrade priorities, click Next.

4. Windows platforms only: If the upgrade target home is a secure home that is associated with an Oracle home user, then the Specify Oracle Home User Password window opens. For other platforms, proceed to the next step.

   
   Description of the illustration dbua3a-win.png

   Provide the Oracle home user name, and provide the password for this user account, and click Next.

5. The Prerequisite Checks window opens. DBUA analyzes the databases, performing preupgrade checks and displaying warnings as necessary. The following is a list of examples of DBUA checks, and of actions that DBUA performs on the database:

   • Empty database recycle bin.

   • Identify invalid objects.

   • Identify deprecated and desupported initialization parameters.

   • Identify time zone data file version.

   The analysis takes several minutes to complete.

   When DBUA finishes its analysis, the Prerequisite Checks window displays again, showing the results of the checks.

   
   Description of the illustration dbua_3.png

   The Prerequisite Checks window shows the checks that DBUA has completed, and the severity of any errors discovered. When DBUA finds errors, it indicates which errors are fixable, and what action you can take to correct the error.

   Select Fix & Check Again if any errors that DBUA can fix appear.

   If DBUA detects errors that it cannot correct, then fix the cause of the error manually, and select Check Again.

   If DBUA finds no errors or warnings, then the DBUA automatically bypasses this window and proceeds to the next window.

   When you have fixed detected errors, click Next.

6. The Select Upgrade Options window displays.

   
   Description of the illustration dbua_4.png

   This window provides the following options:

   Enable Parallel Upgrade

   Select this option if you want to enable parallelism during the upgrade process. Running upgrade processes in parallel reduces the time required to perform the upgrade, based on the number of CPUs available to handle the running of scripts and processes simultaneously.

   Recompile Invalid Objects During Post Upgrade

   This option recompiles all invalid PL/SQL modules after the upgrade is complete. If you do not have DBUA recompile invalid objects in its post-upgrade phase, then you must manually recompile invalid objects after the database is upgraded.

   Upgrade Time Zone Data

   This option updates the time zone data file for this release. If you do not select this option, then you must update the time zone configuration file manually after the upgrade.

   Specify custom SQL scripts to be executed.

   If you want to run custom SQL scripts as part of your upgrade, then select this option. As needed, click Browse for the Before Upgrade or After Upgrade input fields. Navigate to the location where your custom SQL scripts are located.

   When you have made your selections, click Next.

7. The Select Recovery Options window appears. To recover the database if a failure occurs during upgrade, select from one of the following options:

   • Use Flashback and Guaranteed Restore Point.

     You can create a new Guaranteed Restore Point, or use an existing one. If you use an existing restore point, then click the selection field to select the restore point that you want to use.

     Note:

     If the database that you are upgrading has Oracle Data Guard physical standbys, then you must first create a guaranteed restore point on each standby before you create one on the primary database. If you do not create restore points on each standby first, then you must recreate all standby databases again after using the guaranteed restore point to downgrade the primary database. After the upgrade is successful, you must manually drop all guaranteed restore points on the standbys.

   • Use RMAN Backup

     Select among the following RMAN backup options:

     • Create a new Offline RMAN backup. If you select this option, then provide a path where you want to place the backup.
     • Create a New Partial Offline RMAN Backup with User Tablespace. If you select this option, then user tablespaces are placed into read-only mode during the upgrade.
     • Use the Latest Available Full RMAN Backup. If you select this option, then click View/Edit Restore Script to select the backup that you want to use.

   • I have my own backup and restore strategy.

     Select this option only if you have a third-party backup solution in place for your existing database.

   When you have made your selections, click Next.

8. For single-instance database installations, the Configure Network window opens. Select one or more listeners from the source Oracle home that you want to migrate to the new upgraded Oracle home, or create a new listener during installation.

   
   Description of the illustration dbua_6.png

   The Listener Selection area of the Network Configuration window shows a table with the following columns:

   • Select column. Select the listeners that you want to update.

   • Name This column shows listener names.

   • Port This column shows the ports on which listeners are configured.

   • Oracle Home This column shows the Oracle home where listeners are configured.

   • Status This column shows the listener status (up or down).

   • Migrate Select this column, and choose Yes to migrate, or No if you do not want to migrate.

   You can also select to create a new listener. If you create a new listener, then provide the listener name, the Oracle home where you want it placed, and the port that you want to configure the listener to monitor.

   After you make your choices, DBUA completes the following steps for any listeners that you migrate:

   1. DBUA adds the selected listener to the listener.ora file of the target Oracle home, and starts it.

   2. DBUA removes the entry of the upgraded database from the old (source) listener.ora file.

   3. DBUA reloads the listener.ora file in both the source and target Oracle Database environments.

   Note:

   If there are other databases registered with the same listener, then their new client connection requests can be affected during listener migration.

   Click Next when you have completed your choices.

9. The Configure Management window appears. In the Configure Management window, select the management options:

   
   Description of the illustration dbua_7.png

   • Configure Enterprise Manager (EM) database express

     Oracle Enterprise Manager Database Express is a web-based database management application that is built into Oracle Database. EM Express replaces the DB Control component that was available in earlier releases. If you select to configure Enterprise Manager Database Express, then Enter the EM Database Express Port number. For example: 5500. You can also select the check box to configure the express port as the global port.

   • Register with Enterprise Manager (EM) Cloud Control

     Registering with Oracle Enterprise Manager Cloud Control adds the database and its related entities, such as Listener, Oracle ASM disk groups, and Oracle Clusterware, as targets that you can manage with EM Cloud Control.

     If you select this option, then you must provide information in the following fields:

     • OMS Host

     • OMS Port

     • EM Admin Username

     • EM Admin Password

     • DBSNMP User Password

     • ASMSNMP User Password

   When you have completed entering information, click Next.

10. The Summary window opens. The Summary window shows the information that you have provided for the upgrade. Scroll down the list to review the information. The summary includes information such as the following:

    • Source Database

    • Target Database

    • Pluggable Databases

    • Pre-Upgrade Checks

    • Initialization Parameters changes

    • Timezone Upgrade

    Check your selections. Then, either select a link to the item that you want to change, or click Back to go to earlier pages, or select Finish:

    • If you see information in the Summary window that you want to correct, then click a link on an item that you want to update, or click Back to navigate backward through the DBUA configuration interview.

    • Click Finish if the information that you see in the Summary window is correct. The upgrade begins after you select Finish.

    The Progress window displays with the progress bar, as DBUA begins the upgrade. The Progress window displays a table that shows the steps DBUA is completing during the upgrade. This table shows the time duration, and the upgrade steps status as the upgrade proceeds. DBUA provides a Stop button in case you must cancel the upgrade at this point.

    
    Description of the illustration dbua_9.png

    When the upgrade has progressed through finishing the upgrade of the CDB root and each PDB seed, the Progress window marks the status as Finished.

11. After the upgrade is complete, the Results window opens. The Results window displays information about the original database, and about the upgraded database. The Upgrade Results report also shows changes that DBUA made to the initialization parameters. If you are upgrading a multitenant architecture database, then the Results window also shows pluggable databases, and the directory where log files are stored after the upgrade. Scroll down to see more details about preupgrade checks. If the upgrade is successful, then the Upgrade Results field reports the results, and you do not see warning messages. If the upgrade was unsuccessful, as this example image shows, then the Restore Database button is displayed on the lower right corner below the display field. You can click this button to start a database restoration.

    
    Description of the illustration dbua_10.png

12. Optional: Examine the log files to obtain more details about the upgrade process. If the Oracle base environment variable is set, then the DBUA log files are located in the path /ORACLE_BASE/cfgtoollogs/dbua/upgradesession_timestamp/SID. If Oracle base is not set, then the DBUA log files are located in the path /ORACLE_HOME/cfgtoollogs/dbua/upgradesession_timestamp/SID

    Note:

    An HTML version of the Upgrade Results window is also saved in the log files directory. You can click the links in this HTML window to view the log windows in your browser.

    If you are satisfied with the upgrade results, then click Close to quit DBUA.

13. After your upgrade is completed, carry out post-upgrade procedures described in this book. When you have completed post-upgrade procedures, your upgraded database is ready to use.

You can DBUA with the -silent command line option to carry out noninteractive (“silent”) upgrades using DBUA.

. In silent mode, DBUA does not present a user interface. DBUA writes messages (including information, errors, and warnings) to a log file in ORACLE_HOME/cfgtools/dbua/upgradesession_timestamp, where session_timestamp represents the timestamp for the upgrade that DBUA has run. Oracle strongly recommends that you read the resulting DBUA log files to ensure a successful upgrade.

• Running DBUA in Silent Mode
  Use this procedure to start DBUA in noninteractive (or “silent”) mode.
• DBUA Command-Line Syntax for Active and Silent Mode
  Use this syntax to run Database Upgrade Assistant (DBUA) either interactively, or by using the -silent option.

Review this topic if your Oracle Database homes are owned by different operating system user accounts, or you encounter an upgrade.xml not found error.

DBUA upgrades by default assume that both the source Oracle home and the target Oracle home are owned by the same user. If each Oracle home is not owned by the same user, then you must change to database file permissions and pass additional parameters to DBUA. If you do not do this, then during upgrade, the DBUA Prerequisite Checks page reports upgrade.xml not found errors. You are not permitted to proceed with the upgrade until this error is corrected.

• All Oracle Database installation owners should have the group that you designate as the OINSTALL group (or Oracle Inventory group) as their primary group. Ensure all database files (data files, the redo file, control files, archive log destination, recovery area, SPFILE, and password file) are readable and writable by both the new target release and the source (earlier) release binary owners. If this is not the case, then confirm that each installation owner has the same group as their primary group, and ensure that members of the OINSTALL group have read/write access to all of the earlier release and later release Oracle Database files and directories.

• Run DBUA by specifying the -logdir command line option, and provide a directory to which both the new release and earlier release binary owners can write. For example: /tmp. DBUA uses the directory you designate with the logdir parameter to store the output from the Pre-upgrade Information Tool, and to store any DBUA log files generated during the upgrade. You run the Pre-Upgrade Information tool from the earlier release Oracle Database instance as the earlier release Oracle Database installation owner user account.

  For example:

  dbua -logdir /tmp