SQL Profile on an Active Data Guard Standby is not the same as on the primary database
(Doc ID 1264838.1)
Last updated on JANUARY 29, 2022
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 to 126.96.36.199.0 [Release 11.1 to 11.2]
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
After following best practices for tuning read-only queries that execute on an Active Data Guard standby database, it is observed that the active standby is using different execution plans than those used on the primary database. This conflicts with the fact that an Active Data Guard standby database is an exact replica of the primary database in all regards. It uses the same optimizer statistics generated by its primary database, including system statistics. It also uses the same SQL plan baselines and SQL profiles used by the primary database.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!