执行imp命令，导入正式库数据备份时，执行到最后报出如下错误，数据恢复停止；
imp-00017:由于ORACLE的600错误，以下的语句失败
"ALTER PROCEDURE "INV_PRICE_ADJUST_SP" COMPILE REUSE SETTINGS TIMESTAMP '200"
"9-12-21:16:38:08'"
IMP-00003:遇到ORACLE错误600
ORA-00600:内部错误代码，参数：【16201】，【】，【】，【】，【】，【】，【】请高手指教如何解决此问题
imp-00017:由于ORACLE的600错误，以下的语句失败
"ALTER PROCEDURE "INV_PRICE_ADJUST_SP" COMPILE REUSE SETTINGS TIMESTAMP '200"
"9-12-21:16:38:08'"
IMP-00003:遇到ORACLE错误600
ORA-00600:内部错误代码，参数：【16201】，【】，【】，【】，【】，【】，【】请高手指教如何解决此问题
像这样的东东，很可能是BUG，大部分不是DBA能搞掂的。
"ALTER PROCEDURE "INV_PRICE_ADJUST_SP" COMPILE REUSE SETTINGS TIMESTAMP '200"这条语句过不去，在原来的库检查下这个存储过程，并且看下可还有其他的错误了.. 还有导出dmp时没有报什么错吧？ ------------------------------------------------------------------------------
Blog： http://blog.csdn.net/tianlesoftware
网上资源： http://tianlesoftware.download.csdn.net
相关视频：http://blog.csdn.net/tianlesoftware/archive/2009/11/27/4886500.aspx
Q Q 群：62697716
可以先忽略这个对象，同时检查一下alert.log文件看看有什么更多的错误信息没有
修改时间 16-APR-2009 类型 REFERENCE 状态 PUBLISHED
Note: For additional ORA-600 related information please read Note:146580.1PURPOSE:
This article discusses the internal error "ORA-600 [16201]", what
it means and possible actions. The information here is only applicable
to the versions listed and is provided only for guidance.ERROR:
ORA-600 [16201]VERSIONS:
versions 7.0 to 10.1DESCRIPTION: The exception is caused when there is an entry in obj$ for which
there is no corresponding entry in procedure$. This will relate to a object type of Trigger, Procedure, Function or
Package.FUNCTIONALITY:
SQL Library managerIMPACT:
PROCESS FAILURE
POSSIBLE DICTIONARY INCONSISTENCYSUGGESTIONS: If the Known Issues section below does not help in terms of identifying
a solution, please submit the trace files and alert.log to Oracle Support
Services for further analysis. If the problem can be reproduced, please attempt to collect the trace
output from using Event 10046 (at level 4 or level 12) See the following Metalink article relating to this Event : Note:21154.1 "enable SQL statement tracing (including binds/waits)" This will help Oracle Support discover the object that is causing the error.
Known Issues: Bug# 2422726 See Note:2422726.8
OERI[16201] possible when RECOMPILING a WRAPPED PACKAGE
Fixed: 9.2.0.2, 10.1.0.2
Bug:1879479 "BUFFERS TO FETCH FROM SOURCE$/VARCHAR2(4000) NEED TO BE 4001 BYTES IN SIZE"
Release: 8.1.7.2 and below and 9.0.1.2 and below
Problem: Export of a wrapped package can result in a corrupt package being imported (IMP-3 ORA-4030 ORA-3113 ORA-7445 ORA-600[16201]).
Solution: in Oracle8i with 8.1.7.3 and higher; in Oracle9iR1 with 9.0.1.3 and higher
Workaround: no, see Note:165016.1 "Corrupt Packages When Export/Import Wrapper PL/SQL Code"
|||||||||||||||||||||Bug 1879479: BUFFERS TO FETCH FROM SOURCE$/VARCHAR2(4000) NEED TO BE 4001 BYTES IN SIZE --------------------------------------------------------------------------------
Bug 属性--------------------------------------------------------------------------------
类型 B - Defect 已在产品版本中修复 9.0.2
严重性 2 - Severe Loss of Service 产品版本 9.0.1
状态 80 - Development to Q/A 平台 453 - Sun Solaris SPARC (32-bit)
创建时间 12-Jul-2001 平台版本 -
更新时间 19-Dec-2005 基本 Bug -
数据库版本 9.0.1
影响平台 Generic
产品来源 Oracle
相关产品--------------------------------------------------------------------------------
产品线 Oracle Database Products 系列 Oracle Database
区域 Oracle Database 产品 5 - Oracle Server - Enterprise Edition
Hdr: 1879479 9.0.1 RDBMS 9.0.1 EXPORT PRODID-5 PORTID-453Abstract: BUFFERS TO FETCH FROM SOURCE$/VARCHAR2(4000) NEED TO BE 4001 BYTES IN SIZE*** 07/12/01 02:22 am ***MAX size of a varchar2 is 4000 bytes from V8 onwards but when fetchingas a SQLT_STR the value gets a null byte tacked onto the end. This meansthat when fetching from a column defined as the max size and the columnis full (i.e. contains 4000 bytes) then the buffer will overflow andreceive an error unless it is large enough to accommodate the extra byte.cf bug 1874468*** 07/12/01 02:22 am *** (CHG: Asg->NEW OWNER OWNER)*** 07/12/01 02:22 am *** (CHG: Confirmed Flag->Y)*** 07/12/01 09:30 am ****** 07/13/01 07:08 am ****** 07/16/01 04:22 am *** (CHG: Sta->80)*** 07/16/01 04:22 am *** (CHG: Fixed->9.0.2)*** 07/16/01 04:22 am ****** 10/08/01 12:47 pm ****** 10/08/01 12:47 pm ****** 10/11/01 02:50 am ****** 10/11/01 10:45 am ****** 10/11/01 11:10 am ****** 10/11/01 11:10 am ****** 10/31/01 03:25 am ****** 10/31/01 03:25 am ****** 10/31/01 07:24 am ****** 10/31/01 07:24 am ****** 11/01/01 09:49 pm ****** 11/01/01 09:50 pm ****** 11/05/01 09:26 am ****** 11/05/01 09:27 am ****** 11/07/01 10:44 pm ****** 11/07/01 10:44 pm ****** 11/14/01 02:15 pm ****** 11/23/01 09:45 am *** Export / Import of a wrapped package can result in a corrupt package being imported. The symptoms of this depend on exactly where in the package data the corruption occurs. This can produce a package which compiles but does not behave as expected, or can cause a dump on import, or a PLS error on compilation. *** 11/27/01 02:33 am ****** 11/27/01 02:33 am ****** 12/06/01 06:32 am ****** 12/06/01 06:32 am ****** 12/07/01 05:55 am ****** 12/07/01 11:19 am ****** 12/07/01 11:19 am ****** 01/11/02 02:25 am ****** 01/22/02 01:12 pm ****** 02/08/02 05:34 am ****** 02/28/02 10:55 am ****** 02/28/02 10:55 am ****** 03/05/02 11:40 am ****** 03/05/02 11:40 am ****** 06/13/02 05:31 pm ****** 06/13/02 05:33 pm ****** 06/18/02 02:51 pm ****** 06/18/02 02:57 pm ****** 07/11/02 06:55 am ****** 07/16/02 01:14 am ****** 09/10/02 11:43 am ****** 09/10/02 11:43 am ****** 09/19/02 02:12 am ****** 09/19/02 12:41 pm ****** 09/19/02 12:41 pm ****** 10/17/02 06:33 am ****** 10/17/02 06:33 am ****** 05/17/04 11:16 am ****** 05/17/04 11:27 am ****** 05/17/04 11:47 am ****** 05/17/04 11:48 am ****** 05/17/04 11:51 am ****** 05/17/04 01:22 pm ***
看有没有帮助