My Oracle Support Banner

Automatic Fix Control Persistence (FCP) for Database Proactive Bundle Patch (Doc ID 2147007.1)

Last updated on APRIL 13, 2020

Applies to:

Oracle Database - Enterprise Edition - Version and later
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 Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.


In order to support a more flexible and responsive strategy for the RDBMS software release process, Oracle Development has implemented a patch packaging technique that supports the inclusion of module bug fixes (which cause an execution plan change) in a disabled state. This technique was implemented in the April 2017 DB Proactive Bundle Patch (BP) for RDBMS Prior to April 2017, no code module bug fixes that could have resulted in an execution plan change were considered for inclusion into BPs.

This document explains the SQL commands that are available to manage these "installed but disabled" module bug fixes (which cause an execution plan change), and the new 'Automatic Fix Control Persistence' framework (needed only in 12.1.0.X) that ensures that enabled fixes are preserved during subsequent DB Proactive BP application.


This document is intended for DBA's that are responsible for RDBMS software patching.


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
 Managing "installed but disabled" module bug fixes
 The new 'Automatic Fix Control Persistence' framework.
 Fixes with Fix Control starting RDBMS version 12.2 and higher
 Appendix A: Execution plan related bugs inclusion list

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.