How to Analyze Why PX Queries Are Slow with AutoDOP Feature
(Doc ID 1380736.1)
Last updated on AUGUST 14, 2020
Oracle Database - Enterprise Edition - Version 220.127.116.11 and later Oracle Database Cloud Schema Service - Version N/A and later Oracle Database Exadata Cloud Machine - Version N/A and later Oracle Cloud Infrastructure - Database 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.
For developers and DBAs to troubleshoot slow running SQLs with the Automatic Degree of Parallelism (AutoDOP) feature.
How to analyze why PX queries are slow with Automatic Degree of Parallelism( AutoDOP ). The idea behind calculating the AutoDOP is to find the highest possible DOP (ideal DOP) that still scales. In other words, if we were to increase the DOP even more above a certain DOP we would see a tailing off of the performance curve and the resource cost / performance would become less optimal. Therefore the ideal DOP is the best resource/performance point for that statement.
This article would like to give troubleshooting steps to analyze performance issues around PX queries running with AutoDOP feature.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!