X$QKSXA_REASON TABLE, THE REASONS FOR ERROR CODE 353 GOT CHANGED IN 19C.
(Doc ID 2888303.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 19.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
The parallel DOP downgrade reason code in the below 19C Database version
And the meaning of the values is as follows
350: 'DOP downgrade due to adaptive DOP'
351: 'DOP downgrade due to resource manager max DOP' e.g. max DOP is set for resource group
352: 'DOP downgrade due to insufficient number of processes' e.g. value of parallel_max_servers would have been exceeded otherwise
353: 'DOP downgrade because workers failed to join'
The change in DOP downgrade reasons in 19C misleading
Changes
The version upgraded to 19C thereafter the value for reason codes changed
350 invalid limit map phrase
351 OLAP_CONDITION BEGIN predicate exists
352 DOP downgrade due to adaptive DOP
353 DOP downgrade due to resource manager max DOP
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 |