bea0883
asked on
DATABASE MIGRATION FROM SOLARIS TO WINDOWS 2000
Hi,
need advise for database migration.
Current database oracle 8.16, platform Solaris e-450, os 2.6
New database oracle 9.2, platform window 2000.
Since full export file size over than 2G, the exp file is compressed in **.dmp.Z.
What is the command to uncompress dmp file and import the table to the new database on window 2000?
Dose all the old procedure still usefull?
Is any change on calling a DBA_JOB to schedule auto procedure run?
Please provide me all suggestion from your experience.
need advise for database migration.
Current database oracle 8.16, platform Solaris e-450, os 2.6
New database oracle 9.2, platform window 2000.
Since full export file size over than 2G, the exp file is compressed in **.dmp.Z.
What is the command to uncompress dmp file and import the table to the new database on window 2000?
Dose all the old procedure still usefull?
Is any change on calling a DBA_JOB to schedule auto procedure run?
Please provide me all suggestion from your experience.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
And there is no change on DBMS_JOB package to schedule auto procedure run on 9.2. The procedure will work after importing sucessfully
that export is not useful in windows
use the utilities from 9.2 in win to export and import
use the utilities from 9.2 in win to export and import
hi,
have the backup of the database in Solaris as
$exp user/password file=expFILE.dmp log=expfile.log full=y
$compress expFILE.dmp
then u get a file like expFILE.dmp.Z
or
$zip expFILE.dmp
in Windows unzip this file
and import the entire database.
regarrds
sudarshan
have the backup of the database in Solaris as
$exp user/password file=expFILE.dmp log=expfile.log full=y
$compress expFILE.dmp
then u get a file like expFILE.dmp.Z
or
$zip expFILE.dmp
in Windows unzip this file
and import the entire database.
regarrds
sudarshan
@bea:
you can do the math easily
for example 20G data dump
if you set filesize at 2G
then you will have 10 file exp file.
you can do the math easily
for example 20G data dump
if you set filesize at 2G
then you will have 10 file exp file.
the following info is for using export/import between different Oracle version.
Matrix : Which EXPORT utility to use when importing into an Oracle8 or a higher database release
(always use IMPORT utility of the target database):
+----------+--------------
| EXPORT | IMPORT into: |
| from +--------+--------+-------
| \/ | 8.0.5 | 8.0.6 | 8.1.5 | 8.1.6 | 8.1.7 | 9.0.1 | 9.2.0 |
+----------+--------+-----
| 5.x 1) 2)| EXP5x | EXP5x | EXP5x | EXP5x | EXP5x | EXP5x | EXP5x |
| 6.x 2)| EXP6x | EXP6x | EXP6x | EXP6x | EXP6x | EXP6x | EXP6x |
| 7.x 3)| EXP7x | EXP7x | EXP7x | EXP7x | EXP7x | EXP7x | EXP7x |
+----------+--------+-----
| 8.0.4 | EXP804 | EXP804 | EXP804 | EXP804 | EXP804 | EXP804 | EXP804 |
| 8.0.5 | EXP805 | EXP805 | EXP805 | EXP805 | EXP805 | EXP805 | EXP805 |
| 8.0.6 | EXP805 | EXP806 | EXP806 | EXP806 | EXP806 | EXP806 | EXP806 |
+----------+--------+-----
| 8.1.5 | EXP805 | EXP806 | EXP815 | EXP815 | EXP815 | EXP815 | EXP815 |
| 8.1.6 | EXP805 | EXP806 | EXP815 | EXP816 | EXP816 | EXP816 | EXP816 |
| 8.1.7 | EXP805 | EXP806 | EXP815 | EXP816 | EXP817 | EXP817 | EXP817 |
+----------+--------+-----
| 9.0.1 | EXP805 | EXP806 | EXP815 | EXP816 | EXP817 | EXP901 | EXP901 |
| 9.2.0 | EXP805 | EXP806 | EXP815 | EXP816 | EXP817 | EXP901 | EXP920 |
+----------+--------+-----
Remarks: 1) IMPORT can read export dump files created by EXPORT release 5.1.22 and higher (up to same version).
2) An Oracle5 or Oracle6 export dump and an Oracle8 or Oracle8i or Oracle9i IMPORT: see the Oracle Utilities Manual, Chapter 2 "Import" for special considerations to keep in mind.
3) An Oracle7 export dump and an Oracle8 or Oracle8i or Oracle9i IMPORT: constraints on the DATE columns become invalid when TO_DATE function has not been used in the constraint (this was not required in earlier Oracle versions).
Examples.
---------
1. From 7.3.3 to 8.1.6 => Use the EXPORT 7.3.3 to export the data from the
7.3.3 database and IMPORT 8.1.6 to import the data
into the 8.1.6 database.
2. From 8.1.7 to 8.1.7 => Use the EXPORT 8.1.7 to export the data from the
8.1.7 database and IMPORT 8.1.7 to import the data
into the 8.1.7 database.
3. From 9.0.1 to 8.1.7 => Use the EXPORT 8.1.7 to export the data from the
9.0.1 database and IMPORT 8.1.7 to import the data
into the 8.1.7 database.
4. From 8.1.7 to 9.2.0 => Use the EXPORT 8.1.7 to export the data from the
8.1.7 database and IMPORT 9.2.0 to import the data
into the 9.2.0 database.
5. From 9.0.1 to 9.2.0 => Use the EXPORT 9.0.1 to export the data from the
9.0.1 database and IMPORT 9.2.0 to import the data
into the 9.2.0 database.
6. From 8.1.7 to 7.3.4 => Only if never run before, first run CATEXP7.SQL
on the 8.1.7 database in order to create the
Oracle7 data dictionary views; then use the
EXPORT 7.3.4 to export the data from the 8.1.7
database and IMPORT 7.3.4 to import the data into
the 7.3.4 database.
7. From 9.0.1 to 7.3.4 => Not supported.
8. From 8.0.5 to 9.0.1 => Not supported with export FULL=Y and import FULL=Y
9. From 8.1.5 to 9.2.0 => Not supported with export FULL=Y and import FULL=Y
based on the above information, the following way should be practical.
1: on your Windows PC, install a oracle 8.1.6 client. you can have Oracle 816 and Oracle 9i installed in the same PC and in different Oracle home.
2: use Oracle 816 client connect to your Solar database and to do the export.
you should have no 2G file size problem.
3: use Oracle 9.2 import to import the dump file got in step 2.
try it!
ASKER
thanks & Regards,