koko的oracle杂货铺

Applies to:

Oracle Server Enterprise Edition - Version: 10.2.0.2 to 10.2.0.3

This problem can occur on any platform.

Oracle Server - Enterprise Edition - Version: 10.2.0.2 to 10.2.0.3

Symptoms

In the alert log is reported the following internal error:
    ORA-00600: internal error code, arguments: [qkabix], [0], [], [], [], [], [], []

The error is reported running a Select statement.

The call stack looks like:

   qkabix qkaix qkatab qkajoi qkaqkn qkadrv opitca kksFullTypeCheck rpiswu2 kksSetBindType kksfbc
   kkspfda kpodny kpoal8

Cause

The problem could be related to a CBO ( Cost Based Optimizer ) issue when a query uses a bitmap access paths for b-tree indexes.

It is reported in Bug 5945798 but not confirmed.

Solution

One possible workaround to avoid the error is to disable the optimizer to produce bitmap plans for B-Tree indexes even if
there is no bitmap index anywhere in sight:

- at session level
     sql> alter session set "_b_tree_bitmap_plans"=false;

- or at system level 
     sql> alter system set "_b_tree_bitmap_plans"=false;

- or in the init.ora
     _b_tree_bitmap_plans = false

 

 有关 BITMAP CONVERSION TO ROWIDS

 

Answer: The "bitmap
conversion to ROWIDS" execution plan step was generally
introduced in Oracle 9i when the default for _b_tree_bitmap_plans
changed from "false" to "true".  The "BITMAP CONVERSION (TO
ROWIDS)" plan is not always an optimal step when converting from
b-tree indexes, and it can be very inefficient access plan in
some cases.

 

Bitmap conversion to ROWIDS does
not require bitmap indexes, and it's sometimes found in cases of
SQL with complex WHERE clause conditions.

 

The bitmap conversion to rowids is
sometimes seen with star transformations (by setting
star_transformation_enabled = true).  You can also
turn-off bitmap conversion to ROWIDS in your init.ora by
re-setting this hidden parm:

 

_b_tree_bitmap_plans=false

 

You can also turn-off bitmap
conversion at the session level, for testing:

 

alter session set
"_b_tree_bitmap_plans"=false

 

As always, notify Oracle technical
support before employing any hidden parameters, as they can make
your database unsupported.