Inconsistent Session Parameters After Close/Open PDB
(Doc ID 2092746.1)
Last updated on FEBRUARY 03, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.
When set an instance parameter with scope=memory in a PDB, and then close and re-open the PDB the value is the same with the one set before close.
The expectation is that that parameter be reset to default because the PDB was re-opened, so the scope=memory should be aged out.
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 |