RE: Export error
- From: "Spears, Brian" <BSpears@xxxxxxxxxxxxxxxxx>
- To: <pegramrg@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 7 Mar 2005 09:18:49 -0500
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
following errors:
EXP-00008: ORACLE error 6550 encountered ORA-06550: line 1, column13:
ORA-06550: line 1, column 7:
EXP-00083: The previous problem occurred when calling
SYS.DBMS_REPCAT_RGT_EXP.schema_info_exp
EXP-00008: ORACLE error 6550 encountered
ORA-06550: line 1, column 13:
ORA-06550: line 1, column 7:
EXP-00083: The previous problem occurred when calling
SYS.DBMS_REPCAT_RGT_EXP.schema_info_exp
Solution Description
--------------------
If you delete the Entry for DBMS_REPCAT_RGT_EXP in the exppkgact$ tables,
the errors do not occur.
Syntax:
SVRMGR> delete from sys.exppkgact$ where package =
2> 'DBMS_REPCAT_RGT_EXP' and schema= 'SYS';
1 row processed.
Verify this no longer shows in the table
SVRMGR> select * from exppkgact$;
Explanation
-----------
When you Run CATREPR.sql ( to remove replication), the Package you are
getting the error on should be removed, you can verify this by
Command:
grep -i DBMS_REPCAT_RGT_E*
catrepr.sql:DROP PACKAGE sys.dbms_repcat_rgt_exp
This is not getting dropped. So you will have to do it manually
to run an export without errors.
References
----------
[BUG:1049178] CANNOT EXPORT DATABASE AFTER RUNNING CATNOQUEUE.SQL
.
----------------------------------------------------------------------------
----
Copyright (c) 1995,2000 Oracle Corporation. All Rights Reserved. Legal
Notices and Terms of Use.
Note:114356.1
Subject:
Export Fails With ORA-29516 Aurora Assertion Failure EXP-8
Type:
PROBLEM
Status:
PUBLISHED
Content Type:
TEXT/PLAIN
Creation Date:
03-JUL-2000
Last Revision Date:
08-MAY-2001
Problem Description
-------------------
When performing an export on version on Oracle database version 8i, the
following errors are returned after exporting the synonyms:
Exp-00008: Oracle error 29516 encountered.
ORA-29516: Aurora assertion failure: Assertion failure at eox.c:187
Uncaught exception Root of all Java exceptions:
EXP-00000: Export terminated unsuccessfully
Solution Description
--------------------
1. First, run catexp as sys. Then retry the export. Often times this will
fix the problem and then export will run without error.
2. If running catexp as sys does not fix the errors, the problem may be one
of hitting a resource issue for the export, try increasing the
db_block_buffers and size of your rollback segments. Then try the
export
if it is still fails, try the following:
3. It appears that the errors relate to a bad or incomplete installation of
JAVAVM, which stands for java virtual machine. This is installed using
initjvm.sql. If using this, then verify with our Unix group whether or
not the installation of it was successful.
4. Check that LD_LIBRARY_PATH is pointing to the correct area. For example
if
you are running 64 bit software ensure that you are pointing to the 64
bit
libraries and not the 32 bit.
The ORA-29516 means that something failed in the JAVAVM when export tried to
call into it, probably to attempt to translate a synonym from short to long
form. It may be that there are cases where export decides to do this when
Java has not been loaded, in which case the error here might result. To
verify what is currently in your database please run the following queries:
select owner,synonym_name,table_owner,table_name from all_synonyms where
table_owner = 'DLC535' or owner = 'DLC535';
select count(*) from all_objects where object_type like 'JAVA%'
If the jvm was installed you should find about 8000 objects
If you do not intend on using this please deinstall it using the following
instructions:
Remove it by deinstalling it as SYS
- run rmjvm.sql located in your ORACLE_HOME/javavm/install directory.
The export should then run successfully.
References
----------
[BUG:1179670] ORA-6576 Can Occur Running rmjvm.sql
.|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
||||||||||||||
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 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>.
.
----------------------------------------------------------------------------
----
Copyright (c) 1995,2000 Oracle Corporation. All Rights Reserved. Legal
Notices and Terms of Use.
Note:1017276.102
Subject:
Oracle8i Export Fails on Synonym Export with EXP-00008 and ORA-00904
Type:
PROBLEM
Status:
PUBLISHED
Content Type:
TEXT/PLAIN
Creation Date:
28-AUG-1999
Last Revision Date:
11-FEB-2003
Problem Description:
====================
The following is being seen when exporting from Oracle 8.1.x
. exporting referential integrity constraints
. exporting synonyms
EXP-00008: ORACLE error 904 encountered
ORA-00904: invalid column name
EXP-00000: Export terminated unsuccessfully
Running "catexp.sql" does not alleviate the problem.
Problem Explanation:
====================
A synonym named "DBMS_JAVA" or "DBMS_JAVA_TEST" may exist without a
corresponding package.
Solution Explanation:
=====================
If Java is enabled, export uses DBMS_JAVA.LONGNAME in a query while
exporting synonyms. If the DBMS_JAVA or DBMS_JAVA_TEST package
has not been installed, this query will fail with and ORA-00904: "invalid
column name".
In 8.1.5, the Export utility tests if Java is enabled by looking for the
synonym "DBMS_JAVA"; if it exists, Oracle assumes Java is enabled; if it
doesn't, Oracle assumes Java is not enabled.
In 8.1.6, the Export utility tests if java is enabled by looking for java
class "/oracle/aurora/rdbms/DbmsJava"
Using STACKTRACE tracing will show the select statement using the "LONGNAME"
function
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)
,TABOWN,TABNODE, PUBLIC$, SYNOWN, SYNOWNID, SYNTIME
FROM SYS.EXU8SYN
WHERE SYNOWNID=:1
ORDER BY SYNTIME
Solution Description:
=====================
If Java is enabled, ensure that both DBMS_JAVA synonyms and packages are
created and valid. The following script can be used to
create the required packages, "$ORACLE_HOME/javavm/install/initdbj.sql".
This will need to be run as internal.
If Java is disabled, run "$ORACLE_HOME/javavm/install/rmjvm.sql" to remove
java related objects. Do not just drop the synonym.
Search Words:
=============
export, import, utilities, Oracle8i, 8i, synonym, EXP-8, ORA-904
References:
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Robert Pegram
Sent: Monday, March 07, 2005 8:29 AM
To: oracle-l@xxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxx> 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@xxxxxxxxxx]
> Sent: Friday, March 04, 2005 6:33 AM
> To: oracle-l@xxxxxxxxxxxxx
> 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: line 1, column 13:
> PLS-00201: identifier 'SYS.DBMS_REPCAT_RGT_EXP' must be declared
> ORA-06550: 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: line 1, column 13:
> PLS-00201: identifier 'SYS.DBMS_REPCAT_RGT_EXP' must be declared
> ORA-06550: 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
> --
> //www.freelists.org/webpage/oracle-l
> --
> //www.freelists.org/webpage/oracle-l
>
Cheers
__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
