Optimizer Bug Fixes With Disabled Fix Control In 18c
(Doc ID 3000301.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterGen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database - Enterprise Edition - Version 18.3.0.0.0 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 18.3 and above for every DBRU (Database Release Update) of 18c.
There are many optimizer bug fixes included into 18c 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 18c when installed either through one-off backport or through RUs.
Example:
From 18c onwards those bug fixes having the fix control option tied to that are DISABLED by default to avoid any unforeseen issues for 18c Optimizer causing SQL regressions immediately after having applied the DBRU. The below document contains the list of Key Optimizer Bug fixes having fix control in disabled state starting 18.3 and above for every RUs of 18c.
Scope
Scope is limited to only Optimizer bug fixes having fix control in disabled state.
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 |