delayed block cleanout (?) for active tx

From: Alberto Dell'Era <alberto.dellera_at_gmail.com>
Date: Thu, 21 Jun 2007 14:28:44 +0200
Message-ID: <4ef2fbf50706210528p22695f81r2fc295d8fc0730f@mail.gmail.com>

Dear all,

create table t as select rpad(rownum, 100) x from dual connect by level <= 100000;
update t set x=x;

in another session:
set autotrace on
select count(x) from t;
Statistics

...

157612 redo size

If I select again - same redo size:

select count(x) from t;
Statistics

...

157612 redo size

Notice I haven't committed the update, so this is not the classic redo generated due to classic delayed block cleanout (updates to the ITL to mark the tx entries as "committed").

It is anyway related to cleanout, in fact v$mystat shows entries such as:

active txn count during cleanout                       3031
cleanout - number of ktugct calls                     3031
immediate (CR) block cleanout applications      3031
db block changes                                           3031

cleanouts and rollbacks - consistent read gets 3031

Clearly the select has to build the consistent image of the blocks, and clearly it has to visit the ITL, and then the rollback segment, to see whether the tx has committed etc etc; then, it seems that it updates "something" in the block (db block changes). Does anybody know what this "something" is, assuming of course my reasoning so far is correct ?

9.2.0.8 on Windows XP.

Thanks in advance
Alberto

-- 
Alberto Dell'Era
"the more you know, the faster you go"
--
http://www.freelists.org/webpage/oracle-l

Received on Thu Jun 21 2007 - 07:28:44 CDT