Errors caused by Oracle 11g import to 10g

Environment Introduction
Old environment		New environment
Operating system:	redhat5.8 64-bit		redhat6.4 64-bit
Database version:	Oracle 10.2.0.4 64-bit		Oracle 11.2.0.4 64-bit

Background: A previous set of old database RAC was built on oracle10g and ran for several years. The front-end application is now ready to upgrade, considering that the new database used by the front-end application is somewhat different from the old one, and is ready to import the database used by the new environment into the old environment, there is a cross-version import issue, and the other way is to upgrade the old environment database to the same version as the new environment. Consider factors such as potential problems with the upgrade and on-site environments. After communicating with the project leader, the first method is decided. The test results are now recorded as follows:

1, in the Oracle 10g environment through EXP to import 11g database to local, error is as follows:

Encountering errors in Export logfile

Exp-00008:oracle Error # encountered

ora-01455:converting column overflows integer datatype

2, in 11g environment with EXP will export data, and then through IMP user/[email protected] remote way to import, error is as follows:

IMP-00015: Because an object already exists

Description: Before importing into 10g, confirm that 10g does not have a task-related user object, which results in some tables not being imported, presumably due to the Clob field.

3, in 11g environment with EXPDP and specify version to export data to 10g, and then through IMPDP and specify version to import data, error is as follows:

EXPDP User/password directory=impdp_dir dumpfile=file.dmp version=10.2.0.4 (version number to import into 10g)

IMPDP User/password Directory=impdp_dir dumpfile=file.dmp version=10.2.0.4

Ora-39139:data Pump does not support XMLTYPE objects in version 10.2.0.4 table_data: "Test". " TABLE_NAME "would be skipped.

Note: This way there is an import to skip directly, because there is no data in this table, directly the creation of the table statement in 10g to re-execute.

Errors caused by Oracle 11g import to 10g