Donald K. Burleson
Oracle MIG utility
13. Remove the old control files; they
14. From SQLPLUS, issue these commands: CONNECT INTERNAL and STARTUP
15. From SQLPLUS, the DBA issues the ALTER DATABASE CONVERT command
on the Oracle side. This command creates a new controlfile,
converts all online file headers to Oracle format, and mounts the
Oracle instance. This is the point of no return.
16. The DBA issues the ALTER DATABASE OPEN RESETLOGS command on the
Oracle side, which automatically converts all objects and users
defined in the new dictionary to Oracle specifications. It also
converts all rollback segments to Oracle format.
17. Finish converting the catalog to a full Oracle catalog by
running cat9000.sql, usually located in the $ORACLE_HOME/rdbms/admin
subdirectory on UNIX. Then run catalog.sql, located in the same
place. Finally, run catproc.sql to rebuild the PL/SQL and utility
packages. If needed, also run any other cat.sql scripts to install
any purchased options as required.
18. Shut down and back up your new Oracle-ready database.
Using Oracle Data Migration Assistant (ODMA)
The Oracle Data Migration Assistant allows an Oracle8 or 8i database
to be upgraded to 9i. This is considered a release-to-release
upgrade, not a migration, according to Oracle support. ODMA is a
command-line utility written in Java. This means that a compatible
JDK or JRE must be installed. For Linux, this would be jdk118_v3 or
jre118_v3 from Blackdown or the equivalent Sun release. I also found
that, for Linux, the local LANG variable had to be unset or
segmentation faults will occur.
This is an
excerpt by Mike Ault’s book “Oracle
Administration & Management”. If you want more current Oracle tips
by Mike Ault, check out his new book “Mike
Ault’s Oracle Internals Monitoring & Tuning Scripts” or
Ault’s Oracle Scripts Download.
Copyright © 1996 - 2014 by
Burleson. All rights reserved.
Oracle® is the registered trademark
of Oracle Corporation.