ORA-7445 [kditpin()+20] Error Occurs Along With ORA-1652 When Running Select Statement with Order By

(Doc ID 1949027.1)

Last updated on DECEMBER 22, 2014

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Information in this document applies to any platform.

Symptoms

When running SELECT statement with ORDER BY clause, ORA-7445 [kditpin()+20] error occurs along with ORA-1652

SQL statement:

SELECT A.INSTTSN,
  A.INSTTID,
  A.INSTTNM, NVL(NEW_ADRES,A.ADRES) ADRES ,
  A.UPPERINSTTSN,
  A.INSTTSTTUS,
  A.BESTINSTTSN,
  A.INSTTTYID
 FROM TB_INSTTINFO A
 WHERE INSTTSTTUS = 'Y'
  AND INSTTTYID = :1
  AND UPPERINSTTSN <> 0
  AND INSTTNM LIKE '%' || :2 || '%'
 START WITH A.UPPERINSTTSN=0
 CONNECT BY PRIOR A.INSTTSN = A.UPPERINSTTSN
 ORDER SIBLINGS BY A.INSTTSORTORDR, A.INSTTNM
                                                                                            
ORA-1652: unable to extend temp segment by 128 in tablespace                 COMM0_TEMP
Errors in file .../diag/rdbms/sid/SID/trace/SID_ora_9016.trc  (incident=388914):
ORA-07445: exception encountered: core dump [kditpin()+20] [SIGSEGV] [ADDR:0x0] [PC:0x103E4B674] [Address not mapped to object] []
Incident details in: .../diag/rdbms/sid/SID/incident/incdir_388914/SID_ora_9016_i388914.trc


The call stack in the incident trace file written by the error contains the following functions:

kditpin <- kgbtder <- kgbtdes <- stsTmpIxDestroy <- stsend <- sorcls <- qercbiFetch <- qerflFetchOutside

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms