DB2 LUW Query Optimization - IXSCAN timerons greater than total timerons
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.