Complete the following steps to upgrade a database using DBUA. If you need help at any page or want to consult more documentation about DBUA, then click the Help button to access the online Help.
To upgrade a database using DBUA:
Start DBUA. See "Starting DBUA."
At the Select Operation page of DBUA, choose Upgrade Oracle Database. Then, click Next.
The Select Database page appears.
On the Select Database page, choose the database you want to upgrade to Oracle Database 12c Release 1 (12.1.0.2) from the Source Database Oracle Home list. DBUA fills in information about the database. DBUA fills in the information for the release and selects the Oracle database associated with the selected Oracle home.
If the source database does not have operating system authentication, then DBUA prompts you for the user name and password of an account with SYSDBA privilege for the database.
You can select only one database at a time. If the database that you want to upgrade does not appear in the list, then make sure an entry with the database name exists in the oratab file in the etc directory.
If you run DBUA from a user account that does not have SYSDBA privileges, then enter the user name and password for an account with SYSDBA privilege for the selected database.
Click Next.
If the selected database is a multitenant container database (CDB), then DBUA displays the Pluggable Databases page. The Pluggable Databases page lists the pluggable databases (PDBs) contained in the CDB, which will be upgraded along with the selected CDB.
Click Next.
DBUA analyzes the database, performing pre-upgrade checks and displaying warnings as necessary. Examples of DBUA database checks include:
Empty database recycle bin
Invalid objects
Deprecated and desupported initialization parameters
Time zone data file version
When DBUA finishes its analysis, the Prerequisite Checks page appears. The analysis takes several minutes to complete.
The Prerequisite Checks page shows the validation and results, the severity, whether the result is fixable if there is a problem, and the action you can take. When you select the validation result, the Fixable column displays whether the result can be fixed or not. The Action drop-down list shows actions you can take. For example, select Fix for DBUA to run a script or command to fix the problem.
When you select a result in the Validation column, DBUA displays information about the result in the bottom area of the screen.
Click the more details link in the text information area. The Validation Details box appears with more information.
If there are validation errors or warnings and these are fixable, you can select an Action to take.
Click Next.
The Upgrade Options page appears with the Upgrade Options tab selected.
The Upgrade Options page with the Upgrade Options tab selected provides the following options:
Select Upgrade Parallelism
The Select Upgrade Parallelism section enables the degree of parallelism for the upgrade process. This option reduces the time needed to perform the upgrade, based on the number of CPUs available to handle the running of scripts and processes simultaneously.
By default, DBUA sets Upgrade Parallelism to the number of CPUs or 2 if the number of CPUs is less than 4. You can adjust this default value by selecting a new value from the Select Upgrade Parallelism list.
Recompile Invalid Objects During Post-Upgrade
Select Recompile Invalid Objects During Post-Upgrade if you want DBUA to recompile all invalid PL/SQL modules after the upgrade is complete. Specify the parallelism for the recompilation of invalid objects during post upgrade. DBUA provides a recommended degree of Recompilation Parallelism, which it sets to one less than the number of CPUs you have available. Taking advantage of parallism can significantly reduce the upgrade time. 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 Timezone Data
Select Upgrade Timezone Data for DBUA to update 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.
Gather Statistics Before Upgrade
Select Gather Statistics Before Upgrade to reduce the overall time for the upgrade process by gathering statistics before upgrading.
Set User Tablespace to Read Only During the Upgrade
Disable Set User Tablespace to Read Only During the Upgrade if you are upgrading a database in which you must transport tablespaces. Transportable tablespaces must have writable file headers.
Diagnostic Destination
The Diagnostic Destination field specifies the location for output that DBUA creates for diagnostics. You can accept the default, enter a full path into the field, or click Browse to navigate to a location.
Audit File Destination
The Audit File Destination field specifies the location for DBUA to save audit files. Accept the default, enter a full path into the field, or click Browse to navigate to a location.
Optionally, click the Custom Scripts tab to specify custom SQL scripts that you would like to run before and after the upgrade
The Upgrade Options page appears with the Custom Scripts tab selected.
You may also click Next without using the Custom Scripts option.
The Custom Scripts tab in the Upgrade Options page allows you to optionally run custom SQL scripts. If you want to run a script before the upgrade, click Browse for the Before Upgrade field to browse to the location of the custom SQL script you would like to run before the upgrade. If you want to run a script after the upgrade, click Browse for the After Upgrade field to browse to the location of the custom SQL script you would like to run after the upgrade.
You can specify either one or both, or leave the fields blank to skip this tab.
Click Next.
The Management Options page appears.
In the Management Options page, select an option:
Configure Enterprise Manager (EM) Database Express
You can enter the EM Express port number, for example, 5500.
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 managed targets.
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 Password
Click Next.
If you are upgrading a single-instance database (the assumption for readers of this manual) or Oracle Express Edition (XE), the Move Database Files page appears.
On the Move Database Files page, select an option:
Move Database Files as Part of Upgrade
Move Fast Recovery Area as Part of Upgrade
Note:
The fast recovery area is an Oracle managed disk location used for storing backup and recovery related files. Oracle strongly recommends configuring a fast recovery area, because it significantly enhances speed, reliability, and manageability of the database recovery process. The location of the fast recovery area is also used by Oracle Enterprise Manager if you enable local management on the Management Options screen.
If you are upgrading an Oracle Express Edition database, the Move Database Files page also includes the Rename Database section with the Global Database Name and SID fields. You must provide values for these fields. The rest of the Move Database Files page options are the same as for Oracle Database.
If you choose Move Database Files as Part of Upgrade, then you must also configure Storage Type for the database files.
In the Storage Type list, select File System or Oracle ASM.
If you select File System, your database files are moved to the host file system.
If you select Oracle Automatic Storage Management (Oracle ASM), your database files are moved to Oracle ASM storage, which must currently exist on your system. If you do not have an Oracle ASM instance, then you can create one using Automatic Storage Management Configuration Assistant (ASMCA) from the Oracle Grid Infrastructure home and then restart DBUA.
See Also:
Oracle Database Upgrade Guide for more information about moving database files
Oracle Grid Infrastructure Installation Guide for information about installing and configuring Oracle ASM
Oracle Automatic Storage Management Administrator's Guide for information about managing Oracle ASM instances with ASMCA
You can choose either Use Common Location for All Database Files or Use a Mapping File to Specify Location of Database Files. Specify the location in the file location field or browse to the location.
If you choose Oracle Managed Files, then click Multiplex Redo Logs and Control Files. The Multiplex Redo Logs and Control Files dialog box appears with location fields. Enter locations for online redo logs and control files to be written. Use multiple locations spread across different disks to provide greater fault tolerance.
If you choose Move Fast Recovery Area as Part of Upgrade, then you must also configure the storage type and location for the fast recovery area and specify the size to be allocated as described in this step.
The Move Database Files and Move Fast Recovery Area options are independent of each other. For example, you can choose to move database files to Oracle ASM and leave the fast recovery area on the file system.
When you choose to move the fast recovery area, DBUA does not physically move existing archived redo logs to a new location. Instead, DBUA sets the DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE initialization parameters to the new location and new size when the database is started from the new Oracle home.
If an Oracle Express Edition database is being upgraded to Oracle Enterprise Edition, then you must configure a fast recovery area. If a fast recovery area is currently configured, then the current settings are retained but the page displays to enable you to override these values.
Fast Recovery Area Storage Type
In the Storage Type list, select File System or ASM.
If you select File System, your fast recovery area will be on the host file system.
If you select Oracle Automatic Storage Management (Oracle ASM), your fast recovery area will be on Oracle ASM storage, which must currently exist on your system. If you do not have an Oracle ASM instance, then you can create one using Automatic Storage Management Configuration Assistant (ASMCA) from the Oracle Grid Infrastructure home and then restart DBUA.
Fast Recovery Area Location
Browse to the location on the host file system, or on Oracle ASM storage.
Fast Recovery Area Size
Specify the size to allocate for the fast recovery area. The default is 1024 MB.
Click Next. The Network Configuration page appears with the Listener Selection tab showing.
The Listener Selection tab on the Network Configuration page shows a table with: Name, Port, Oracle Home, Status, and Migrate columns. To the left of the listener name is a box for selecting the listener.
Select one or more listeners from the source Oracle home to be migrated to the new upgraded Oracle home.
DBUA adds the selected listener to the listener.ora. of the target Oracle home and starts it.
DBUA removes the entry of the upgraded database from the old (source) listener.ora file.
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 may be affected during listener migration.
Select Create a New Listener to create a new listener. Provide the name and port number.
Click Next.
DBUA displays the Recovery Options page. DBUA performs the listener migration during the pre-upgrade steps.
In the Recovery Options Configuration page, select the recovery method to use if the upgrade process encounters a problem.
The following recovery options and configurations are available:
Use RMAN Backup
If you select Create RMAN Backup before Upgrade, then enter the full path for a location for the backup in the Backup Location field.
If you select Use Latest Available RMAN Backup but do not choose to create an RMAN backup before upgrading, then DBUA displays the time stamp for the latest RMAN backup that exists. You can click Restore Script next to the time stamp to select an existing script to run for restoring this backup.
Use Flashback and Guaranteed Restore Point
Select Create a New Guaranteed Restore Point to have DBUA create a restore point before DBUA enters the upgrade process.
If you previously enabled Flashback Database and configured a fast recovery area with a flashback retention target, then you can select Use Available Guaranteed Restore Point and pick the named SCN from the drop-down list. Your current settings for the restore point are retained. DBUA displays a page to permit you to override these values if needed.
I have my own backup and restore strategy
Click this option only if you used your own backup procedure to back up the database. In this case, Restore restores only the original database settings. To restore the database itself, you must restore the backup you created with your own backup utilities.
Note:
The database you are upgrading must be release 11.1.0.7 or later in order to take advantage of Flashback and Guaranteed Restore Point, and this must be enabled in the source database.
See Also:
Oracle Database Backup and Recovery User's Guide for more information on using Flashback Database and guaranteed restore points
Click Next.
The Summary page appears.
The Summary page shows the following information about the upgrade before it starts:
Source Database
Target Database
Pluggable Databases
Pre-Upgrade Checks
Initialization Parameter changes
Timezone Upgrade
See Also:
Oracle Database Upgrade Guide for information about setting the COMPATIBLE initialization parameter after the upgrade
Check all of the details. Then click Back or Finish as follows:
Click Back if anything is incorrect until you reach the page where you can correct it.
Click Finish if everything is correct.
The Progress page appears and DBUA begins the upgrade.
The Progress page shows a table with the steps being performed, the time duration, and the 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, the Progress page marks the status Finished. You can click Activity Log, Alert Log, and Upgrade Results to view more information.
After the upgrade has completed, the Upgrade Results page appears.
The Upgrade Results page displays a description of the original database and the upgraded database and shows the changes made to the initialization parameters. The page also shows the directory where various log files are stored after the upgrade, and PDBs (if you upgraded a CDB with PDBs). Scroll down to view more details about pre-upgrade checks.
Optionally, you can examine the log files to obtain more details about the upgrade process. The DBUA log files are located under the /oracle_base/cfgtoollogs/dbua/logs directory.
Note:
An HTML version of the Upgrade Results is also saved in the log files directory. You can click the links in this HTML page to view the log pages in your web browser.
If you are satisfied with the upgrade results, then click Close to quit DBUA and use your newly upgraded database.
See Also:
Oracle Database Upgrade Guide for information about additional tasks that should be completed after upgrading your database
Note:
To prevent unauthorized use of the database, Oracle recommends that you change all user passwords immediately after you upgrade your database.
If the default security settings for Oracle Database 12c are in place, then passwords must be at least eight characters, and passwords such as welcome and oracle are not allowed. See Oracle Database Security Guide for information about configuring authentication.