How To Identify High Number Of Child Cursors Leading To ORA-600 [17059]
(Doc ID 1213715.1)
Last updated on SEPTEMBER 01, 2023
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterOracle Database Backup Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 8.1.7.0 and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data.
Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Goal
This article provides an approach for addressing non-sharable cursors that may fail with an error ORA-600 [17059].
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 [17059].
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
Solution
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
| Goal |
| Solution |
| Query for 10.2: |
| Query for 11.1: |
| Query for 11.2: |
| Example output: |
| Conclusions and Summary of bugs due to reason code: |
| References |