My Oracle Support Banner

ORA-600 [Sorgetqb_1] With Connect By Prior Clause (Doc ID 415648.1)

Last updated on APRIL 06, 2020

Applies to:

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


NOTE: The document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered
with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Symptoms

1. ORA-600[sorgetqb_1] when running a request that has the clause 'connect by prior...'

Example :

Current SQL statement for this session:
select sys_connect_by_path(lst, :"SYS_B_0") as path from
(select t1.lst, t1.list from listlists t1, lists t2 where t1.list=t2.id)
where list=:p1 connect by prior list=lst start with lst=:p2

2. Call Stack Trace from the trace file:

ksedst ksedmp ksfdmp kgerinv kgeasnmierr sorgetqb qercbiPFetch qersoFetch qerjotFetch qerjotFetch qercbiFilterData qercbiFetch qerflFetchOutside

3. This problem is reproducible when using:

OPTIMIZER_MODE = first_rows, first_rows_n

Changes

 NONE

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.