Optimizer Bug Fixes With Disabled Fix Control In 21c
(Doc ID 3000302.1)
Last updated on FEBRUARY 17, 2025
Applies to:
Oracle Database Cloud Exadata ServiceOracle Cloud Infrastructure - Exadata Cloud Service
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine)
Gen 2 Exadata Cloud at Customer
Oracle Database - Enterprise Edition - Version 21.1 and later
Information in this document applies to any platform.
Purpose
Purpose of this document is to maintain the list of Key Optimizer Bug fixes having fix control in disabled state starting 21.4 and above for every DBRU (Database Release Update) of 21c.
There are many optimizer bug fixes included into 21c base release as well as in every RU. Some of the Optimizer bug fixes (not all) are controlled by _FIX_CONTROL setting and are DISABLED by default in 21c when installed either through one-off backport or through RUs.
Example:
From 21c onwards those bug fixes having the fix control option tied to that are DISABLED by default to avoid any unforeseen issues for 21c Optimizer causing SQL regressions immediately after having applied the DBRU. The below document contains the list of Key SQL Performance related bug fixes having fix control in disabled state starting 21.4 and above for every RUs of 21c.
Scope
Scope is limited to SQL Performance or Wrong Results related bug fixes having fix control in disabled state that are most popular. Some of the below may have multiple fix control modifications or have a different fix number than the bug number that will be needed to enable that fix, reference the Fix Control Modifications column for details.
(Please note that this will not show all bugs that have fix controls in disabled state this list is for the most popular bug fixes.)
Details
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
| Purpose |
| Scope |
| Details |
| References |