How to Investigate Query Performance Regressions Caused by VPD (FGAC) Predicates?
(Doc ID 967042.1)
Last updated on FEBRUARY 01, 2022
Applies to:
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and laterOracle 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
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
Goal
This note tries to answer the following questions about the performance regressions caused by VPD:
#1. General Considerations. What are the implications of VPD?
#2. How to investigate?
#3. How to solve the performance problem?
#4. What to provide to support?
#5. Example
#6. Known issues
#6. Known issues
Solution
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
| Goal |
| Solution |
| #1. Take the sql trace file? |
| #2. Determine the predicate that has been applied on the base tables. |
| #3. Take a 10053 trace file. |
| #4. Use SQL Access Advisor: |
| #5. Use the SQL Tuning Advisor. |
| Known issues of Query Performance Regression due to VPD: |
| References |