ITPub博客

首页 > Linux操作系统 > Linux操作系统 > 遭遇ORA-00600 [kokle_lob2lob13:input mismatch]

遭遇ORA-00600 [kokle_lob2lob13:input mismatch]

原创 Linux操作系统 作者:NinGoo 时间:2019-07-16 20:15:02 0 删除 编辑

版本:

SYS@ning>select * from v$version;

BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Prod
PL/SQL Release 10.2.0.3.0 - Production
CORE 10.2.0.3.0 Production
TNS for 32-bit Windows: Version 10.2.0.3.0 - Production
NLSRTL Version 10.2.0.3.0 - Production

场景:

执行set autotrace on以后,在生成执行计划的部分报错:ORA-00600: internal error code, arguments: [kokle_lob2lob13:input mismatch], [1], [], [], [], [], [], []

使用alter session set sql_trace=true得到的trace文件中,导致错误产生的语句为:

ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [kokle_lob2lob13:input mismatch], [1], [], [], [], [], [], []
Current SQL statement for this session:
SELECT /*+ opt_param('parallel_execution_enabled', 'false') */
/* EXEC_FROM_DBMS_XPLAN */ id, position, depth, operation, options, object_name, cardinality, bytes, temp_space, cost, io_cost, cpu_cost , time, partition_start, partition_stop, object_node, other_tag, distribution, projection, access_predicates, filter_predicates , other, qblock_name, object_alias, nvl(other_xml, remarks), null, null, null, null, null, null, null,
null, null, null, null, null,
null, null, null, null from PLAN_TABLE where plan_id = (select max(plan_id)
from PLAN_TABLE where id=0 and statement_id = :stmt_id)
order by id


查metalink,该错误相关的文章有3篇,都是被报告为bug的:

  • Bug No.5370758
  • Bug No.5259008
  • Bug No.4292049

其中5259008,5370758都提到另外一个bug(Bug No.5135557),但是5135557的文档无法打开。不知道是我的帐号没权限看还是怎么的,有能看到该文章的朋友,请share一份给我,谢谢^_^

Bug 5135557.cannot be displayed. Possible reasons are:

  • The bug is not classified as publicly accessible ("non-public").
  • The bug is filed under a product for which you have no license. To view your product licenses go in your User profile and select the Show License option.
  • The bug was filed before June 1996. Only bugs that were opened after this date are accessible on this server.
  • The bug number does not exist (it was referenced incorrectly).

If you still have questions about why you weren't able to access this bug number, please use the Feedback button at the bottom of the left-hand menu bar.

上述bug报告中都没有给出应对策略,并且sqlplus重新登录后,该错误消失。Bug报告中有说该错误可能重复出现,记录一下,以后再观察。

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/193161/viewspace-50342/,如需转载,请注明出处,否则将追究法律责任。

下一篇: Oracle常用dump命令
请登录后发表评论 登录
全部评论

注册时间:2004-12-07

  • 博文量
    200
  • 访问量
    132092