> > with _in_memory_undo=false
> > true => 6656 KB
> > false => 7168 KB
> > supplemental logging => 10752 KB
> > This is seems understandable.
>
> How did you test the redo generation? I saw some strange things happening,
> that with the same test case occasionally way more or less of redo was
> generated (which means that my test case wasn't adequate enough).
The database have beed 100% dedicated for a test (single user mode).
Before and after each update I have made logswitch.
Have noted the generated archive redo file size.
(I know I could use v$sesstat, but in that case the size of redo
wasn't the primary attantion object)
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Feb 23 2006 - 18:19:35 CST
