Oracle partitioning bug (Bug 2111373)

I found a bug in Oracle partitioning (Bug 2111373 on Metalink, has public access), and they don't want to fix it! It affects all versions (I tried on 8.1.6, 8.1.7, and 9.0.1). While the results returned by the query are correct, there is a severe impact on performance. It affects queries agains tables with range partitioning on two columns, when BETWEEN condition is specified for the first
column, "=" (equal) condition is specified for the second column, and access is by full partition scan (no indexes). Instead of scanning partitions specified in the WHERE clause, Oracle scans ALL partitions between the first and the last partitions in the WHERE clause by Partition_Position.

Please see metalink for more info on this bug.

Regards,
Sev Received on Mon Jan 28 2002 - 17:42:09 CST