Using the Pre-Upgrade Information Tool for Oracle Database

Review these topics to understand and to use the Pre-Upgrade information tool (preupgrade.jar).

About the Pre-Upgrade Information Tool
The Pre-Upgrade Information Tool is revised and enhanced in Oracle Database 12c release 2 (12.2). Run this tool on your earlier release Oracle Database to determine if it is ready for upgrading.
Setting Up Environment Variables for the Pre-Upgrade Information Tool
Before you run the Pre-Upgrade Information Tool, set up the user environment variables for the Oracle user that runs the tool, and open pluggable databases (PDBs) for analysis.
Pre-Upgrade Information Tool (preupgrade.jar) Command
Use Pre-Upgrade Information Tool (preupgrade.jar) commands to check your system before upgrades.
Output of the Pre-Upgrade Information Tool
The Pre-Upgrade Information Tool (preupgrade.jar) creates fixup scripts and log files in the output directory that you specify with the DIR command-line option.
Pre-Upgrade Information Tool Warnings and Recommendations for Oracle Database
Use this section to analyze any Pre-Upgrade Information Tool warnings before you upgrade to the new release of Oracle Database.
Pre-Upgrade Information Tool Output Example
In this example, you can see how the Pre-Upgrade Information Tool displays recommended fixes, but does not carry out fixes automatically.

About the Pre-Upgrade Information Tool

The Pre-Upgrade Information Tool is revised and enhanced in Oracle Database 12c release 2 (12.2). Run this tool on your earlier release Oracle Database to determine if it is ready for upgrading.

Oracle Database 12c release 2 introduces the preupgrade.jar Pre-Upgrade Information Tool. You can run the tool from the operating system command line. In previous Oracle Database releases, the Pre-Upgrade Information Tool was run within SQL*Plus as a SQL file.

Note:

Oracle requires that you run the Pre-Upgrade Information Tool before you upgrade to Oracle Database 12c release 2.

What the Pre-Upgrade Information Tool Does

The Pre-Upgrade Information Tool (preupgrade.jar) creates the following files:

A log file (preupgrade.log).

The log file contains the output of the Pre-Upgrade Information Tool.
The pre-upgrade fixups:
- Non-CDB: preupgrade_fixups.sql
- CDB: preupgrade_fixups.sql (a consolidated script for all PDBs), and individual scripts for each PDB, named postupgrade_fixups_pdbname.sql, where pdbname is the name of the PDB.
You must run these scripts before you run the upgrade. The scripts resolve many of the issues identified by the preupgrade tool, either by using catcon.pl, or by using SQL*Plus commands.
The post-upgrade fixups:
- Non-CDB: postupgrade_fixups.sql
- CDB: postupgrade_fixups.sql (a consolidated script for all PDBs), and individual scripts for each PDB, named preupgrade_fixups_pdbname.sql, where pdbname is the name of the PDB.
You must run these scripts after you complete the upgrade. The scripts resolve many of the issues identified by the preupgrade tool, either by using catcon.pl, or by using SQL*Plus commands.

Each identified issue includes a description of the problem, and a task that you can carry out to resolve the problem. The preupgrade tool itself does not make changes to your database to correct errors. However, it does generate scripts that you can use to correct identified errors.
The tool generates a preupgrade SQL script, preupgrade_fixups.sql, which you can run before the upgrade to repair issues that can be fixed before the upgrade.

The preupgrade_fixups.sql script fixes only those issues that an automated script can fix safely.

Preupgrade issues that the automated script cannot fix safely typically require DBA knowledge of user applications. You can address those issues manually.
The tool generates a postupgrade SQL script, postupgrade_fixups.sql, which you can run after the upgrade to fix issues that can be fixed after the upgrade.

Postupgrade issues that the automatic script cannot fix safely typically require DBA knowledge of user applications. You can address those issues manually.

Overview of Pre-Upgrade Information Tool Output Files

The Pre-Upgrade Information Tool (preupgrade.jar) creates the following files:

The log file preupgrade.log.

The log file contains the output of the Pre-Upgrade Information Tool.
The preupgrade_fixups_pdbname.sql (for PDBs, where pdbname is the name of the PDB) or preupgrade_fixups.sql script (Non-CDB databases).

Before you run the upgrade, you can run the preupgrade fixups script manually in SQL*Plus to resolve many of the issues identified by the preupgrade tool.
The postupgrade_fixups_pdbname.sql (for PDBs, where pdbname is the name of the PDB) or postupgrade_fixups.sql script (Non-CDB databases).

You can run this script to fix issues after the database upgrade is completed.

Related Topics

Running Postupgrade Fixup Scripts

Setting Up Environment Variables for the Pre-Upgrade Information Tool

Before you run the Pre-Upgrade Information Tool, set up the user environment variables for the Oracle user that runs the tool, and open pluggable databases (PDBs) for analysis.

You must set up the user environment variables for the Pre-Upgrade information tool. This example shows how to use shell commands to set up user environment variables to point to an earlier release Oracle home. For multitenant architecture upgrades, you must also open up all the PDBs that you want the tool to analyze.

In this example, the operating system is Linux or UNIX, the system identifier is sales01, and the earlier release Oracle home path is /u01/app/oracle/product/12.1.0/dbhome_1

Set up the user environment variables to point to the earlier release Oracle home that you want to upgrade.

For example:

$ export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1
$ export ORACLE_BASE=/u01/app/oracle
$ export ORACLE_SID=sales01
$ export PATH=.:$ORACLE_HOME/bin:$PATH

(Multitenant architecture upgrades): If you are running the Pre-Upgrade Information Tool in a CDB, then use the command alter pluggable database all open to open the PDBs so that the tool can analyze them.
For example: Log in to the database and enter the following command to open all PDBs:
```
$ sqlplus \ as SYSDBA
.
.
.
SQL> alter pluggable database all open;
```

Pre-Upgrade Information Tool (preupgrade.jar) Command

Use Pre-Upgrade Information Tool (preupgrade.jar) commands to check your system before upgrades.

Prerequisites

The Pre-Upgrade Information Tool is in the new release Oracle home, in the file path ORACLE_HOME/rdbms/admin/preupgrade.jar. Oracle has configured it with the system checks necessary for Oracle Database 12c release 2 (12.2). However, the checks that the tool performs are carried out on the earlier release Oracle Database home. Set up the Oracle user environment variables so that they point to the earlier release Oracle home.

Run the Pre-Upgrade Information Tool by using the Java version in your earlier release Oracle home. For multitenant architecture (CDB and PDB) upgrades, open up all the PDBs that you want the tool to analyze before you run the tool.

Set the environment variables for your user account to point to the earlier release ORACLE_HOME, ORACLE_BASE, and ORACLE_SID.

File Path

The preupgrade.jar file is located in the new Oracle home:

New_release_Oracle_home/rdbms/admin/preupgrade.jar

You can also copy the preupgrade.jar binaries to a path of your choosing. For example:

/tmp/preupgrade.jar

Syntax

$Earlier_release_Oracle_home/jdk/bin/java -jar $New_release_Oracle_home
/rdbms/admin/preupgrade.jar [FILE|TERMINAL] [TEXT|XML] [DIR output_dir]

Options

Command Option	Description
`FILE\|TERMINAL`	Script output location. Use FILE to direct script output to a file. Use TERMINAL to direct output to the terminal. If you do not specify a value, then the default is FILE. If you specify TERMINAL, then screen output is directed to the display, and scripts and logs are placed in the output directory path.
`TEXT\|XML`	Output type. Use TEXT to specify text output. Use XML to specify XML output. If you do not specify an output type, then the default is text.
`DIR output_dir`	Directs the output to a specific directory. If you do not specify an output directory with the `DIR` option, then the output is directed to one of the following default locations: If you do not specify an output directory with `DIR`, but you define an `ORACLE_BASE` environment variable, then the generated scripts and log files are created. If you do not specify an output directory, and `ORACLE_BASE` is not defined, then the generated scripts and log files are created in the following path: `ORACLE_HOME/cfgtoollogs/dbunique_name/preupgrade`
`-c "pdb1 pdb2 pdb3"` (Windows) `-c 'pdb1 pdb2 pdb3'` (Linux and UNIX)	Specifies a list of containers inside a CDB that you want to include for processing (a "White list"). Provide a space-delimited list of PDBs that you want processed. To specify the list, use single quotes on Linux and UNIX operating systems, and use double quotes on Windows systems. If you do not specify either `-c` or `-C`, then all PDBs in a CDB are processed.
`-C "pdb1 pdb2 pdb3"` (Windows) `-C 'pdb1 pdb2 pdb3'` (Linux and UNIX)	Specifies a list of containers inside a CDB that you want to exclude from processing (a "Black list"). Provide a space-delimited list of PDBs that you want to exclude from processing. To specify the list, use single quotes on Linux and UNIX operating systems, and use double quotes on Windows systems. If you do not specify either `-c` or `-C`, then all PDBs in a CDB are processed.
`-loadonly`	Loads the Pre-Upgrade Information Tool into the database, without carrying out any other action. You can use this parameter to prepare earlier releases for upgrades. For example, if you plug in an earlier release PDB into a current release CDB, the PDB, you can use this option to load the tool where the PDB does not have all packages and the directory loaded, or where the directory is not present in the new Oracle home.
`-p password`	Provides the password for the user. If you do not use operating system authentication to connect to the database, then use the `-p` option to specify a password on the command line. If a username is specified on the command line with `-u`, but no password specified with `-p`, then the tool prompts you for a password.
`-u username`	Provides the user name of the user that you want to use to connect as SYSDBA to the database that you want to check. Use this option only if you do not use operating system authentication to connect to the database For example, You log in as a user that is not a member of the OSDBA group for the database that you want to check. In that case, the user account does not have operating system authentication privileges for the SYSDBA system privilege. Use the `-u` and `-p` option to provide data dictionary authentication to log in as a user with SYSDBA system privileges.
`-oh oracle_home`	Specifies an Oracle home that you want to check. Provide the path of the Oracle home that you want to check. If you do not specify an Oracle home path to check, then the Pre-Upgrade Information Tool defaults to the path specified by the user environment variable for the Oracle home. That variable is $ORACLE_HOME on Linux and UNIX systems, and %ORACLE_HOME% on Windows systems.
`-sid system_identifier`	Specifies an Oracle system identifier that you want to check. Provide the ORACLE_SID of the database that you want to check.
`-help`	Displays the command-line syntax help text.

Example 2-4 Non-CDB In the Source Oracle Home Example

Set your user environment variables to point to the earlier release Oracle home.

$ export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1
$ export ORACLE_BASE=/u01/app/oracle
$ export ORACLE_SID=sales01
$ export PATH=.:$ORACLE_HOME/bin:$PATH

Run the new release Oracle Database Pre-Upgrade Information Tool on the earlier release Oracle Database server (12.2), using the environment settings you have set to the earlier release Oracle home.
```
$ORACLE_HOME/jdk/bin/java -jar /u01/app/oracle/product/12.2.0/rdbms/admin/preupgrade.jar TERMINAL TEXT
```

Example 2-5 CDB in a Source Oracle Home

Open all the pluggable databases
```
SQL> alter pluggable database all open;
```

Set your user environment variables to point to the earlier release Oracle home.

$ export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1
$ export ORACLE_BASE=/u01/app/oracle
$ export ORACLE_SID=sales01
$ export PATH=.:$ORACLE_HOME/bin:$PATH

Run the Pre-Upgrade Information Tool with an inclusion list, using the -c option. In this example, the inclusion list is PDB1 and PDB2, and the command is run on a Linux or UNIX system. The output of the command is displayed to the terminal, and the output is displayed as text.
```
$ORACLE_HOME/jdk/bin/java -jar /u01/app/oracle/product/12.2.0/dbhome_1/rdbms/admin/preupgrade.jar TERMINAL TEXT -c 'pdb1 pdb2'
```

Output of the Pre-Upgrade Information Tool

The Pre-Upgrade Information Tool (preupgrade.jar) creates fixup scripts and log files in the output directory that you specify with the DIR command-line option.

When you run the Pre-Upgrade Information Tool, it generates the following files inside the directory that you specify as the output directory.

Log File (preupgrade.log)

The file preupgrade.log is the report that the Pre-Upgrade Information Tool generates whenever you run the command with the FILE option. The log file contains all the tool recommendations and requirements for upgrade. The log file is located in the following path, where timestamp is the date and time when the command is run: $ORACLE_BASE/cfgtoollogs/dbua/upgradetimestamp/SID/. If you run the command with the TERMINAL option, then the content of this file is output to the display. Refer to the section "Pre-Upgrade Information Tool Output Example" for an example of a log file.

XML DBUA File (upgrade.xml)

If you specify XML file output on the Pre-Upgrade Information Tool command line, then it generates the upgrade.xml file instead of preupgrade.log.

Preupgrade Fixup File (preupgrade_fixups.sql) and Postupgrade Fixup File (postupgrade_fixups.sql)

The Pre-Upgrade Information Tool identifies issues that can block or hinder an upgrade.

Some issues require a DBA to resolve, because it is not possible for the automated script to understand the specific goals of your application. However, other issues do not present any difficulty in resolving. In these cases, the Pre-Upgrade Information Tool automatically generates scripts that contain the SQL statements necessary to resolve the issues. Using these scripts can perform, track, and simplify the work that DBAs must do to resolve potential upgrade issues. The SQL statements that resolve issues before upgrade are placed in the preupgrade_fixups.sql script. The SQL statements that resolve issues after upgrade are placed in the postupgrade_fixups.sql script. When you run the Pre-Upgrade Information tool on a multitenant architecture Oracle Database, you can run the consolidated scripts preupgrade_fixups.sql script and postupgrade_fixups.sql across all the containers. Run the consolidated scripts using catcon.pl.

Both of these fixup files are generated in the output directory that you specify with the Pre-Upgrade Information Tool DIR command-line option.

The script carries out the following steps to resolve pre-upgrade or post-upgrade issues:

For each issue that the Pre-Upgrade Information Tool identifies, it reruns the individual Pre-Upgrade Information Tool check again, to determine if the issue is still present.
If the issue is present, then the tool does one of the following, depending on whether there is a fixup routine for the issue:
- If there is an Oracle-supplied fixup routine for that issue, then the script executes that fixup routine. It then reruns the Pre-Upgrade Information Tool check again, to confirm that the issue is resolved. If the issue is resolved, then the script displays a message that the issue is resolved.
- If there is no Oracle-supplied fixup routine, then the script displays a message that the issue is still present.

Review the issues that the script indicates are still present after it completes its checks. Resolve all the issues marked Required before upgrading. You can choose to resolve recommended fixes and informational fixes. You can rerun the preupgrade_fixups.sql and postupgrade_fixups.sql scripts as many times as you want to. You can use the scripts as a progress report to track remaining issues as part of your issue resolution plan.

After you resolve issues identified by the Preupgrade fixup and Postupgrade fixup scripts, Oracle recommends that you rerun the Pre-Upgrade Information Tool (preupgrade.jar) one more time before upgrade. Running the tool one more time helps to confirm that you have resolved all issues that you intend to address.

If you are checking a multitenant environment system (CDBs and PDBs), then the preupgrade_fixups.sql and postupgrade_fixups.sql scripts contain a rollup of the fixup code for all the individual PDBs. They are coded so that only the code for the current PDB runs. You can run the same script in each PDB. The script fixes only the issues in that PDB. As a result, it is easy to use the preupgrade_fixups.sql and postupgrade_fixups.sql with catcon.pl to run fixups across an entire CDB.

Related Topics

Pre-Upgrade Information Tool Warnings and Recommendations for Oracle Database

Use this section to analyze any Pre-Upgrade Information Tool warnings before you upgrade to the new release of Oracle Database.

Refer to My Oracle Support note 472937.1 for information about installed database components and schemas. Refer to My Oracle Support note 753041.1 for information about diagnosing components with NON VALID status.

Updating Access Control Lists and Network Utility Packages
Use this procedure to update access control lists (ACLs) and Network Utility Packages.
Evaluate Dependencies and Add ACLs for Network Utility Packages
You can receive a warning about network utility package dependencies. Use this procedure to evaluate the dependencies, and provide access by adding the appropriate access control lists (ACLs).
About Database Links with Passwords from Earlier Oracle Database Releases
This information is important only for downgrading to your original database release after performing the upgrade.
About Oracle Database Warnings for TIMESTAMP WITH TIME ZONE Data Type
Oracle Database upgrades include updated time zone data types, which may affect existing TIMESTAMP WITH TIME ZONE data types.

Related Topics

Updating Access Control Lists and Network Utility Packages

Use this procedure to update access control lists (ACLs) and Network Utility Packages.

Starting with Oracle Database 12c, the access control of the UTL packages is implemented using Oracle Database Real Application Security. UTL packages include UTL_TCP, UTL_SMTP, UTL_MAIL, UTL_HTTP, and UTL_INADDR. The access control does not require Oracle XML DB.

Ensure that the logged-in user has the connect privilege for the host and port specified by DBMS_LDAP.init. There is new behavior for the DBMS_LDAP PL/SQL package and the HttpUriType type. Because of this new behavior, you must create or update access control lists (ACLs) after you upgrade to the new Oracle Database release.

For example, if your application depends on the DBMS_LDAP package, then the error "ORA-24247: network access denied by access control list (ACL)" can occur. To avoid this error, the logged-in user must have the connect privilege for the host and port specified by DBMS_LDAP.init.
If you have any of the following packages installed, then you can be required to reinstall these packages after upgrade:
- UTL_TCP
- UTL_SMTP
- UTL_MAIL
- UTL_HTTP
- UTL_INADDR
Ensure that you have the latest version of these packages for the new Oracle Database release.

Evaluate Dependencies and Add ACLs for Network Utility Packages

You can receive a warning about network utility package dependencies. Use this procedure to evaluate the dependencies, and provide access by adding the appropriate access control lists (ACLs).

Run the Pre-Upgrade Information Tool.

Check the output from the Pre-Upgrade Information Tool (preupgrade.jar) for warning messages, such as the following example:

WARNING: --> Database contains schemas with objects dependent on network packages.
.... Refer to the Database Upgrade Guide for instructions to configure Network ACLs.
.... USER WKSYS has dependent objects.
.... USER SYSMAN has dependent objects.
.... USER FLOWS_010600 has dependent objects.
.

Query the view DBA_DEPENDENCIES to obtain more information about the dependencies. For example:

SELECT * FROM DBA_DEPENDENCIES
WHERE referenced_name IN ('UTL_TCP','UTL_SMTP','UTL_MAIL','UTL_HTTP','UTL_INADDR','DBMS_LDAP')
  AND owner NOT IN ('SYS','PUBLIC','ORDPLUGINS');

To ensure that the new access controls are part of your upgrade testing, prepare a post-upgrade script to make the scripts available in your database environment.

Use the package DBMS_NETWORK_ACL_ADMIN to update your database access control lists (ACLs). You use this package to create, assign, and add privileges to the new access controls so that the updated access control packages can work as they did in prior releases. Refer to the example script provided in Oracle Database Real Application Security Administrator’s and Developer’s Guide to see how to use DBMS_NETWORK_ACL_ADMIN to update your access control list.
After the upgrade, grant specific required privileges. Access is based on the usage in the original database.

Related Topics

Oracle Database Real Application Security Administrator's and Developer's Guide

About Database Links with Passwords from Earlier Oracle Database Releases

This information is important only for downgrading to your original database release after performing the upgrade.

During the upgrade to the new Oracle Database release, any passwords in database links are encrypted.

To downgrade to the release from which you upgraded, you must drop all of the database links with encrypted passwords before the downgrade. Consequently, the database links are nonexistent in the downgraded database.
If you must be able to downgrade to your original release, then save the information about affected database links from the SYS.LINK$ table, so that you can recreate the database links after the downgrade.
For information about earlier releases, refer to the original documentation for the Oracle Database release from which you upgraded. Also refer to your platform-specific Oracle Database Installation Guide for the earlier release.

About Oracle Database Warnings for TIMESTAMP WITH TIME ZONE Data Type

Oracle Database upgrades include updated time zone data types, which may affect existing TIMESTAMP WITH TIME ZONE data types.

The time zone files supplied with Oracle Database 12c are updated to reflect changes in transition rules for some time zone regions. The changes may affect existing TIMESTAMP WITH TIME ZONE data types.

Oracle recommends that you ensure that you have the latest time zone files before you upgrade the database. If the time zone file version of the database you are upgrading is not the most recent version of the time zone file available for the new release of Oracle Database, then the Pre-Upgrade Information Tool displays a warning and describes how to proceed. The following table describes the warnings and summarizes how to resolve a mismatch in time zone file versions.

Caution:

The TIMESTAMP WITH TIME ZONE data stored in the database can become corrupted during the upgrade if there is a time zone file version mismatch.

Table 2-3 Choices for Fixing the Time Zone File Version

Time Zone Version On the Database Being Upgraded When to Fix the Time Zone Files

Time Zone Version On the Database Being Upgraded	When to Fix the Time Zone Files
Earlier than the most current version included in the new database release and the Pre-Upgrade Information Tool displays "Database is using a time zone file older than version n."	After completing the database upgrade. Use the `DBMS_DST` PL/SQL package and follow the instructions in "Steps to Upgrade Time Zone File and Timestamp with Time Zone Data. Refer to the following document: Oracle Database Globalization Support Guide.
Later than the version included in the new database release and the Pre-Upgrade Information Tool displays "Database is using a time zone file greater than version n."	Before beginning the database upgrade. You must patch the Oracle home by using an `RDBMS DST` patch with the appropriate patch for the time zone file version in use. Apply the patch for each database that you want to upgrade. Otherwise, the upgrade script terminates without upgrading the database. The `RDBMS DST` patches are available from My Oracle Support note ID 412160.1.

Earlier than the most current version included in the new database release and the Pre-Upgrade Information Tool displays "Database is using a time zone file older than version n."

After completing the database upgrade.

Use the DBMS_DST PL/SQL package and follow the instructions in "Steps to Upgrade Time Zone File and Timestamp with Time Zone Data. Refer to the following document:

Oracle Database Globalization Support Guide.

Later than the version included in the new database release and the Pre-Upgrade Information Tool displays "Database is using a time zone file greater than version n."

Before beginning the database upgrade.

You must patch the Oracle home by using an RDBMS DST patch with the appropriate patch for the time zone file version in use. Apply the patch for each database that you want to upgrade. Otherwise, the upgrade script terminates without upgrading the database. The RDBMS DST patches are available from My Oracle Support note ID 412160.1.

Related Topics

Pre-Upgrade Information Tool Output Example

In this example, you can see how the Pre-Upgrade Information Tool displays recommended fixes, but does not carry out fixes automatically.

You have control over how and when the fixup scripts are run.

The following example shows the output that is generated and written to preupgrade.log by running the Oracle Database 12c Pre-Upgrade Information Tool on a release 11.2.0.3 database:

Report generated by Oracle Database Pre-Upgrade Information Tool Version
12.2.0.1.0

Upgrade-To version: 12.2.0.1.0

=======================================
Status of the database prior to upgrade
=======================================

      Database Name:  AIME1
     Container Name:  Not Applicable in Pre-12.1 database
       Container ID:  Not Applicable in Pre-12.1 database
            Version:  11.2.0.3.0
         Compatible:  11.2.0
          Blocksize:  8192
           Platform:  Linux x86 64-bit
      Timezone File:  14
  Database log mode:  NOARCHIVELOG
           Readonly:  FALSE
            Edition:  EE

  Oracle Component                       Upgrade Action    Current Status
  ----------------                       --------------    --------------
  Oracle Server                          [to be upgraded]  VALID
  JServer JAVA Virtual Machine           [to be upgraded]  VALID
  Oracle XDK for Java                    [to be upgraded]  VALID
  Oracle Workspace Manager               [to be upgraded]  VALID
  OLAP Analytic Workspace                [to be upgraded]  VALID
  Oracle Label Security                  [to be upgraded]  VALID
  Oracle Database Vault                  [to be upgraded]  VALID
  Oracle Enterprise Manager Repository   [to be upgraded]  VALID
  Oracle Text                            [to be upgraded]  VALID
  Oracle XML Database                    [to be upgraded]  VALID
  Oracle Java Packages                   [to be upgraded]  VALID
  Oracle Multimedia                      [to be upgraded]  VALID
  Oracle Spatial                         [to be upgraded]  VALID
  Expression Filter                      [to be upgraded]  VALID
  Rule Manager                           [to be upgraded]  VALID
  Oracle Application Express             [to be upgraded]  VALID
  Oracle OLAP API                        [to be upgraded]  VALID


==============
BEFORE UPGRADE
==============

  Run <preupgradeLogDirPath>/preupgrade_fixups.sql to complete all
  of the BEFORE UPGRADE action items below marked with '(AUTOFIXUP)'.

  REQUIRED ACTIONS
  ================
   + Adjust TABLESPACE SIZES as needed.
                                                Auto      12.2.0.1.0
     Tablespace                        Size     Extend    Min Size    Action
     ----------                     ----------  --------  ----------  ------

     EXAMPLE                            314 MB  DISABLED      309 MB  None
     SYSAUX                             530 MB  ENABLED      1442 MB  None
     SYSTEM                             720 MB  ENABLED      1228 MB  None
     TEMP                                20 MB  ENABLED       150 MB  None
     UNDOTBS1                            75 MB  ENABLED       400 MB  None

     Note that 12.2.0.1.0 minimum sizes are estimates.
     If you plan to upgrade multiple pluggable databases concurrently,
     then you must ensure that the UNDO tablespace size is equal to at least
     the number of pluggable databases that you upgrade concurrently,
     multiplied by that minimum.  Failing to allocate sufficient space can
     cause the upgrade to fail.




   + Update NUMERIC INITIALIZATION PARAMETERS to meet estimated minimums.

     Parameter                         12.2.0.1.0 minimum
     ---------                         ------------------
     processes                                        300




   + You must rename or drop the USER or ROLE named AUDSYS from the database.


     The database contains a USER or ROLE named AUDSYS. That name was
     reserved to Oracle in release 12.1.0.1.0, and remains reserved in
     release 12.2.0.1.0.

     Oracle occasionally adds new internal USERs and ROLEs as the database
     evolves.  To avoid a name conflict in the upgraded version, a source
     database must not contain any USER or ROLE with a name that matches one
     reserved by Oracle in the target release.

   + You must rename or drop the USER or ROLE named AUDIT_ADMIN from the
     database.

     The database contains a USER or ROLE named AUDIT_ADMIN. That name was
     reserved to Oracle in release 12.1.0.1.0, and remains reserved in
     release 12.2.0.1.0.

     Oracle occasionally adds new internal USERs and ROLEs as the database
     evolves.  To avoid a name conflict in the upgraded version, a source
     database must not contain any USER or ROLE with a name that matches one
     reserved by Oracle in the target release.

   + Run rdbms/admin/olspreupgrade from the new Oracle Database 12.2.0.1.0
     home.

     olspreupgrade.sql has not been run on this database.  To view the number
     of records that olspreupgrade.sql moves, use the following command:

       SELECT count(*) from system.aud$

     As part of the upgrade to 12.2.0.1.0, records in the 11.2.0.3.0 audit
     table SYSTEM.AUD$ are moved to SYS.AUD$. This step can be manually
     performed before the upgrade to reduce downtime.  Refer to the
     12.2.0.1.0 Oracle Label Security Administrator's Guide, or to Oracle
     Database Upgrade Guide for further details.

   + (AUTOFIXUP) Empty the RECYCLEBIN immediately before database upgrade.

     The database contains 3 objects in the recycle bin.

     The recycle bin must be completely empty before database upgrade.

  RECOMMENDED ACTIONS
  ===================
   + Remove the EM repository.

     - Copy the rdbms/admin/emremove.sql script from the target 12.2.0.1.0
     ORACLE_HOME into the source 11.2.0.3.0 ORACLE_HOME.

     - Stop EM Database Control:

       $> emctl stop dbconsole

     - Connect to the database using the SYS account AS SYSDBA

       SET ECHO ON;
       SET SERVEROUTPUT ON;
       @emremove.sql

     Without the set echo and serveroutput commands, you will not be able to
     follow the progress of the script.

     The database has an Enterprise Manager Database Control repository.

     Starting with Oracle Database 12c, the local Enterprise Manager Database
     Control does not exist anymore. The repository will be removed from your
     database during the upgrade.  This step can be manually performed before
     the upgrade to reduce downtime.

   + Run 11.2.0.3.0 ORACLE_HOME/rdbms/admin/utlrp.sql to recompile invalid
     objects.  You can view the individual invalid objects with

       SET SERVEROUTPUT ON;
       EXECUTE DBMS_PREUP.INVALID_OBJECTS;

     2 objects are INVALID.

     There should be no INVALID objects in SYS/SYSTEM or user schemas before
     database upgrade.

   + Remove OLAP Catalog by running the SQL script
     $ORACLE_HOME/olap/admin/catnoamd.sql script.

     The OLAP Catalog component, AMD, exists in the database.

     Starting with Oracle Database 12c, the OLAP Catalog (OLAP AMD) is
     desupported and will be removed from the database during the database
     upgrade.  This step can be manually performed before the upgrade to
     reduce downtime.