Wrong Result Against Partitioned Tables Without Disabled Bug 6239039 Fix
Last updated on MAY 12, 2017
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199.0 to 188.8.131.52 [Release 11.2]
Information in this document applies to any platform.
If querying against partitioned tables, then it returns wrongly, i.e.:
"no rows selected"
The result of a query should only ever be impacted by the data in the table and not the physical characterisitics of the table, such as whether it's partitionedand what partitions have been allocated.
The "no rows selected" result returned by the query is incorrect.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms