EXP-00008: Oracle error 904

Case Scenario-when an Oracle database is exported:

C: \ Documents ents and Settings \ Administrator> exp lsxy/lsxy @ lsxy_db file = E: \ lsxy. dmp owner = lsxy

Export: Release 11.2.0.1.0-Production on Monday November 26 14:07:18 2012 Copyright (c) 1982,200 9, Oracle and/or its affiliates. All rights reserved.

Connect to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0-64bit Production
With the Partitioning, Data Mining and Real Application Testing options
The ZHS16GBK and AL16UTF16 NCHAR character sets have been exported.
. Exporting objects and operations in the pre-schema Process
. Exporting the external function library name of user JXUNICOM
. Export PUBLIC type Synonyms
. Exporting the special type Synonym
. Exporting the object type definition of user JXUNICOM
Object To be exported to JXUNICOM...
. Exporting database link...
. Exporting sequence number
. Exporting cluster Definition
. To export the JXUNICOM table through the regular path...
EXP-00008: ORACLE error 904
ORA-00904: "POLTYP": invalid identifier
EXP-00000: Export termination failed

EXP-00008: An export error with ORACLE error 904 is reported.

According to the online data and summary, the analysis may be caused by the inconsistent version of the locally used exp export tool and the database server exp version.

In the command operation, we found that the Oracle version installed locally is Release 11.2.0.1.0, while the Oracle version installed on the database server is Release 10.2.0.4.0.

The Oracle imp/exp component operation principle is backward compatible with some rules:

Rule 1: Earlier exp/imp versions can be connected to database servers of higher versions (or the same version), but later exp/imp versions cannot be connected to database servers of lower versions;

Rule 2: A dmp file generated in a higher version exp, which cannot be imp in a lower version (the dmp file cannot be identified); A dmp file generated in a lower version exp can be imp (backward compatible) in a later version );

Rule 3: Data from earlier versions of Oracle Export can be imported to later versions of Oracle, but it is limited to adjacent versions of Oracle, such as from Oracle 10 to Oracle 11. For conversions between two non-adjacent versions, such as from Oracle 9 to Oracle 11, data should be first input to the intermediate version-Oracle 10, and then transferred from the intermediate database to a later version of Oracle 11.

Therefore, the quickest solution is to export database data on the server using a 10 Gb Oracle host.