While refreshing the partition's graph Toad reports wrong record count for each partition.
The problem is that the data boundaries are always considered inclusive even if the data partition is not defined as "Start Inclusive" or "End Inclusive", so for a partition boundary defined as starting from (1) inclusive and ending at (10) exclusive, toad run the following query on the database to count the records:
select count(1) from table where (key >= low_boundary and key <= high_boundary)
instead of:
select count(1) from table where (key >= low_boundary and key < high_boundary
WORKAROUND:
None
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center