关于EXP导出的问题

mwdba

系统环境：
SOLARIS2.8+ORACLE8.1.7.4.0

不管导出哪一张表都报错，错误信息如下：
[B]
bash-2.03$ exp xlt/xlt_web file=1.dmp tables=ALREADY_SEND_SM

Export: Release 8.1.7.4.0 - Production on Mon Feb 16 15:45:23 2004

(c) Copyright 2000 Oracle Corporation.  All rights reserved.


Connected to: Oracle8i Enterprise Edition Release 8.1.7.4.0 - 64bit Production
With the Partitioning option
JServer Release 8.1.7.4.0 - 64bit Production
Export done in ZHS16CGB231280 character set and ZHS16CGB231280 NCHAR character set

About to export specified tables via Conventional Path ...
EXP-00008: ORACLE error 904 encountered
ORA-00904: invalid column name
EXP-00000: Export terminated unsuccessfully
[B]bash-2.03$ exp xlt/xlt_web file=1.dmp tables=ALREADY_SEND_SM[/B]



真是急死人

sofayoung

我也碰到这个问题不知道怎么办？

k_598

是否是表的字段名称有问题？
可以先导出一个小表的数据试试。

blue_prince10

from metalink:

Bookmark Go to End

Doc ID:  Note:232708.1
Subject:  Handling ORA-00904 errors on Export
Type:  PROBLEM
Status:  PUBLISHED
Content Type:  TEXT/X-HTML
Creation Date:  23-NOV-2001
Last Revision Date:  06-OCT-2003




fact: Oracle Server - Enterprise Edition
symptom: ORA-00904: Invalid column name
symptom: EXP-00008: ORACLE error %s encountered
cause: The package is missing, invalid or corrupt



fix:

How to handle ORA-00904 errors on Export
========================================

When running full database export the following errors will be returned:

exp80 user/password full=y file=D:\DB-Backup\ORCL\expORCL.dmp
log=D:\DB-Backup\ORCL\expORCL.log consistent=y buffer=40960000

    EXP-00008: ORACLE error 904 encountered
    ORA-00904: invalid column name




To get a clue what has force these ORA-00904 message, follow the following
steps:

1. Connect as privileged user and run the following command inside an
   SQLPLUS session:

   SQL> alter system set events='904 trace name errorstack';

   -------------------------------- Note ------------------------------------

   This event will work starting with Oracle8i. If running a Oracle database
   version below Oracle8i, you'll get ORA-02065 errors returned, when
   specifying this event. In Oracle versions below 8i you'll have to insert
   the following entry into INIT.ORA

   event="904 trace name errorstack"
   
   --------------------------------------------------------------------------

2. Retry the FULL export. When the ORA-00904 occurs, a trace file will be
   written to the storage location specified by the INIT.ORA parameter
   'user_dump_dest'. As soon as the ORA-00904 has been returned to your
   export session, you can abort the export and examine the trace information.

3. Disable event tracing by running the following command:

   SQL> alter system set events='904 trace name errorstack off';

   On Oracle versions below 8.1.5 return the event entry from INIT.ORA

4. Examine the trace file:

   *** SESSION ID9.3) 2001.11.21.15.28.00.494
   *** 2001.11.21.15.28.00.494
   ksedmp: internal or fatal error
   ORA-00904: invalid column name
   Current SQL statement for this session:
   SELECT fname,fsize,maxextend,inc FROM sys.exu8fil WHERE tsid = :1
                                         ===========

   a) a problem with object EXU8FIL has been detected
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   In this example, there's a problem with the EXE8FIL view. To examine,
   whether this object exist, run the following command:

   SQL> select owner,object_name,object_type,object_id,status
        from   dba_objects
        where  object_name='EXU8FIL';

   If the problem is on the EXU8FIL object you simply can recreate the
   object by running the CATEXP.SQL script.

   b) a problem with object DBMS_JAVA or DBMS_JAVA_TEST
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   ksedmp: internal or fatal error
   ORA-00904: invalid column name
   Current SQL statement for this session:
   SELECT SYNNAM, DBMS_JAVA.LONGNAME(SYNNAM), DBMS_JAVA.LONGNAME(SYNTAB), ...

   On systems where the Java Server has been installed the trace file could
   contain information on a failing select statement on DBMS_JAVA packages.

   For reference on fixing errors relating to DBMS_JAVA, please follow
   <Note:1017276.102>.