Underscore Parameters Set In Pluggable Databases Are Not Persistent After Restart
(Doc ID 2335758.1)
Last updated on MARCH 18, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- Underscore parameters set in pluggable databases are not persistent after the database restart.
Example:
Parameter _optimizer_use_feedback=FALSE is applied to a single PDB within a 12c container:
SQL> alter session set container = PDB1;
SQL> alter system set "_optimizer_use_feedback"=FALSE scope=BOTH; - After restart the parameter is no longer applied, the following commands do not return anything:
SQL> show parameter "_optimizer_use_feedback"
SQL> show parameter _optimizer_use_feedback
The parameter _optimizer_use_feedback=FALSE applied on 12c PDB not persistent after restart.
Similarly, there are other underscore (Optimizer related and other) parameters that are set but not persistent after database restart.
As the parameters are not set persistently in PDBs, there are suboptimal execution plan for the SQL statements in PDBs upon database restart.
Changes
Upgrade to 12c multitenant environment (CDB/PDB).
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 |