Checklists for Oracle Database Upgrade

Use checklists to plan and carry out Oracle Database upgrades.

Oracle recommends that you use checklists as part of your upgrade planning and implementation process. Using checklists can help you to use available upgrade utilities, and can help you to ensure you carry out a successful upgrade.

Source Server Preparation Upgrade Checklist

Use this checklist to prepare your server with the earlier Oracle Database release before you start the upgrade.

Table 2-1 Source Server Preparation Upgrade Checklist

Task Description
Clean up the database
  • Empty the recycle bin

  • Check for INVALID objects in SYS and SYSTEM

  • Check for duplicate objects in SYS and SYSTEM

Check components
  • Check for INVALID components

  • Check for mandatory components

  • Remove obsolete components

Check materialized views
  • Check the status of all materialized views (MV), and refresh any materialized views that are not fresh.

  • Check the size of your materialized view logs. If any materialized view logs have non-zero rows, then refresh the base table materialized views.

  • Check the size of direct loader logs and PMOP logs (partition maintenance operation logs). If any direct loader logs or PMOP logs have non-zero rows, then refresh the MVs indicated by the logs.

Obtain performance baseline
  • Preserve performance statistics

  • Check network performance

Perform system integrity checks
  • Perform your own integrity checks

  • Run Pre-Upgrade Information Tool (preupgrade.jar)

Check Time Zone setting
  • Default time zone version for Oracle Database 12c release 2 (12.2) is V26

  • If the source database Time Zone version is higher than the target database, then apply the Time Zone patch on the target database to match the source database version.

    Time Zone defaults are in located in the path $ORACLE_HOME/oracore/zoneinfo.

Gather dictionary statistics

To decrease Oracle Database downtime, gather optimizer statistics.

Back up the database
  • Back up the database, create a guaranteed flashback restore point, or both.

  • Test your fallback strategies at least once before your upgrade window.

  • Ensure that you have fallback strategies for issues both during upgrade, and after upgrade.

Target Server Post-Upgrade Checklist

Complete these checks on the upgraded Oracle Database environment.

Table 2-2 Target Server Post-Upgrade Checklist

Task Description
Run postinstallation SQL scripts
  • $ORACLE_HOME/rdbms/admin/utlrp.sql

  • $ORACLE_HOME/rdbms/admin/utlu122s.sql

  • $ORACLE_BASE/cfgtoollogs/SID/preupgrade/postupgrade_fixups.sql

Review upgrade logs and trace files
  • $ORACLE_BASE/cfgtoollogs/DBUA/upgradeTimestamp

    (Look under $ORACLE_HOME if $ORACLE_BASE is not set). Also, folders with the system identifier (SID) of individual database are in this timestamp folder. The SID folders contain files for individual databases for the preupgrade and upgrade process.


Verify upgrade status for CATALOG and CATPROC components
  • select substr(comp_name, 1, 45) as comp_name, substr(version,1,8) as version , substr(status,1,8) as status from dba_registry

    Look for version and status changes.

Run Oracle Database 12.2 Post-Upgrade Status Tool (utlu122s.sql)
  • /rdbms/admin/utlu122s.sql

Update time zone settings
  • If Time Zone version at source database is lower than the target database, then run Time Zone conversion after the upgrade.

    Time Zone defaults are in the path $ORACLE_HOME/oracore/zoneinfo

Create Oracle Database system files
  • Create an SPFILE from the PFILE

  • Gather new Oracle Cost-Based Optimizer (CBO) statistics

  • Back up the database