Mauricio,
Variances of 1G of redo generation (i.e. 4G one day, 2G
another day, 3G another day) are not indicative of anything
unusual. I've seen systems that generate 4T of redo one
day, 6T of redo another day, and then only 0.5T of redo the
following day. All without changing the size of the on
e -
From:
Mauricio Vélez
To: Multiple recipients of list ORACLE-L
Sent: Thursday, January 08, 2004 4:04
PM
Subject: Re: Re: Difference on ArchiveLog
(I'm rewriting the question)
Hello everybody thank for your answers,
the size I'm talking about is summing up
Hello everybody thank for your answers,
the size I'm talking about is summing up real sizes of archivelogs files, and I had each configuration of redo logs for one week, and the first one was for many months.
There was not any change on database objects and the database is small, the summing
Hmm...
Given the amount of data to work with, I would
chalk it up to coincidence.
I washed my car on Tuesday morning, Tuesday
afternoon it rained.
Washed it again on Wednesay, it rained again.
Didn't wash it Thursday, no rain.
If you could establish this pattern for at least
3 successive week
Is your system overloaded e.g. there is a
continuous queue of transactions waiting?
In that case, with bigger redologs, full
checkpoints happen less frequently, allowing database to work faster, thus
generating more redo.
But, othervise, the archive generation shouldn't be
dependent on red
