Started database in upgrade mode and fired catupgrd.sql :
SQL> startup upgrade
ORACLE instance started.
Total System Global Area
6413680640 bytes
Fixed Size
2160112 bytes
Variable Size
1946159632 bytes
Database Buffers
4429185024 bytes
Redo Buffers
36175872 bytes
Database mounted.
Database opened.
SQL> @catupgrd.sql
DOC>#######################################################################
DOC>#######################################################################
DOC>
DOC> The first
time this script is run, there should be no error messages
DOC> generated;
all normal upgrade error messages are suppressed.
DOC>
DOC> If this
script is being re-run after correcting some problem, then
DOC> expect the
following error which is not automatically suppressed:
DOC>
DOC> ORA-00001:
unique constraint () violated
DOC>#
FROM
registry$database
*
ERROR at line 2:
ORA-00942: table or view does not exist
This error is related
to timezone file which must be version 4
for Oracle version 11g.If timezone is not version 4 than patch needs to be
applied.
Query to check timezone file
is:
SQL> select * from v$timezone_file;
FILENAME
VERSION
———— ———-
timezlrg.dat
4
SQL> select * from v$timezone_file;
FILENAME
VERSION
———— ———-
timezlrg.dat
4
So I had correct version.I remember applying patch before
upgrade.I got lucky because patch existed for version 10.2.0.3.
If there is no patch for your Oracle versions than patch can
be download for similar version and
applied manually.
Instructions are below:
1. Download the
identified patch.
2. Unzip the patch, and locate the 2 files timezone.dat and
timezlrg.dat in the “files/oracore/zoneinfo” directory of the uncompressed
patch (or from the relevant .jar file of a
patchset). If there is also a readme.txt in this location then make a
note of this as well.
3. Backup your existing files in
$ORACLE_HOME/oracore/zoneinfo – THIS CAN BE VITAL, DO NOT SKIP.
Note:
Before going on with step 4, make sure the current files are
not in use.
On Windows the files will simply refuse to be removed when
the are in use.
On Unix replacing the files whilst they are in use can cause
the files to become corrupt. Use the fuser command before replacing the files
to make sure they are not in use.
4. Copy the 2 .dat files and possibly the readme.txt file
that were found in step 2 into the $ORACLE_HOME/oracore/zoneinfo directory.
5. Restart the database (in case of installation on a
database), or restart the client applications (in case of client install). Note
that the database did not need to be down before the time zone files were
applied, but it does need to be restarted afterwards.
No comments:
Post a Comment