My Oracle Support Banner

ORA-600 [kdibc3position] While Executing Specific Query (Doc ID 1997134.1)

Last updated on FEBRUARY 20, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.2.0 to 11.2.0.2.0 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

1. Following error is being encountered when specific query is executed:

ORA-00600: internal error code, arguments: [kdibc3position], [], [], [], [], [], [], [], [], [], [], []


2. The plan table in trace file shows TABLE ACCESS BY LOCAL INDEX ROWID on <TABLE_NAME> table and BITMAP CONVERSION TO ROWIDS:

...
| 31 |          PARTITION LIST ALL                 |                            | 1674K |  554M |  163K | 00:06:35 |      |      |     | 1 | 3 |
| 32 |           TABLE ACCESS BY LOCAL INDEX ROWID | <TABLE_NAME>               | 1674K |  554M |  163K | 00:06:35 |      |      |     | 1 | 3 |   <---
| 33 |            BITMAP CONVERSION TO ROWIDS      |                            |       |       |       |          |      |      |     |   |   |
| 34 |             BITMAP AND                      |                            |       |       |       |          |      |      |     |   |   |
| 35 |              BITMAP MINUS                   |                            |       |       |       |          |      |      |     |   |   |
| 36 |               BITMAP MERGE                  |                            |       |       |       |          |      |      |     |   |   |
| 37 |                BITMAP KEY ITERATION         |                            |       |       |       |          |      |      |     |   |   |
| 38 |                 BUFFER SORT                 |                            |       |       |       |          |      |      |     |   |   |
| 39 |                  TABLE ACCESS FULL          | <TABLE_NAME1>              |   10K |  253K |   319 | 00:00:01 |      |      |     |   |   |
| 40 |                 BITMAP INDEX RANGE SCAN     | <INDEX_NAME1>              |       |       |       |          |      |      |     | 1 | 3 |
| 41 |               BITMAP INDEX SINGLE VALUE     | <INDEX_NAME2>              |       |       |       |          |      |      |     | 1 | 3 |
| 42 |              BITMAP INDEX SINGLE VALUE      | <INDEX_NAME3>              |       |       |       |          |      |      |     | 1 | 3 |
| 43 |              BITMAP MERGE                   |                            |       |       |       |          |      |      |     |   |   |
| 44 |               BITMAP KEY ITERATION          |                            |       |       |       |          |      |      |     |   |   |
| 45 |                BUFFER SORT                  |                            |       |       |       |          |      |      |     |   |   |
| 46 |                 INDEX FAST FULL SCAN        | <INDEX_NAME4>              |   12K |  160K |     4 | 00:00:01 |      |      |     |   |   |
| 47 |                BITMAP INDEX RANGE SCAN      | <INDEX_NAME5>              |       |       |       |          |      |      |     | 1 | 3 |
| 48 | BUFFER SORT                                 |                            |       |       |       |          |:Q1007| PCWC |     |   |   |
| 49 |  PX RECEIVE                                 |                            | 5052K | 2047M |   38K | 00:01:18 |:Q1007| PCWP |     |   |   |
| 50 |   PX SEND HASH                              | :TQ10004                   | 5052K | 2047M |   38K | 00:01:18 |      | S->P |HASH |   |   |
| 51 |    TABLE ACCESS FULL                        | <TABLE_NAME6>              | 5052K | 2047M |   38K | 00:01:18 |      |      |     |   |   |
...


3. The call stack in the trace file shows functions like:

... kdibc3position qerbmStrmMi qerbmFetch kdibr1sf qerbaFndOl qerbaStrmAnd qerbaFetch kdibr1sf qerbtFetch qertbFetchByRowID qergiFetch rwsfcd qerhjFetch rwsfcd qertqoFetch qerpx_resume qerpxFetch opifch2 kpoal8 opiodr ...


4. Disabling constant predicate elimination by setting event 10078, level 1 did not help.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.