A SQL Profile Is Not Consistently Fixing a Performance Problem When VPD Is In Use
(Doc ID 1440205.1)
Last updated on MAY 19, 2020
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata 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.
A SQL Profile created to fix performance problems works inconsistently on a query---sometimes producing a desirable plan and sometimes producing various undesirable plans. Some of the objects involved in the query have Virtual Private Database (VPD) policies in place.
This note applies to both kinds of SQL Profiles.
A SQL Profile may have been created on a problematic query, or VPD policies may have been created on one or more objects referenced in a query with a formerly working SQL Profile.
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