How To Identify High Number Of Child Cursors Leading To ORA-600 
Last updated on NOVEMBER 28, 2016
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 and later
Information in this document applies to any platform.
***Checked for relevance on 07-Oct-2014***
This article provides an approach for addressing non-sharable cursors that may fail with an error ORA-600 .
The purpose of this article is to assist Support engineers and Customers to identify a high number of non-sharable child cursors potentially causing ORA-600 .
This article can also be used for non-sharable child cursors potentially leading to an ORA-4031.
The article provides SQL to query dictionary views V$SQLAREA and V$SQL_SHARED_CURSOR to get the reason code for why a cursor is not shared. Based on the reason codes, a list of known defects related to non-sharable cursors are listed with links towards articles with more details about fixed releases and known workarounds
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