DB2 LUW Query Optimization - IXSCAN timerons greater than total timerons Sorry - I feel like this is a newb question, but I can't find anything on it.
In optimizing a query, I was able to apparently reduce the total timerons from 3,700 to 38.
However, on closer examination of the explain plan for the optimized query, I see one IXSCAN that reports 3,707.97 timerons, while the total is still reported as 38.61!

I'm not super familiar with DB2 LUW, and was wondering how this could be.  Even with parallelism, I would not think we could get much smaller than, say, 1/4 of the largest #. Surely not 1/10th. (?)

This is DB2 LUW 9.5 on AIX.  Very plain-vanilla installation for testing environment. No HA, no partitioning, nothing like that.
Just want to tie this off.
As was suggested in the comments, this simply should not be so. It must have been a bug in the level of DB2 I was using.