My Oracle Support Banner

ORA-600[kge.h:KGEENDFRAME error not handled] or ORA-600[17813] From a Job Process When Selecting From V$OPEN_CURSOR or Access To X$KGLLK is Seen in Plan Table (Doc ID 2732179.1)

Last updated on SEPTEMBER 10, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 to 19.9.0.0.0 [Release 12.2 to 19]
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Information in this document applies to any platform.

Symptoms

The error ORA-600[kge.h:KGEENDFRAME error not handled] is raised during the execution of a job process.

The error usually is raised by Data Pump Master (DM) or Worker Process (DW), but it might be seen for a non-Data Pump job process as well.

For Data Pump processes, the internal error is raised from package body SYS.KUPW$WORKER.CHECK_FOR_OPEN_CURSORS:

----- PL/SQL Call Stack -----
 object      line  object
 handle    number  name
000001C8FE06FE30     21737  package body SYS.KUPM$MCP.CHECK_FOR_OPEN_CURSORS
000001C8FE06FE30     13593  package body SYS.KUPM$MCP.SCHEDULE_WORK
000001C8FE06FE30      9426  package body SYS.KUPM$MCP.GET_WORK
000001C8FE06FE30      1777  package body SYS.KUPM$MCP.DISPATCH

during a select from v$open_cursor. The select might be similar to those below:

SELECT COUNT(*) FROM v$open_cursor WHERE sid = SYS_CONTEXT(:"SYS_B_0", :"SYS_B_1") AND cursor_type = :"SYS_B_2";
SELECT COUNT(*) FROM v$open_cursor WHERE sid = SYS_CONTEXT('USERENV', 'SID') AND cursor_type = 'OPEN_PLSQL';


The call stack for this error looks like:

... kglic_cbk <- kglic0 <- kqlftl <- qerfxFetch <- qergsFetch <- opifch2 <- opiefn0 <- opipls <- opiodr <- rpidrus <- rpidru <- rpiswu2 <- rpidrv ...


For all cases ( e.g for a Data Pump process or any job process), the plan table shows access on X$KGLLK fixed table:

============
Plan Table
============

-------------------------------------+-----------------------------------+
| Id  | Operation          | Name    | Rows  | Bytes | Cost  | Time      |
-------------------------------------+-----------------------------------+
| 0   | SELECT STATEMENT   |         |       |       |     1 |           |
| 1   |  SORT AGGREGATE    |         |     1 |    42 |       |           |
| 2   |   FIXED TABLE FULL | X$KGLLK |     1 |    42 |     0 |           |
-------------------------------------+-----------------------------------+

- OR -
....
| 127 |       FIXED TABLE FULL                                | X$KGLLK               |     5 |   120 |     0 |           |
| 128 |      BUFFER SORT                                      |                       |    63 |   504 |     2 |  00:00:01 |
| 129 |       FIXED TABLE FULL                                | X$KSLWT               |    63 |   504 |     0 |           |
| 130 |     FIXED TABLE FIXED INDEX                           | X$KSUSE (ind:1)       |     1 |    25 |     0 |           |
| 131 |    FIXED TABLE FIXED INDEX                            | X$KSLED (ind:2)       |     1 |     4 |     0 |           |
....

Changes

 

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
Changes
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.