If you have done data migration between 64bit Oracle and 32bit Oracle, then you will find that DMP files directly from 64bit, you can't Imp on the 32bit Oracle, then how we will solve this Question:
1. Connect in TNSName, then use 32bit Oracle even 64bit Oracle:
C: Documents and settingsduanl> SQLPLUS / NOLOGSQL * PLUS: Release 9.2.0.1.0 - Production On Wednesday June 30 11:56:21 2004CopyRight (C) 1982, 2002, Oracle Corporation. All Rights Reserved.SQL> Connect / As SYSDBA is connected. SQL> Select * from v $ version; banner ---------------------------------------- ------------------------ Oracle9i Enterprise Edition Release 9.2.0.1.0 - ProductionPL / SQL Release 9.2.0.1.0 - ProductionCore 9.2.0.1.0 ProductionTns for 32-Bit Windows: Version 9.2.0.1.0 - Productionnlsrtl Version 9.2.0.1.0 - Production '
Server Oracle 64bit 9204:
SQL> Connect Dlinger/dlinger@ora64.ufsoft.com.cn is connected. SQL> Select * from v $ version; banner ---------------------------------------- ------------------------ Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit ProductionPL / SQL Release 9.2.0.4.0 - ProductionCore 9.2.0.3. 0 ProductionTns for Solaris: Version 9.2.0.4.0 - Productionnlsrtl Version 9.2.0.4.0 - Productionsql> CREATE TABLE TEST (ID INT); Table has been created. SQL> INSERT INTO TEST VALUES (1); 1 line has been created. SQL> Commit; submit completion. '
2. Do EXP on 32bit Oracle (this machine), export 64bit Oracle data:
C: Documents and settingsduanl> exp userid=dlinger/dlinger@ora64.ufsoft.com.cn Owner = DLinger File = 'D: /exp.dmp'Export: Release 9.2.0.1.0 - Production on Wednesday June 30 11: 53:59 2004Copyright (c) 1982, 2002, Oracle Corporation All rights reserved connection to:.. Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit ProductionWith the Partitioning, OLAP and Oracle Data Mining optionsJServer Release 9.2.0.4.0 - Production The exported zhs16GBK character set and the Al16UTF16 nchar character set will be exported to the specified user .... is exporting the pre-schema process object and operation. Export user DLinger's external function library name. Export the PUBLIC type synonym. Export private type synonym. Export User DLinger Type Definition is about to export DLinger's object .... is exporting a database link. The serial number is being exported. The cluster definition is exported. The table to export DLinger is through the regular path .... is exporting table Test 1 line Export. Synonyms are being derived. The view is being derived. The process is being derived. Export operators are exported to reference integrity constraints. Are exporting triggers. Export index type. Export bitmap, functional index and scalable Index. Back table activity is being derived. Exporting the physicalized view. Export snapshot logs. Export job queues. Export refresh groups and subgroups are exporting the dimension. Exporting the POST-Schema process objects and operations. Export statistics. WARNING 3. Import DMP into 32bit Oracle:
C: Documents and settingsduanl> IMP Userid = DLINGER / DLINGER FULL = Y File = 'D: /exp.dmp'Import: Release 9.2.0.1.0 - Production On Wednesday, June 30 11:59:23 2004CopyRight (c) 1982 ., 2002, Oracle Corporation All rights reserved connection to:. Oracle9i Enterprise Edition Release 9.2.0.1.0 - ProductionWith the Partitioning, OLAP and Oracle Data Mining optionsJServer Release 9.2.0.1.0 - Production export via conventional path by the eXPORT: V09. 02.00 The file created has completed the import of the zhs16GBK character set and the Al16UTF16 nchar character set. Import the DLinger object into DLinger.. Import Table "Test" 1 line is imported to stop
4. Query data:
C: Documents and Settingsduanl> SQLPlus DLINGER / DLINGERSQL * PLUS: Release 9.2.0.1.0 - Production On Wednesday, June 30 11:59:57 2004 Copyright (C) 1982, 2002, Oracle Corporation. All Rights Reserved. Connection to: Oracle9i Enterprise Edition Release 9.2.0.1.0 - ProductionWith The Partitioning, OLAP AND ORACLE DATA MINING OPTIONSJSERVER RELEASE 9.2.0.1.0 - Productions QL> Select * from test; id -------- 1 So, if we use 64bit client to exp, then use 32bit client IMP, what will it?
We also do Table on the EXP, exp.dmp is the DMP file I use 64bit client EXP:
D: /> IMP DLINGER / DLINGER FILE = 'D: /EXP64.DMP'
Import: Release 9.2.0.1.0 - Production on Thursday 8 16:44:52 2004
CopyRight (C) 1982, 2002, Oracle Corporation. All Rights Reserved.
Connect to: Oracle9i Enterprise Edition Release 9.2.0.1.0 - ProductionWith The Partitioning, OLAP AND ORACLE DATA MINING OPTIONSJSERVER Release 9.2.0.1.0 - Production
IMP-00010: Not a valid export file, title verification failed IMP-00000: Unsecured termination import
Let's compare the difference between 64 and 32bit EXP DMP files:
From the size, the 64bit DMP file is smaller than the 32bit DMP file under the same amount of DMP file.
Let's take a look at the information of the file:
64bit:
TEXPORT: V09.02.00DDLINGERRTABLES10240320TT
32bit:
TEXPORT: V09.02.00DDLINGERRTABLES20480200TT
The difference between the red word part should be the reason why "Title Verification Failure" is.
