Microsoft Windows Upgrades to Oracle Database 23ai

D Microsoft Windows Upgrades to Oracle Database 23ai

For single-instance and Oracle Real Application Clusters (Oracle RAC) upgrades, you must use either Database Upgrade Assistant (DBUA), or a manual upgrade procedure.

Upgrading Microsoft Windows with Oracle Database Upgrade Assistant (DBUA)
Database Upgrade Assistant (DBUA) provides a graphical user interface to guide you through the upgrade of Oracle Database.

Upgrading Microsoft Windows with Oracle Database Upgrade Assistant (DBUA)

Database Upgrade Assistant (DBUA) provides a graphical user interface to guide you through the upgrade of Oracle Database.

Note:

At the time of this release, AutoUpgrade is not supported for use with Microsoft Windows upgrades. DBUA is supported only for Oracle Database upgrades on Microsoft Windows.

Using Database Upgrade Assistant (DBUA) for Microsoft Windows Upgrades
In Oracle Database 23ai, you can use DBUA to complete single-instance or Oracle Real Application Clusters upgrades.
About Stopping DBUA When Upgrading
You must complete an upgrade manually if you stop DBUA.
How DBUA Processes the Upgrade for Oracle Database
You can start DBUA as part of the database software installation, or you can start it manually after installing the software.
Using DBUA to Upgrade the Database on Microsoft Windows
To upgrade a database using the DBUA graphical user interface, perform these steps from within the new Oracle home.
Using DBUA in Silent Mode to Upgrade Oracle Database
You can DBUA with the -silent command line option to carry out noninteractive (“silent”) upgrades using DBUA.

Parent topic: Microsoft Windows Upgrades to Oracle Database 23ai

Using Database Upgrade Assistant (DBUA) for Microsoft Windows Upgrades

In Oracle Database 23ai, you can use DBUA to complete single-instance or Oracle Real Application Clusters upgrades.

Note:

This procedure applies only to Microsoft Windows platforms. For all other platforms, use AutoUpgrade.

DBUA helps you to perform the following tasks:

Upgrade and configure a database to run with the new Oracle Database release
Migrate your new Oracle Database from one Oracle home to another of the same version.

DBUA automates the upgrade process by performing all the tasks that otherwise would be done manually. DBUA makes appropriate recommendations for configuration options such as tablespaces, redo logs, and so on. You can then act on these recommendations. For example, DBUA recommends sizing information for the SYSAUX tablespace.

DBUA also enables you to move your database from one Oracle home to another Oracle home of the same version. If you have multiple databases sharing the same Oracle home, then you must stop all databases in the Oracle home before you patch it.

You can reduce the downtime by carrying out the following steps:

Installing another Oracle home of the same version
Patching the new Oracle home
Use DBCA to migrate each database to the new Oracle home in succession.

Preparing for the Upgrade

Before upgrading your database, DBUA checks for invalid user accounts or roles, invalid datatypes, or desupported character sets. DBUA also checks for adequate resources, including rollback segments and free disk space and, optionally, backs up all necessary files.

DBUA does not begin the upgrade until it completes all the initialization steps.

Note:

Ensure that all the applications that are associated with the Oracle Database Service are closed before clicking Finish, in the DBUA Summary page. For example, ensure that the Services Panel, Registry Editor, and the Performance Monitor are closed.

If any applications associated with the Oracle Database Service are left open during upgrade, or if you are restoring the database after an upgrade failure, then you can see the following error message:

Error in Process: ORACLE_BASE\ORACLE_HOME\bin\oradim.exe Upgrade failed due to running the step "Upgrading Oracle 
Server""DIM-00020: A service for this SID is already created. Please enter a different SID name. No action has 
been taken O/S-Error: (OS 1072) The specified service has been marked for deletion."

Workaround: restart the machine. Before you restart DBCA, manually recreate the Oracle Database Service by using the ORADIM utility.

Oracle Real Application Clusters (Oracle RAC) Support

DBUA is fully compliant with Oracle RAC environments. In Oracle RAC environments, DBUA upgrades all the database and configuration files on all the nodes in a cluster.

During the Upgrade

DBUA has built-in intelligence to modify or create new required tablespaces automatically. DBUA also runs the appropriate script, archives the redo logs, and disables archiving during an upgrade. While the upgrade is running, DBUA shows the upgrade progress for each component. DBUA writes detailed trace and logs 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 (init.ora, spfile, and listener files) in the new Oracle home.

Oracle Real Application Clusters (Oracle RAC) Support

DBUA is fully compliant with Oracle RAC environments. In Oracle RAC environments, DBUA upgrades all the database and configuration files on all the nodes in a cluster.

Support for Silent Mode

DBUA supports a silent mode of operation where no user interface is presented to the user. Silent mode enables you to use a single command for the upgrade. For example:

dbua -silent -dbName sales

For command-line features, use the -help option of DBUA. For example:

dbua -help

To start DBUA:

Parent topic: Upgrading Microsoft Windows with Oracle Database Upgrade Assistant (DBUA)

About Stopping DBUA When Upgrading

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 upgrade procedure. You cannot go back to the original Oracle Database server unless you restore your database.

Parent topic: Upgrading Microsoft Windows with Oracle Database Upgrade Assistant (DBUA)

How DBUA Processes the Upgrade for Oracle 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 preupgrade steps are completed.

Related Topics

Tasks to Prepare for Oracle Database Upgrades

Parent topic: Upgrading Microsoft Windows with Oracle Database Upgrade Assistant (DBUA)

Using DBUA to Upgrade the Database on Microsoft Windows

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

Note:

This procedure applies for Oracle Database upgrades on Microsoft Windows platforms only. For all other platforms, use AutoUpgrade.

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.

Start Oracle Database Upgrade Assistant (DBUA) from the Oracle home where the new database software is installed.

Select Start, then Programs, then Oracle HOME_NAME, then Configuration and Migration Tools, and then Database Upgrade Assistant.
The Select Database window displays. If you have earlier release Oracle Database installations, then these installations are listed as available to upgrade.
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.
- 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.
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.

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.
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.

Provide the Oracle home user name, and provide the password for this user account, and click Next.
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.

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.
The Select Upgrade Options window displays.

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.
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 button 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. Select a path where you want to place the backup.
  - Create a New Partial Offline RMAN Backup with R/O User Tablespace. If you select this option, then user tablespaces are placed into read-only mode during the upgrade, and a new partial offline RMAN backup is created.
  - Use Latest Available Full RMAN Backup. If you select this option, then click 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.
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.

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.
The Configure Management window appears. In the Configure Management window, select the management options:
- Configure Enterprise Manager (EM) database express
  
  Oracle Enterprise Manager Database Express (EM Express) is desupported in Oracle Database Release 23ai.
  
  EM Express is a web-based database management tool that is built inside Oracle Database. It supports key performance management and basic database administration functions. EM Express was deprecated in Oracle Database 21c. Many of EM Express's capabilities are now available in Oracle Cloud Infrastructure (OCI) Database Management service, Oracle Enterprise Manager Cloud Control, or Oracle SQL Developer.
- 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.
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.

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.
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, 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.
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.
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.

Parent topic: Upgrading Microsoft Windows with Oracle Database Upgrade Assistant (DBUA)

Using DBUA in Silent Mode to Upgrade Oracle Database

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.

Parent topic: Upgrading Microsoft Windows with Oracle Database Upgrade Assistant (DBUA)

Running DBUA in Silent Mode

Use this procedure to start DBUA in noninteractive (or “silent”) mode.

To start DBUA in silent mode, enter the dbua -silent -sid command. The command starts DBUA in silent mode, and identifies the database that you want to upgrade.

For example, enter the following command, where the database name is ORCL:
```
dbua -silent -sid ORCL &
```

Parent topic: Using DBUA in Silent Mode to Upgrade Oracle Database

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.

Purpose

When you run DBUA by using the command-line option, you can specify all valid DBUA options in a script form. The script form enables you to avoid entering configuration information in a graphic user interface dialog.

Note:

Database Upgrade Assistant (DBUA) is desupported except on Windows as of Oracle Database 23.4. Oracle recommends using AutoUpgrade to upgrade your database.

To improve the reliability and support for Oracle Database upgrades, Oracle is desupporting Database Upgrade Assistant (DBUA), manual upgrades using the Parallel Upgrade Utility (catctl.pl) , and the database upgrade scripts dbupgrade and dbupgrade.cmd. Use AutoUpgrade for Oracle Database upgrades. Replacing obsolete upgrade methods enables Oracle to focus on improving and extending the features and manageability of the AutoUpgrade utility.

Oracle Enterprise Manager Database Express (EM Express) is desupported in Oracle Database Release 23ai.

EM Express is a web-based database management tool that is built inside Oracle Database. It supports key performance management and basic database administration functions. EM Express was deprecated in Oracle Database 21c. Many of EM Express's capabilities are now available in Oracle Cloud Infrastructure (OCI) Database Management service, Oracle Enterprise Manager Cloud Control, or Oracle SQL Developer.

File Path

$ORACLE_HOME/directory_name

Syntax

Usage: dbua [flag] [option]

Flags

-createPartialBackup  Flag to create a new offline partial RMAN backup by setting the user tablespaces in Read-Only mode.
        -backupLocation  Flag to identify the path for the RMAN backup.
        -disableParallelUpgrade  Flag to disable the parallel execution of database upgrade.
        -executePreReqs  Flag to run the preupgrade checks alone for the specified database.
                -sid | -dbName
                -sid
                -dbName
        -help - Shows this usage help.
        -ignorePreReqs Ignore error conditions in preupgrade checks.
        -silent Runs configuration in silent mode.
                -sid | -dbName
                -sid
                -dbName
        -skipListenersMigration Flag to bypass the listener migration process as part of the database upgrade.

Options

The DBUA command line options are as follows:

[-asmsnmpPassword - ASMSNMP user password]
        [-backupLocation - Directory-where-you-want-to-back-up-your-database-before-starting-upgrade
       [-createGRP - [True | false] Create a guaranteed restore point when database is in archive log and flashback mode.
        [-createListener - [true [listenrName:lsnrPort] | false]] Create a listener in later release Oracle home. If true, then add: listenerName:lsnrPort
        [-dbName - database-name]
                [-oracleHome - Oracle-home-path-of-database]
                [-sysDBAUserName - User-name-with-SYSDBA-privileges]
                        [-sysDBAPassword - Password-for-sysDBAUserName-user-name]
       [-dbsnmpPassword - DBSNMP-user-password]
        [-disableUpgradeScriptLogging - [true | false]] This command disables the detailed log generation for running SQL scripts during the upgrade process. By default this is enabled. To enable the log generation, don't specify this command.
        [-emConfiguration - [DBEXPRESS | CENTRAL | BOTH | NONE] Specifies Enterprise Manager information.
                [-dbsnmpPassword - DBSNMP-user password]
                [-emPassword - Enterprise-Manager-administration-user-password]
                [-emUser - Enterprise-Manager-Administration-username-to-add-or-modify-targets]
                [-emExpressPort - port-for-EM-Express]
                [-omsHost - Enterprise-Manager-management-server-host-name]
               [-omsPort - Enterprise-Manager-management-server-port-number]
                [-asmsnmpPassword - ASMSNMP-user-password]
        [-ignoreScriptErrors - [true | false]] Specify this flag for ignoring ORA errors during custom scripts.
        [-initParam - name=value,name=value,...] Specify a comma separated list of initialization parameter values of the
                       format name=value,name=value
                [-initParamsEscapeChar - [escape character] Escape character for comma when a specific initParam has multiple values. If the escape character is not specified, then backslash (\) is the default escape
        [-excludeInitParams - comma-delimited-list-of-initialization-parameters-to-exclude]
        [-keepDeprecatedParams - [true | false]] Retain (or not) deprecated parameters during database upgrade.
        [-localListenerWithoutAlias] Sets LOCAL_LISTENER without TNS Alias.
        [-listeners listenerName:Oracle Home, listenerName:Oracle Home, …] Registers the database with existing listeners. Specify listeners by comma-delimited list in the form listenerName:Oracle Home. Listeners from earlier release Oracle homes are migrated to newer release,lsnrName2 or -listeners lsnrName1:Oracle home path,-listeners lsnrName2:Oracle home path. DBUA searches specified listeners from the Grid Infrastructure home (if configured), the target home, and source home.
        [-localRacSid - local-System-Identifier-of-cluster-database] Use if if the cluster database is not registered in the Oracle Cluster Registry (OCR).
        [-logDir - Path-to-a-custom-log-directory]
       [-newGlobalDbName - New Global Database Name] This option can only be used for Oracle Express Edition upgrades
        [-newSid - New System Identifier] This option can only be used for Oracle Express Edition upgrades
        [-newInitParam - name=value,name=value,...] Specify a comma-delimited list of initialization parameter values of the format name=value,name=value. Use this option to specify parameters that are allowed only on the target Oracle home.
                [-initParamsEscapeChar - escape character] Specify an escape character for comma when a specific initParam has multiple values. If the escape character is not specified, then backslash (\) is the default escape.
        [-oracleHomeUserPassword - Oracle-Home-user-password]
        [-pdbs - [All | NONE | pdb, pdb,…]] Specify ALL to select all PDBs, NONE to select no PDBs, or provide a comma-delimited list with
                       the names of the pluggable databases (PDBs) that you want upgraded.
                -sid | -dbName
                -sid - System Identifier
                        [-oracleHome - Oracle home path of the database]
                        [-sysDBAUserName - User-name-with-SYSDBA-privileges]
                                [-sysDBAPassword - Password-for-sysDBAUserName-user-name]
                -dbName - Database-Name
                        [-oracleHome - Oracle-home-path-of-database]
                        [-sysDBAUserName - User-name-with-SYSDBA-privileges]
                                [-sysDBAPassword - Password-for-sysDBAUserName-user-name]
        [-pdbsWithPriority - pdb:priority, pdb:priority, pdb:priority,...] Specify a comma-delimited list of pluggable databases (PDB) that you want upgraded, including their corresponding priorities (1 the top priority).
                -sid | -dbName
                -sid - system-identifier
                        [-oracleHome - Oracle-home-path-of-database
                        [-sysDBAUserName - User-name-with-SYSDBA-privileges]
                                [-sysDBAPassword - Password-for-sysDBAUserName-user-name]
                -dbName - database-name
                        [-oracleHome - Oracle-home-path-of-the-database]
                        [-sysDBAUserName - User-name-with-SYSDBA-privileges]
                                [-sysDBAPassword - Password-for-sysDBAUserName-user-name]
        [-performFixUp - [true | false] Enable or disable fixups for the silent upgrade mode.
       [-postUpgradeScripts - SQLscript, SQLscript,…] Specify a comma-delimited list of SQL scripts with their complete pathnames. After the upgrade completes, these SQL scripts are run.
        [-preUpgradeScripts - SQLscript, SQLscript,…]Specify a comma-delimited list of SQL scripts with their complete pathnames. Before the upgrade starts, these SQL scripts are run.
        [-recompile_invalid_objects - [true | false]] If true, then recompiles invalid objects as part of the upgrade.
        [-upgrade_parallelism - number] Numeric value for the number of CPUs that you want to use for parallel upgrade.
        [-upgradeTimezone - [true | false]] If true, then upgrades the timezone files of the database during the upgrade.
        [-upgradeXML - Path-to-existing-preupgrade-XML-file] This option only applies to in-place database upgrades.
        [-useExistingBackup - [true | false]] Use to enable restoration of the database using existing RMAN backup.
        [-useGRP - Name-of-existing-guaranteed-restore-point] Use to enable restoration of the database using a specified guaranteed restore point.

Example D-1 Selecting a Database for Upgrade with DBUA

The following command selects the database orcl for upgrade:

dbua -sid orcl

Note:

You can use DBUA commands to set passwords. If the default Oracle Database security settings are in place, then passwords must be at least eight characters, and passwords such as welcome and oracle are not allowed.

Example D-2 Selecting a Database for Upgrade with DBUA Using Noninteractive ("Silent") Option

The following command selects the database orcl for upgrade using the noninteractive ("silent") option:

dbua -silent -sid orcl

Example D-3 Use Cases for Running DBUA in Noninteractive (”Silent") Mode

The examples that follow illustrate how you can use DBUA with the noninteractive (”silent") option to carry out a variety of upgrade scenarios.

dbua -silent -sid sidb112 -backupLocation /u01/sidb1123/backup -sysDBAUserName sys -sysDBAPassword r3aDy2upg -oracleHome /u01/app/product/11.2.0/dbhome_1 -upgradeTimezone true dbua -silent -sid sidb1123 -backupLocation /u01/sidb1123/backup -sysDBAUserName sys -sysDBAPassword r3aDy2upg -oracleHome /u01/app/product/11.2.0/dbhome_1 -upgrade_parallelism 1 -upgradeTimezone true

dbua -silent -sid db1124 -backupLocation /u01/sidb1123/backup -sysDBAUserName sys -sysDBAPassword r3aDy2upg -performFixUp true -upgradeTimezone true

dbua -silent -dbName rdbcdb -oracleHome /u01/app/product/11.2.0/dbhome_1 -sysDBAUserName sys -sysDBAPassword r3aDy2upg -backupLocation /u01/sidb1123/backup -recompile_invalid_objects true -upgradeTimezone true

dbua -silent -dbName amdb -oracleHome /u01/app/product/11.2.0/dbhome_1 -sysDBAUserName sys -sysDBAPassword r3aDy2upg -recompile_invalid_objects true -useGRP GRP_20170620bfupgrade -upgradeTimezone true

dbua -silent -dbName rdb12 -oracleHome /u01/app/product/12.2.0/dbhome_2 -sysDBAUserName sys -sysDBAPassword r3aDy2upg -backupLocation /u01/sidb12/backup -recompile_invalid_objects true -upgradeTimezone true

dbua -silent -dbName ronedb -oracleHome /u01/app/product/12.2.0/dbhome_2 -sysDBAUserName sys -sysDBAPassword r3aDy2upg -recompile_invalid_objects true -upgradeTimezone true -createGRP true

Note:

Refer to Oracle Database Security Guide for information about security best practices.

Related Topics

Oracle Database Security Guide

Parent topic: Using DBUA in Silent Mode to Upgrade Oracle Database