|
viadeazhu's research is very interesting.
We (including me) should not quickly jump to the conclusion about any relationship between heartbeat and SCN increase. It's just a hypothesis, until anybody can find an official document to prove it. 9i's 'redo size' statistic# is 115. If you run this query
select sysdate, dbms_flashback.get_system_change_number, value from v$sysstat where statistic# = 115;
multiple times in 9i, you'll see the SCN go up while redo value remains the same for a while. It may indicate the cause of the SCN increase is heartbeat, but we don't know for sure.
Before you run it in 10g, change 115 to 134. Do not use current_scn column of v$database to do this test. Apparently, a simple query (on any column) of v$database in 10g will increase SCN. This doesn't happen in 9i.
viadeazhu said you can't get SQL trace to generate a trace file. Two things you need to watch. One is you need to use oradebug to set event on the SMON session. What method did you use? Secondly, wait longer. You may need to wait as long as 5 minutes (SMON has a few cycles to perform its different routine tasks, one of which is 5 minutes.) The SQL trace I got on SMON in Oracle 10.2.0.1 on Windows has these SQLs (excluding select's, shown below not in order):
delete from smon_scn_time...
insert into smon_scn_time...
update smon_scn_time...
insert into sys.col_usage$ values...
lock table sys.col_usage$ in exclusive mode nowait
insert into sys.mon_mods$ values...
lock table sys.mon_mods$ in exclusive mode nowait
update sys.col_usage$...
update sys.mon_mods$...
Yong Huang |
|