Parallel_Degree_Policy=AUTO does not control recursive SQL generated for the purposes of referential integrity
(Doc ID 2042044.1)
Last updated on AUGUST 26, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 to 12.1.0.2 [Release 11.2 to 12.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
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
Information in this document applies to any platform.
Symptoms
When PARALLEL_DEGREE_POLICY is set to AUTO the optimizer computes the DOP for user queries. Even if the optimizer decides to run a query in serial mode the recursive queries used to check referential integrity can run in parallel depending on the table's PARALLEL setting. If there are many of these queries this can generate a large number of parallel workers. This is similar to document “Some Statements Unexpectedly Run in Parallel With Auto DOP (PARALLEL_DEGREE_POLICY = AUTO or LIMITED) (Doc ID 1643540.1)”, but this is related to bug 9728438, whereas the behavior described in this document is expected.
Changes
Recursive SQL statements used to check referential integrity use the target table's PARALLEL setting
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 |