EXP-00008: ORACLE error 904 Problems

EXP-00008: encountered ORACLE error 904 case scenario -- at an Oracle Database Export: www.2cto.com C: \ Documents and Settings \ Administrator> exp lsxy/lsxy @ lsxy_db file = E: \ lsxy. dmp owner = lsxyExport: 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 ProductionWith the Partitioning, Data Mining and Real Application Testing options have exported the ZHS16GBK Character Set and AL16UTF16 NCHAR character set. exporting objects and operations in the pre-schema process. exporting the external function library name of user JXUNICOM. export a PUBLIC synonym. exporting the special type synonym. exporting the object type definition of JXUNICOM to export the object of JXUNICOM .... exporting database link. exporting sequence number. exporting the cluster definition. the table to be exported to JXUNICOM will pass the regular path... EXP-00008: encountered ORACLE error 904ORA-00904: "POLTYP": invalid identifierEXP-00000: Export Termination failure occurred EXP-00008: encountered ORACLE error 904 export error. 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. Due to the operational principles of Oracle imp/exp components-downward compatibility, there are some rules: rule 1: Earlier exp/imp versions can be connected to the higher version (or the same version) but the exp/imp of the higher version cannot connect to the database server of the lower version. Rule 2: dmp files output from the higher version exp, earlier versions cannot be imp (dmp files cannot be identified); later versions can be imp (backward compatible) for dmp files generated by exp; 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.