Chinaunix首页 | 论坛 | 博客
  • 博客访问: 698942
  • 博文数量: 147
  • 博客积分: 5347
  • 博客等级: 大校
  • 技术积分: 1453
  • 用 户 组: 普通用户
  • 注册时间: 2005-06-06 11:11
文章分类

全部博文(147)

文章存档

2014年(4)

2012年(9)

2011年(5)

2010年(28)

2009年(21)

2008年(29)

2007年(15)

2006年(17)

2005年(19)

我的朋友

分类: Oracle

2010-07-02 09:19:41

Ora-00600[Qkaconfindpriorpred:1] With Non-Default OPTIMIZER_INDEX_COST_ADJ [ID 759024.1]  

  修改时间 01-JAN-2009     类型 PROBLEM     状态 REVIEWED  

In this Document
  
  
  
  


Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.3 to 11.1.0.7
This problem can occur on any platform.

Symptoms

The following error may occur when using the non-default value for OPTIMIZER_INDEX_COST_ADJ(default 100):

ORA-00600: internal error code, arguments: [qkaconFindPriorPred:1], [], [], [], [], [], [], []


Cause

- ORA-600 [QKACONFINDPRIORPRED:1] WITH NON-DEFAULT OPTIMIZER_INDEX_COST_ADJ

that was closed as a duplicate to

- Poor CONNECT BY performance with complex views
"CONNECTBY QPERF Details: A CONNECT BY query on a complex view that uses the filtering mode may get
a poor execution plan that shows that the CONNECT BY predicates are not used in the view.
Workaround: Sometimes forcing the use of the no-filtering mode can provide an improvement in
performance."

Solution

1- _optimizer_connect_by_cost_based=false
This is to switch off cost-based transformation for connect by clause, setting the parameter system wide may cause some performance degradation.
to set at session level:
alter session set "_optimizer_connect_by_cost_based"=false;

2-Use the default value for OPTIMIZER_INDEX_COST_ADJ(100)

3-Apply , if the patch is not available for your platform please log a SR with Oracle Support.

The problem is fixed in the 11.1.0.7 patchset.

References

- SLOW QUERY WITH INCREASED NUMBER OF ROWS
- ORA-00600 [QKACONFINDPRIORPRED:1] WITH NON-DEFAULT OPTIMIZER_INDEX_COST_ADJ
阅读(950) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~