After 12c DB Upgrade, SPM Baseline Not Used and Fails to Reproduce at Reparse Time
(Doc ID 2377190.1)
Last updated on FEBRUARY 03, 2019
Oracle Database - Enterprise Edition - Version 188.8.131.52 and later Information in this document applies to any platform.
After upgrading baseline from 184.108.40.206 to 220.127.116.11, SELECT with a fixed baseline started using a much slower plan that was not in SPM
After statistics gathering, new plan was generated because the fixed one was failing at re-parse:
SPM: statement found in SMB SPM: re-parsing to generate selected accepted plan, planId = 2885638348 SPM: finding a match for the generated plan, planId = 3122775218 SPM: failed to reproduce selected accepted plan on re-parse, planId = 3122775218 <<<<<<<< SPM: failed to reproduce the plan using the following info: SPM: generated non-matching plan: SPM: re-parsing again to produce best-cost plan SPM: statement found in SMB SPM: re-parsing to generate cost-based plan, sig = 9107058701240182256 SPM: finding a match for the generated plan, planId = 4180201812 SPM: re-parsed again to produce a best-cost plan, planId = 4180201812
Upgrade from 18.104.22.168 to 22.214.171.124.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!