Case scenario-When an Oracle database is exported:
C:\Documents and Settings\administrator>exp lsxy/[email protected]_db file=e:\lsxy.dmp owner=lsxy
Export:release 11.2.0.1.0-production on Monday November 14:07:18 Copyright (c) 1982, the 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
Exported ZHS16GBK character set and Al16utf16 NCHAR character set
. Exporting Pre-schema process objects and operations
. Exporting external function library name for user jxunicom
. Export a public type synonym
. Exporting private type synonyms
. Exporting object type definitions for user jxunicom
Objects that are about to be exported jxunicom ...
. Exporting database Links
. Exporting serial numbers
. Exporting cluster definitions
. The table that is about to be exported jxunicom through the regular path ...
EXP-00008: Encountering ORACLE error 904
ORA-00904: "Poltyp": Invalid identifier
EXP-00000: Export termination failed
occurred EXP-00008: An export error was encountered with ORACLE error 904.
Based on the information and summary on the Web, it may be that the version of the EXP export tool that is used locally is inconsistent with the database server side exp version.
As found in the command operation, the locally installed Oracle version is release 11.2.0.1.0, and the database server-side installation of Oracle is release 10.2.0.4.0.
Due to the operational principles of Oracle's IMP/EXP components-backwards compatible, there are some rules:
Rule 1: A low version of Exp/imp can connect to a higher version (or the same version) of the database server, but the higher version of Exp/imp cannot connect to the lower version of the database server;
Rule 2: High version exp out of DMP file, low version cannot imp (cannot recognize DMP file); Low version exp out DMP file, high version can imp (backwards compatible);
Rule 3: Data from Oracle's low version of export can be import into Oracle high, but is limited to adjacent versions of Oracle, such as Oracle 10 to Oracle 11. Convert between two nonadjacent versions, such as from Oracle 9 to Oracle 11, you should first enter the data into the intermediate version of-oracle 10, and then move from the intermediate database to the higher version of Oracle 11.
As a result, the quickest solution is to use a 10g Oracle-installed machine to export database data on the server.
The most important issue is the version of the EXP/IMP program and the associated database.
EXP-00008: An Oracle Error 904 issue was encountered