I had a similar problem the other day on a database I inherited. I had
to remove Replication.. Forcefully, and remove the java virtual machine (
you may not need to do this but..)
Note:116283.1
Subject:
Exp-00083 on Full or User Export
Type:
PROBLEM
Status:
PUBLISHED
Content Type:
TEXT/PLAIN
Creation Date:
28-JUL-2000
Last Revision Date:
01-MAR-2002
Problem Description
-- ---- ---- ------
When trying to do a full or user export, the export completes with the
This event will work starting with Oracle8i. If running a Oracle database
version below Oracle8i, you 'll get ORA-02065 (See ORA-02065.ora-code.com) errors returned, when
specifying this event. In Oracle versions below 8i you 'll have to insert
the following entry into INIT.ORA
2. Retry the FULL export. When the ORA-00904 (See ORA-00904.ora-code.com) 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 (See ORA-00904.ora-code.com) 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 (See ORA-00904.ora-code.com): 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 (See ORA-00904.ora-code.com): 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 >.
-- --Original Message-- --
From: oracle-l-bounce@(protected) [mailto:oracle-l-bounce@(protected)]
On Behalf Of Robert Pegram
Sent: Monday, March 07, 2005 8:29 AM
To: oracle-l@(protected)
Subject: RE: Export error
I get the same error on a database I inherited. I looked into fixing it
once, but determined it was not worth the risk. The error does not happen
in test, and I can still use the export file to restore the application data
into another database. There are plans to upgrade that instance this year,
so I will take that opportunity to fix this problem (and several others).
HTH,
Rob Pegram
Duke University
--- "Mercadante, Thomas F " <thomas.mercadante@(protected) > wrote:
> Denham,
>
> Look under the SYS schema for a table called EXPACT$. Look for the
> SYS.DBMS_REPCAT_RGT_EXP entry in this table.
>
> When Oracle export runs, it uses this table to determine what
> additional tables need to be exported - even if you didn 't ask them to
> be exported. I
> have deleted entries in this table in the past when I got the same
> error
> that you got, and the error went away. The example I use is the
> ORDSYS and
> MDSYS stuff. I dropped these schema 's in the past and export
> complained
> about the tables not being there. I removed the entries and all was
> fine.
>
> *Caution*. If you do this and your database dies, it 's not my
> fault!!!
>
> Good Luck!
>
> Tom
>
>
> -- --Original Message-- --
> From: Denham Eva [mailto:EVAD@(protected)]
> Sent: Friday, March 04, 2005 6:33 AM
> To: oracle-l@(protected)
> Subject: Export error
>
> Hello Listers
>
> Does someone please have some advice. An export error has appeared
> since a colleage created a database with replication and as we don 't
> have a license I removed this product using the catrepr.sql script.
> However I now have the following error and would like to know how to
> get
> rid of it.
>
> .......
> . exporting pre-schema procedural objects and actions
> EXP-00008: ORACLE error 6550 encountered
> ORA-06550 (See ORA-06550.ora-code.com): line 1, column 13:
> PLS-00201: identifier 'SYS.DBMS_REPCAT_RGT_EXP ' must be declared
> ORA-06550 (See ORA-06550.ora-code.com): line 1, column 7:
> PL/SQL: Statement ignored
> EXP-00083: The previous problem occurred when calling
> SYS.DBMS_REPCAT_RGT_EXP.schema_info_exp
> . exporting cluster definitions
> ......
> .....
> ....
> ......
> . exporting post-schema procedural objects and actions
> EXP-00008: ORACLE error 6550 encountered
> ORA-06550 (See ORA-06550.ora-code.com): line 1, column 13:
> PLS-00201: identifier 'SYS.DBMS_REPCAT_RGT_EXP ' must be declared
> ORA-06550 (See ORA-06550.ora-code.com): line 1, column 7:
> PL/SQL: Statement ignored
> EXP-00083: The previous problem occurred when calling
> SYS.DBMS_REPCAT_RGT_EXP.schema_info_exp
> . exporting user history table
> . exporting default and system auditing options
> . exporting statistics
> Export terminated successfully with warnings.
>
> Many Thanks
> Denham
> --
> http://www.freelists.org/webpage/oracle-l
> --
> http://www.freelists.org/webpage/oracle-l
>
Cheers
__ ____ ____ ____ ____ ____ ______
Celebrate Yahoo! 's 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/
--
http://www.freelists.org/webpage/oracle-l