Different Plan Hash Value due to Migration from Solaris to Linux Causing SQL Performance Analyzer to Report Incorrect Plan Changes
(Doc ID 2065831.1)
Last updated on NOVEMBER 26, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.5 and laterOracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- The SQL ID and explain plan remains the same but the plan hash value changes when changing the platform
- This can cause SQL Performance Analyzer (SPA) to report incorrect plan changes due to wrong plan hash value calculation
- Here is a following example after migrating from Sun Soloris to Linux showing different hash value:
Changes
Moved from one platform to another.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |