Things to Consider for 184.108.40.206 to Avoid Problems with SQL Plan Management (SPM)
(Doc ID 2035898.1)
Last updated on DECEMBER 05, 2019
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 12.1]
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
The purpose of this note is to publish some recommended fixes in hopes of avoiding problems associated with performance and failure to reproduce desired plans when using SQL Plan Management in 22.214.171.124.x.
This Document concerns itself with highly desirable patches in 126.96.36.199 that address performance and reproduction problems when using the SQL Plan Management feature.
NOTE: Some reproduction bugs cause the creation of defective plans, so applying these patches before capturing plans from the cursor cache is necessary to avoid some issues. In particular, when using SPM to avoid plan regressions during an upgrade, the appropriate set of patches should be applied not only to the post-upgrade environment, but also the pre-upgrade environment prior to capturing plans. See the following for patches for other Oracle releases:
<Document 2034706.1> Things to Consider for 188.8.131.52 to Avoid Problems with SQL Plan Management (SPM)
<Document 2035897.1> Things to Consider When Upgrading From 184.108.40.206 to Avoid Problems with SQL Plan Management (SPM)
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
|Patches relevant for all platforms|
|For no PSU and PSUs up through 160719|
|For PSUs 161018 and above|