Professional Documents
Culture Documents
.
**********************************************************************
Tablespaces: [make adjustments in the current environment]
**********************************************************************
> SYSTEM tablespace is adequate for the upgrade.
.
.
.
.
WARNING: > Database contains schemas with objects dependent on network
packages.
. Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
. USER SYSMAN has dependent objects.
WARNING: > EM Database Control Repository exists in the database.
. Direct downgrade of EM Database Control is not supported. Refer to the
. 11g Upgrade Guide for instructions to save the EM data prior to upgrade.
.
PL/SQL procedure successfully completed.
The utility will give the output in the form of recommendations to be implemented before
starting the upgrade. Unless these requirements are met, the upgrade will fail.
Step 3) Executing the recommended steps
Following are the critical steps to be executed based on above warnings. These commands are to
be executed while connecting to database from 10g Oracle Home
WARNING: > Database is using an old timezone file version.
. Patch the 10.2.0.1.0 database to timezone file version 4
. BEFORE upgrading the database. Re-run utlu111i.sql after
. patching the database to record the new timezone file version.
Finding the Version of existing timezone files:
SQL> select * from v$timezone_file;
FILENAME VERSION
timezlrg.dat 2
SQL> SELECT CASE COUNT(DISTINCT(tzname))
WHEN 183 then 1
WHEN 355 then 1
WHEN 347 then 1
WHEN 377 then 2
WHEN 186 then case COUNT(tzname) WHEN 636 then 2 WHEN 626 then 3 ELSE 0 end
WHEN 185 then 3
WHEN 386 then 3
WHEN 387 then case COUNT(tzname) WHEN 1438 then 3 ELSE 0 end
WHEN 391 then case COUNT(tzname) WHEN 1457 then 4 ELSE 0 end
WHEN 392 then case COUNT(tzname) WHEN 1458 then 4 ELSE 0 end
WHEN 188 then case COUNT(tzname) WHEN 637 then 4 ELSE 0 end
WHEN 189 then case COUNT(tzname) WHEN 638 then 4 ELSE 0 end
ELSE 0 end VERSION
FROM v$timezone_names;
VERSION
2
If the Version of the existing timezone is less than 4, then apply the patch for Version 4 timezone
files.
Check the database version
SQL> select banner from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 Prod
PL/SQL Release 10.2.0.1.0 Production
CORE 10.2.0.1.0 Production
TNS for Linux: Version 10.2.0.1.0 Production
NLSRTL Version 10.2.0.1.0 Production
For 10.2.0.1 check the metalink note ID 413671.1. We have a table which defines the patch to be
applied.
Always try to use the official patch
The script (and on 10g also the csv file) are normally delivered through installation of a patch in
the Oracle home. Please note that before using this note you are advised to double check that the
time zone patches are not available for your patchset. Applying the correct patch through
opatch is always preferable to the manual method described in this note.
If there is no official patchset for the version you are currently having then you can Identify the
utltzuv2.sql & timezdif.csv combination patch for a different patchset, but same release.
For example if you run 10.2.0.1 and you are trying to find the utltzuv2.sql script & timezdif.csv
file you can find the correct patch 5632264 for 10.2.0.2 and this will be applicable to 10.2.0.1 as
well.