Which has the higher priority in your organization: Deploying a new database or securing the ones you already have?
Looking for a website, and resources, dedicated solely to securing Oracle databases? Check out DBSecWorx.
This package is created to manage (enable/disable) optimizer fixes provided as part of PSU/bundles. Optimizer fixes are those provided as part of bundle which has a fix-control and can possibly cause a plan change.
This package has existed in some previous versions of the database, was dropped again most recently from 19.3 which is why it was again dropped from the Library.
Oracle reintroduced it with 19.4 which the Library did not research so, from our perspective, it is "new" again in 20c.
Be sure to read: MOS Note:2147007.1 – Automatic Fix Control Persistence (FCP) for Database Proactive Bundle Patch tells you more about it.
In brief, it deals with the – off by default – behavior changing optimizer fixes shipped in Bundle Patches and Update which Mike Dietrich discussed in his July 25, 2017 blog post:
TYPE dbms_optim_bugvalobtype ...
TYPE dbms_optim_fctabtype ...
PRAGMA SUPPLEMENTAL_LOG_DATA(default, NONE);
Owned by SYS with no privileges granted
ENABLE_OPTIM_FIXES (new 20c)
Enables and disables fixes
action IN VARCHAR2 DEFAULT 'OFF',
scope IN VARCHAR2 DEFAULT 'MEMORY',
current_setting_precedence IN VARCHAR2 DEFAULT 'YES);