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

1
  Database Name:  ORCL
2
 Container Name:  orcl
3
   Container ID:  0
4
        Version:  12.1.0.2.0
5
 DB Patch Level:  No Patch Bundle applied
6
     Compatible:  12.1.0.2.0
7
      Blocksize:  8192
8
       Platform:  Linux x86 64-bit
9
  Timezone File:  18

Database log mode: ARCHIVELOG 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 Real Application Clusters [to be upgraded] OPTION OFF 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 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 Oracle OLAP API [to be upgraded] VALID

============== BEFORE UPGRADE#

REQUIRED ACTIONS#

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

   The database contains 5 objects in the recycle bin.

   The recycle bin must be completely empty before database upgrade.

2. Contact Oracle Support for instructions on how to resolve this error. ERROR: ORA-29548 ORA-29548: Java system class reported: release of classes.bin in the database does not match that of the oracle executable

   There is a problem with the JAVAVM component and database upgrade cannot be performed until it is corrected.

   JAVAVM component must be functioning properly before database upgrade.

RECOMMENDED ACTIONS#

3. Upgrade Oracle Application Express (APEX) manually before the database upgrade.

   The database contains APEX version 192.168.1.10.08. Upgrade APEX to at least version 18.2.0.00.12.

   Starting with Oracle Database Release 18, APEX is not upgraded automatically as part of the database upgrade. Refer to My Oracle Support Note 1088970.1 for information about APEX installation and upgrades.

4. (AUTOFIXUP) Gather stale data dictionary statistics prior to database upgrade in off-peak time using:

   EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;

   Dictionary statistics do not exist or are stale (not up-to-date).

   Dictionary statistics help the Oracle optimizer find efficient SQL execution plans and are essential for proper upgrade timing. Oracle recommends gathering dictionary statistics in the last 24 hours before database upgrade.

   For information on managing optimizer statistics, refer to the 12.1.0.2 Oracle Database SQL Tuning Guide.

INFORMATION ONLY#

5. Here are ALL the components in this database registry:

   Component Current Current Original Previous Component CID Version Status Version Version Schema

   ---

   APEX 192.168.1.10.08 VALID APEX_040200 APS 12.1.0.2.0 VALID SYS CATALOG 12.1.0.2.0 VALID SYS CATJAVA 12.1.0.2.0 VALID SYS CATPROC 12.1.0.2.0 VALID SYS CONTEXT 12.1.0.2.0 VALID CTXSYS DV 12.1.0.2.0 VALID DVSYS JAVAVM 12.1.0.2.0 VALID SYS OLS 12.1.0.2.0 VALID LBACSYS ORDIM 12.1.0.2.0 VALID 12.1.0.2.0 12.1.0.2.0 ORDSYS OWM 12.1.0.2.0 VALID WMSYS RAC 12.1.0.2.0 OPTION OFF SYS SDO 12.1.0.2.0 VALID MDSYS XDB 12.1.0.2.0 VALID XDB XML 12.1.0.2.0 VALID SYS XOQ 12.1.0.2.0 VALID SYS

   Review the information before upgrading.

6. To help you keep track of your tablespace allocations, the following AUTOEXTEND tablespaces are expected to successfully EXTEND during the upgrade process.

   1
                                          Min Size
   

   Tablespace Size For Upgrade

   ---

   SYSAUX 820 MB 887 MB SYSTEM 800 MB 1142 MB

   Minimum tablespace sizes for upgrade are estimates.

7. Ensure there is additional disk space in LOG_ARCHIVE_DEST_1 for at least 4618 MB of archived logs. Check alert log during the upgrade that there is no write error to the destination due to lack of disk space.

   Archiving cannot proceed if the archive log destination is full during upgrade.

   Archive Log Destination: Parameter : LOG_ARCHIVE_DEST_1 Destination : +DATADB

   The database has archiving enabled. The upgrade process will need free disk space in the archive log destination(s) to generate archived logs to.

8. Check the Oracle Backup and Recovery User’s Guide for information on how to manage an RMAN recovery catalog schema.

   If you are using a version of the recovery catalog schema that is older than that required by the RMAN client version, then you must upgrade the catalog schema.

   It is good practice to have the catalog schema the same or higher version than the RMAN client version you are using.

9. Here is a count of invalid objects by Oracle-maintained users:

   Oracle-Maintained User Name Number of INVALID Objects

   ---

   None None

   Review the information before upgrading.

10. Here is a count of invalid objects by Application users:

    Application User Name Number of INVALID Objects

    ---

    None None

    Review the information before upgrading.

ORACLE GENERATED FIXUP SCRIPT#

All of the issues in database ORCL which are identified above as BEFORE UPGRADE “(AUTOFIXUP)” can be resolved by executing the following

1
    SQL>@/home/oracle/enmo/log/preupgrade_fixups.sql

============= AFTER UPGRADE#

REQUIRED ACTIONS#

None

RECOMMENDED ACTIONS#

11. Upgrade the database time zone file using the DBMS_DST package.

    The database is using time zone file version 18 and the target 19 release ships with time zone file version 32.

    Oracle recommends upgrading to the desired (latest) version of the time zone file. For more information, refer to “Upgrading the Time Zone File and Timestamp with Time Zone Data” in the 19 Oracle Database Globalization Support Guide.

12. Recreate directory objects to remove any symbolic links from directory paths. To identify paths that contain symbolic links before upgrading, use OS commands like UNIX file or WINDOWS dir. After upgrading, run $ORACLE_HOME/rdbms/admin/utldirsymlink.sql to identify directory objects with symbolic links in the path.

    Found 1 user directory objects to be checked: ORACLECLRDIR.

    Starting in Release 18c, symbolic links are not allowed in directory object paths used with BFILE data types, the UTL_FILE package, or external tables.

13. (AUTOFIXUP) Gather dictionary statistics after the upgrade using the command:

    EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;

    Oracle recommends gathering dictionary statistics after upgrade.

    Dictionary statistics provide essential information to the Oracle optimizer to help it find efficient SQL execution plans. After a database upgrade, statistics need to be re-gathered as there can now be tables that have significantly changed during the upgrade or new tables that do not have statistics gathered yet.

14. Gather statistics on fixed objects after the upgrade and when there is a representative workload on the system using the command:

    EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;

    This recommendation is given for all preupgrade runs.

    Fixed object statistics provide essential information to the Oracle optimizer to help it find efficient SQL execution plans. Those statistics are specific to the Oracle Database release that generates them, and can be stale upon database upgrade.

    For information on managing optimizer statistics, refer to the 12.1.0.2 Oracle Database SQL Tuning Guide.

ORACLE GENERATED FIXUP SCRIPT#

All of the issues in database ORCL which are identified above as AFTER UPGRADE “(AUTOFIXUP)” can be resolved by executing the following

1
    SQL>@/home/oracle/enmo/log/postupgrade_fixups.sql