Wrong Results or Incorrect Filter Predicate Pushdown For UNION ALL View With NOT EXISTS and Remote Tables Over DBLINK At Both Branches
(Doc ID 2967417.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
- Wrong result is caused when all the following are met:
1) fix control 20232513 is enabled.
2) SQL statement includes a view or a subquery with UNION ALL or UNION.
3) Both sides of UNION ALL or UNION refer to remote table via DBLINK
4) Either side of UNION ALL or UNION has NOT EXIST or NOT IN
5) A predicate has been pushed down the UNION ALL view
Changes
Upgrade from 11.2.0.4 to 19c
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 |