Solution of Exp-00008:oracle Error 904 encountered

error|oracle| Solution
"Error Condition"

[ORACLE@CCDEVSVR admin]$ Exp Wmap/pass@jackeydb

Export:release 8.1.7.4.0-production on Fri Oct 8 11:28:37 2004

(c) Copyright to 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
[Oracle@ccdevsvr admin]$


"Workaround One"
Bookmark Go




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

Handle ORA-00904 errors on Export
========================================

When running full database export the following errors would 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 this 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 would work starting with oracle8i. If Running a Oracle database
Version below Oracle8i, you'll get a ORA-02065 errors returned when
Specifying this event. In Oracle versions below 8i "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 would 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 of 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 for 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>.
"Workaround Two"
If This error (ORA-904 invalid column name) occurs after applying a patch, this would probably fix the problem.
1. A, run catexp as INTERNAL. Then Retry the export. Often this'll fix the problem and then export would run without error. The reason being a problem with object Exu8fil view has been.
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 for you simply can recreate the object by running the Catexp. SQL script.