My Oracle Support Banner

ORA-600 [17114] Or ORA-600 [17125] Followed By An Instance Crash (Doc ID 730726.1)

Last updated on JANUARY 29, 2022

Applies to:

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


- Alert log shows ORA-600 [17xxx] and heap corruption errors similar to the following:

ORA-00600: internal error code, arguments: [17114], [0xC000000237BF43C8], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [17125], [0x000000000], [], [],

Please note that the errors can also occur due to other reasons.

- Call stack trace is similar to:

ksfdmp <- kgherror <- kghfrmrg <- kghfre <- kghfrh_internal <- kghfrh <- kglobf0 <- kglhpd_internal

- or -

ksedst <- ksedmp <- ksfdmp <- kgeriv <- kgesiv <- kgesic1 <- kgherror <- kghichk <- kghhchk <- kghfrh_internal <- kghfrh <- kglobf0 <- kgllkdl

- Parameter CURSOR_SHARING is set to SIMILAR or FORCE
And if running on a release which has the fix for <Bug:5055175>, then it increases the odds of it being this issue.

-  If the heap corruption trace files show kksl*** functions in the call stack, that also would be an indication.

- This problem (due to it's nature) will likely require SQL statements having very large number of bind variables. Such statements may not be visible in trace files but if the application does have such statements, then that is another reason to suspect this.




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

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