Oracle DBMS_FIX_CONTROL_PERSISTENCE Version 126.96.36.199
Morgan's Library Page Header
prepared for the release of Oracle Database
18c ... the first autonomous database? We are here at the Library. It is
time for DBAs to stop fighting robots with their fingers and losing ...
time to start using our intelligence and winning.
This package is created to persist fix control environment and make use of the same to manage fixes which were enabled prior to applying bundle patch but got disabled as part of bundle patch.
Background: Fixes having fix_control are included in exadata bundle patches starting 188.8.131.52 BP12, these fixes are disabled by default and explicitly enabled by the customer using the dbms_optim_bundle package (note that dbms_optim_bundle does not exist in 184.108.40.206).
Issue: Fix control state for bug fixes present in the DB environment prior to bundle patch apply is not persisted after bundle patch apply.
Modifies the modify_at_startup flag in the Fix-Control Persistence Table and then triggers an 'alter system' command to restore the required fix_controls in current environment with scope=memory.
The user of this proc is the post-install script of each subsequent bundle patch which has fixes having fix_controls.
startbundleId IN VARCHAR2,
endbundleId IN VARCHAR2,
series IN VARCHAR2,
patchMode IN VARCHAR2,
patchId IN VARCHAR2,
patchUID IN VARCHAR2);
Syncronizes the current fix-control environment and the fix-control persistence table. Also triggers an 'alter system' command to restore required fix_controls in the current environment with scope=memory.
This is done during each database startup. User of this Procedure is qksbgnfy() which does this after
the database is successfully opened.
dbms_fix_control_persistence.sync_fcpt_alter_fc(performAlter IN NUMBER);
SELECT fix_control, ofe