Two problems encountered by exp/imp (ORA-00904 and theobjectswereexportedb

Recently, I was responsible for setting up the user environment of a system, which involved importing data from the test environment. due to objective constraints, the table space transfer method cannot be used for synchronization. Therefore, impexp or data pump is required, impexp is used here. The following describes the problems encountered during the operation. Problem 1: exp export ORA-00904: IFREEPOOL: invalidid

Recently, I was responsible for setting up the user environment of a system, which involved importing data from the test environment. due to objective constraints, the table space transfer method cannot be used for synchronization, therefore, the imp/exp or Data Pump method is required. Here imp/exp is used. The following describes the problems encountered during the operation. Problem 1: exp export ORA-00904: IFREEPOOL: invalid

Recently, I was responsible for setting up the user environment of a system, which involved importing data from the test environment. due to objective constraints, the table space transfer method cannot be used for synchronization, therefore, the imp/exp or Data Pump method is required. Here imp/exp is used. The following describes the problems encountered during the operation.

Problem 1: ORA-00904 for exp export: "IFREEPOOL": invalid identifierAnd "OLEVEL": invalid identifier Error

First operation:

The version used to execute imp/exp is: 10.2.0.4

The database version used for export is: 10.2.0.3

Execute exp abc/xxx file = test. dmp log = exp_test.log

There are some alarms in the process:

EXP-00008: ORACLE error 904 encountered
ORA-00904: "IFREEPOOL": invalid identifier
...
EXP-00008: ORACLE error 904 encountered
ORA-00904: "OLEVEL": invalid identifier

...

EXP-00000: Export terminated unsuccessfully

This MOS article (726182.1) describes the causes of this problem:

If the source database is 10.2.0.3, the export client must be 10.2.0.3, mainly because the export tool keeps accessing the data dictionary object, such as SYS. EXU9LOG, but a new column "IFREEPOOL" is introduced in 10.2.0.4. This column information is not found in 10.2.0.3, so it cannot be operated.

From this we can see that the problem may be caused by the table operation on the LOB object. workaround uses version 10.2.0.3 and later. Therefore, 10.2.0.1 is used, and the above error is not returned for export.

Question 2: during import, Warning: the objects were exported by ABC not by you didn't import any objects

Execute imp xyz/xxx file = test. dmp log = imp_test.log ignore = y commit = y buffer = 300000000 feedback = 10000

Prompt during process:

Warning: the objects were exported by ABC, not by you
...
Import done in ZHS16GBK character set and AL16UTF16 NCHAR character set
. Importing RTCRM's objects into UAT_RTCRM
Import terminated successfully without warnings.

No object is imported to the target database.

The error message Warning: the objects were exported by RTCRM, not by you indicates that the data to be imported belongs to the ABC user, but the user XYZ is used for import, therefore, you must specify the user name for different import and export usernames. Execute:

Imp xyz/xxx file = test. dmp log = imp_test.log fromuser = abc touser = xyz ignore = y commit = y buffer = 300000000 feedback = 10000

The import operation is successfully performed.