How to Download and Run Oracle's Database Pre-Upgrade Utility

How to Download and Run Oracle's Database Pre-Upgrade Utility [ID 884522.1]
Modified 05-MAY-2011 Type HOWTO Status PUBLISHED
In this Document
Goal
Origin of Script
Solution


[Insert note here]
Script Guidelines
Script Execution Steps
Script Changes
References
Applies to:

Oracle Server - Standard Edition - Version: 9.2.0.4 to 11.2.0.2 - Release: 9.2 to 11.2
Oracle Server - Enterprise Edition - Version: 9.2.0.4 to 11.2.0.2 [Release: 9.2 to 11.2]
Information in this document applies to any platform.
Goal

One of the first steps that should be taken prior to an Oracle Database Upgrade is determining any issues the upgrade may present to your database.

Oracle Database Pre-Upgrade utility is executed on your existing database, while the database is running (no shutdown required) and provides a list of items which should be reviewed prior to the actual upgrade. Reviewing and making adjustments prior to actual database upgrade will usually reduce down time and can limit problems during the upgrade.

Origin of Script

The pre-upgrade scripts that are available for download below are shipped with each Oracle Database release. The scripts can also be found in the newly installed $ORACLE_HOME/rdbms/admin directory of the version you are planning to upgrade to. Getting a hold of the pre-upgrade script used to mean downloading the entire Oracle Database Release kit, unpacking it, and pulling it out of the admin directory. Allowing access to the script through this method will make the Oracle Database Upgrade planning easier.

Solution

[Insert note here]
Script Guidelines

The pre-upgrade scripts can be executed on a database without the need to shutdown or restart the database. It gathers information about the database configuration and reports on conditions, parameters and settings which may need attention prior to upgrading to the new version.

You must have DBA privilege to execute the script successfully.

The Database can not be in read-only mode. A few registry$ tables may be created, if they do not already exist, and some rows may be inserted into existing Upgrade tables.
Script Execution Steps

See the table below to determine which version of the pre-upgrade script you need. It will depend on which version you are upgrading from, and which version you are upgrading to
Save the file to a directory that will be accessible when you connect to your database
Run SQL*Plus and connect to the database to be upgraded using an account with DBA privileges
Set spool output to save data reported by the script
Execute the script
Review the output
Correct any deficiencies noted in the script output

Coming From Version

Script Build/Date

Upgrade Target Version

9.2.0 (9.2.0.8 and above),
10.1.0, 10.2.0,
11.1.0, 11.2.0.1
Build 4
December 2010 11gR2
(11.2.0.2) - utlu112i_2.sql
Use the above script when your target upgrade is 11.2.0.2. If you are planning to upgrade to 11.2.0.1, use the utlu112_1.sql script below.
9.2.0 (9.2.0.8 and above),
10.1.0, 10.2.0,
11.1.0
Build 4
December 2010 11gR2
(11.2.0.1) - utlu112i_1.sql
9.2.0 (9.2.0.4 and above),
10.1.0,10.2.0
Build 2
December 2010 11gR1- utlu111i.sql
8.1.7, 9.0.1,
9.2.0 (9.2.0.4 and above),
10.1.0
Build 2
December 2010 10gR2 - utlu102i.sql
Script Changes

utlu112i_2.sql - Upgrade to 11.2.0.2 - Build 4 - December 2010

This script should be used when upgrading to 11.2.0.2. The version of the timezone file shipped with 11.2.0.2 is newer than 11.2.0.1 and this version verifies you are at the right version for an upgrade to 11.2.0.2.
All changes fixed in utlu112i_1.sql
Timezone to version 14
utlu112i_1.sql - Upgrade to 11.2.0.1 - Build 4 - December 2010

Below are the enhancements and changes added into Build 4:
Timezone version updates
Obsolete cell_partition_large_extents
OLS & DV msgs to reflect 112 installer
Fix connect by statement
Add DMSYS recommendation coming from 11.1 to 11.2
Size tablespace with apex correctly
Fix invalid object list
Fix XML output for STATUS/VERSION of components
Fix for xml output
Change drop table to truncate if possible
Check for editioning views
utlu111i.sql - Build 2 - December 2010

Below are the enhancements and changes added into Build 2:
Timezone version updates
Optimize select statements for dba_queues
utlu102.sql - Build 2 - December 2010

Below are the enhancements and changes added into Build 2:
cursor_space_for_time is deprecated
Tablespace size updates
Invalid Object update
utlu112i.sql - Build 3 - June 2010

Below are the enhancements and changes added into Build 3:
Linesize decreased to 100
Check for Stale Statistics removed
Recommendation section added (Hidden parameter/events moved to this section)
utlu112i.sql - Build 2 - May 2010

Below are the enhancements and changes added into Build 2:
Warning issued about hidden parameters that are in use
Warning issued about non-default events
Warning issued about ldap dependencies
Warning issued if database in MOUNT state
Warning added relating to UltraSearch
Warning issued if run by non SYS-DBA
Warning for Recycle bin added (changed from recommend to MUST be purged)
Recommendations added on shared pool size for both 32/64 bit target systems
Stats check updated
Allow limited set of checks if database in read-only mode
Removed Network ACL check
Removed cursor_space_for_time warning
Removed text relating to auto-extent. Wording was too confusing
Removed ASM check (non-functioning)

References

NOTE:466181.1 - 10g Upgrade Companion
NOTE:601807.1 - Oracle 11gR1 Upgrade Companion
NOTE:785351.1 - Oracle 11gR2 Upgrade Companion

Attachments
Upgrade Script for 10.1 (130.5 KB)
Upgrade Script for 11.1 (157.09 KB)
Upgrade Script for 11.2.0.1 (200.03 KB)
Upgrade Script for 11.2.0.2 (200.11 KB)
Related
Products
Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Standard Edition
Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition
Keywords
DATABASE UPGRADE; ORACLE DATABASE; PRE-UPGRADE UTILITY; UPGRADE; UPGRADE 10.2.0; UPGRADE 11.1.0.7; UPGRADE PREPARATION; UTILITY

Back to top

Rate this document