EXP-00008: ORACLE error 1403 encountered

最新推荐文章于 2021-04-08 22:35:46 发布

whz110

最新推荐文章于 2021-04-08 22:35:46 发布

阅读量519

点赞数

分类专栏： Oracle 文章标签：数据库

本文链接：https://blog.csdn.net/whz110/article/details/84473814

版权

Oracle 专栏收录该内容

119 篇文章 1 订阅

订阅专栏

本文解决Oracle导出时遇到的ORA-01403错误，该问题通常由运行catnoqueue.sql脚本导致，而未先删除数据库中的所有队列表。通过检查现有队列表并删除它们，再清理SYS.EXPACT$表中相关记录，最终实现成功导出。

摘要由CSDN通过智能技术生成

导出数据报下面的错误：

. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
EXP-00008: ORACLE error 1403 encountered
ORA-01403: no data found
ORA-06512: at "SYS.DBMS_AQ_IMPORT_INTERNAL", line 77
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_SYS_SQL", line 781
ORA-06512: at "SYS.DBMS_SQL", line 316
ORA-06512: at "SYS.DBMS_EXPORT_EXTENSION", line 82
ORA-06512: at "SYS.

查看metalink，解决办法如下：

Problem Explanation:

====================
This can be caused by running the script 'catnoqueue.sql' without first dropping all the queue tables in the database.

Solution Explanation
====================
The script 'catnoqueue.sql' has been run which drops the tables DEF$AQCALL and DEF$AQERROR. The corresponding rows in SYS.EXPACT$ are not dropped. Prior to running 'catnoqueue.sql', check for and drop any existing queue tables. To ascertain the existence of any queue tables, from SQL*Plus issue the following command to list all queue tables:

SELECT * FROM dba_queue_tables

To drop the queue tables, from SQL*Plus issue the following command: execute dbms_aqadm.drop_queue_table('<queue table name>')

Solution Description:
=====================
If 'catnoqueue.sql' has already been run, then you need to delete from SYS.EXPACT$ rows for non-existent queue tables. The following steps will allow a full export to run successfully:

All rows from the SYS.EXPACT$ table for the function package DBMS_AQ_IMPORT_INTERNAL need to be deleted.

1. Login into Server Manager as INTERNAL or SYS; or, login into SQL*Plus as SYS

2. Enter the following SQL command:

DELETE FROM SYS.EXPACT$
WHERE FUNC_PACKAGE = 'DBMS_AQ_IMPORT_INTERNAL';

After the statement issue a 'commit' so the statement can take effect.

3. Exit Server Manager or SQL*Plus.
4. Now you should be able to do a full database export.

这样问题得到圆满的解决。

Sun 上面oracle文件的限制:metalink note 62409.1

Filesize Limits For Oracle RDBMS 32-bit On Solaris (SPARC) Servers

~~~~~~~~~~~~~~~~~~~~~~~
SOLARIS 2.6 / 2.7 / 2.8
~~~~~~~~~~~~~~~~~~~~~~~
              File     Exp/   Loader
Oracle      System Raw   Imp** see **   UTL_FILE Notes (see below)
=========================================================================
10.1.0.1.0                                          There is no 32 Bit Oracle
9.2.0.1       >4Gb >=2Gb >=2Gb   >=2Gb   >=2Gb
8.1.7.0       >4Gb >=2Gb >=2Gb   >=2Gb   >=2Gb
8.1.6.0       >4Gb >=2Gb >=2Gb   >=2Gb   >=2Gb
8.1.5.0 32Bit >4Gb >=2Gb   <2Gb   <2Gb    <2Gb
8.1.5.0 64Bit >4Gb >=2Gb   <2Gb   <2Gb    <2Gb      Exp is a 32bit executable