Modifying CURSOR_SHARING Parameter In One Pluggable Database Influences Other PDBs
(Doc ID 2258739.1)
Last updated on MARCH 18, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterOracle 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.
Symptoms
- Setting CURSOR_SHARING = FORCE parameter in one of the pluggable databases in an multitenant environment influences other PDBs as well.
- The CDB does not have the CURSOR_SHARING set to FORCE, it is set to default as EXACT.
- This weird behavior of CURSOR_SHARING mechanism among the PDBs is creating performance issues among the PDBs.
Changes
Upgraded the database to 12c with CDB enabled.
Changed the parameter CURSOR_SHARING to FORCE in one PDB only.
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 |
| Changes |
| Cause |
| Solution |
| References |