DBMS_SHARED_POOL.PURGE Does Not Purge the Cursors Completely
(Doc ID 2214994.1)
Last updated on JANUARY 10, 2025
Applies to:
Oracle Cloud Infrastructure - Database Service - Version N/A and laterOracle Database Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- DBMS_SHARED_POOL.PURGE API does not purge the cursors completely
- Oracle still keeps the reference of the purged cursors in shared pool and the same will get reused
- The CURSOR_SHARING=FORCE is set but literal replacement does not happen for the same literal for which the cursor has been purged using DBMS_SHARED_POOL.PURGE API
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 |
| Cause |
| Solution |
| References |