EXP-00008: ORACLE error 904 encountered的解决方法

error|oracle|解决

【错误情况】

[[email protected] admin]$ exp wmap/[email protected]

Export: Release 8.1.7.4.0 - Production on Fri Oct 8 11:28:37 2004

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

Connected to: Oracle9i Release 9.2.0.1.0 - Production
JServer Release 9.2.0.1.0 - Production
Enter array fetch buffer size: 4096 >

Export file: expdat.dmp > host    

(2)U(sers), or (3)T(ables): (2)U > u

Export grants (yes/no): yes >

Export table data (yes/no): yes >

Compress extents (yes/no): yes >

Export done in WE8ISO8859P1 character set and UTF8 NCHAR character set
server uses ZHS16GBK character set (possible charset conversion)
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user WMAP
. exporting object type definitions for user WMAP
About to export WMAP's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. about to export WMAP's tables via Conventional Path ...
EXP-00008: ORACLE error 904 encountered
ORA-00904: "SPOLICY": invalid identifier
EXP-00000: Export terminated unsuccessfully
[[email protected] admin]$

【解决方法一】 
Bookmark Go to End 

 

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 ID:(9.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>.
 【解决方法二】
If this error (ORA-904 invalid column name) occurs after applying a patch, this would probably fix the problem.
1. First, run CATEXP as INTERNAL. Then retry the export. Often times this will fix the problem and then export will run without error. The reason being a problem with object EXU8FIL view has been detected.
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.

时间: 2016-02-09

EXP-00008: ORACLE error 904 encountered的解决方法的相关文章

IMP-00003: ORACLE error 3113 encountered ORA-03113: end-of-file on communication channel

 IMP-00003: ORACLE error 3113 encountered  ORA-03113: end-of-file on communication channel . . importing table    "SFP_FILE_6"      11179 rows imported IMP-00017: following statement failed with ORACLE error 3113:  "DECLARE  SREC DBMS_STATS

ORACLE中一些问题的解决方法

oracle|解决|问题  ORACLE中一些问题的解决方法 在ORACLE管理和应用中,难免出现一些问题.通常,ORACLE会显示错误标号和简短说明,我们可以根据显示的信息去处理问题.但有时显示的信息很少,处理起来有些麻烦.本文讨论了这样几个问题,根据一些资料和经验,提出了解决方法.   一.             ORA-00604 error occurred at recursive SQL level 这个信息表明,在数据库执行内部SQL语句时,发生了错误.比如,要往表中插入一行数据

win7电脑开机后显示CPU Fan Error错误提示的解决方法

win7电脑开机后显示CPU Fan Error错误提示的解决方法 方法一: 如果出现CPU风扇接线接错的情况会导致出现CPU Fan Error提示,打开机箱检查CPU风扇是否连接到主板对应的接口即可. 方法二: 开机后就按下DEL键进入BIOS,进入POWER的Hardware Monitor,将CPU FAN SPEED项改成IGNORED,CHASSIS FANSPEED项改成N/A,POWER FAN SPEED项改成IGNORED,然后看是否还会出现错误提示. 方法三: 或者是由于一

Win7系统error code 0x00000005错误解决方法

  声卡驱动是一种可以使计算机和设备通信的特殊程序,可以说相当于硬件的接口,操作系统只有通过这个接口,才能控制硬件设备的工作,假如某设备的驱动程序未能正确安装,便不能正常工作. 因此,驱动程序被誉为" 硬件的灵魂".声卡是计算机进行声音处理的适配器.它有三个基本功能:一是音乐合成发音功能;二是混音器(Mixer)功能和数字声音效果处理器(DSP)功能;三是模拟声音信号的输入和输出功能.所以一旦声卡驱动安装出错,就必然导致电脑声音信号的输入.输出和处理.下面小编就为大家介绍,当系统报错e

丢失Android系统库或者Conversion to Dalvik format failed with error 1错误的解决方法_Android

本文分析了丢失Android系统库或者Conversion to Dalvik format failed with error 1错误的解决方法.分享给大家供大家参考,具体如下: 在eclipse开发Android项目时出现的很多问题都可以使用Project--------->clean来轻易解决. 但如果出现说Android库找不到,或者不小心remove了Android系统库,怎么重新添加Android系统库呢?在eclipse里面的Java Build Path里面是没法添加例如Andr

mysql登录报错提示:ERROR 1045 (28000)的解决方法_Mysql

本文分析了mysql登录报错提示:ERROR 1045 (28000)的解决方法.分享给大家供大家参考,具体如下: 一.问题: 公司linux系统的mysql数据库root用户设置过密码,但常常用命令'mysql -u root -p'登录报错,有时又能登录.登录报错信息为: [[email protected] ~]# mysql -u root -p Enter password: ERROR 1045 (28000): Access denied for user 'root'@'localho

mysql主从同步失败Last_IO_Error: Got fatal error 1236 from master解决方法

mysql教程主从同步失败Last_IO_Error: Got fatal error 1236 from master解决方法 遇到这样的错误如:"Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file'"等或由于清数据导致主从库不同步了,解决办法如下:

【Oracle】RMAN-03009 ORA-01400 错误解决方法

  生产库备份遇到ORA-01400 错误~当rman 不使用 catalog时,RMAN 命令可以正常实施~!当rman 备份使用catalog数据库时,执行rman 命令总是报错:ORA-01400:cannot insert NULL into ("RMAN_YANGDB"."RLH"."LOW_TIME") RMAN> resync catalog; starting full resync of recovery catalog

【MySQL】Got fatal error 1236原因和解决方法

一 前言  MySQL 的主从复制作为一项高可用特性,用于将主库的数据同步到从库,在维护主从复制数据库集群的时候,作为专职的MySQL DBA,笔者相信大多数人都会遇到"Got fatal error 1236 from master when reading data from binary log" 这类的报错/报警.本文整理了常见的几种 error 1236 报错,并给出相应的解决方法,有所不足之处,当然也希望各位读者朋友指正. 二 常见的error 1236 报错2.1 log