Thanks Daniel, but I ran a quick query on v$db_cache_advice and see the following (I formatted the number) 1 select BLOCK_SIZE, SIZE_FOR_ESTIMATE "Size", SIZE_FACTOR "Factor", ESTD_PHYSICAL_READ_FACTOR "PIO Factor" 2 , ESTD_PHYSICAL_READS "PIOs" 3* from v$db_cache_advice > / BLOCK_SIZE Size Factor PIO Factor PIOs ---------- ---------- ---------- ---------- ------------------ 8192 16 .25 .0679 113,043,394 8192 32 .5 .0381 63,462,017 8192 48 .75 .0148 24,699,763 8192 64 1 1 1,664,058,522 8192 80 1.25 .9859 1,640,643,731 ... 8192 288 4.5 .8356 1,390,454,052 8192 304 4.75 .8214 1,366,896,833 8192 320 5 .7884 1,311,921,253 We can see that it now shows over 1 billion PIO's. I also checked the sprepins.sql script (the one spreport.sql calls) and that formats the value to 9,999,999,999,999.