Inconsistent Session Parameters After Close/Open PDB
Last updated on SEPTEMBER 01, 2017
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Information in this document applies to any platform.
***Checked for relevance on 01-Sep-2017***
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.
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