Mauricio,
Think
about it.
Your
redo logs are now larger, and they have to be cleared out by the archiver less
often. So archivelog files are produced less often. So you have less
physical archive log files being produced.
The
other data that *used to be* in archivelog files are now in the Redo Log
files. It hasn't gone anyplace - it's just waiting for the Redo Log file
to fill up so it can be archived.
The
metric that you should be looking at is not how much archive log is being
generated - but how often a log file switch is being performed. I like no
less than 20 minutes - that is - an archivelog file is not being created more
often that 20 minutes. This ensures that the database is never waiting for
the archiver to complete it's work (thus stopping updates) before it can
continue.
Hope
this helps.
Tom Mercadante
Oracle Certified Professional
Oracle Certified Professional
-----Original Message-----
From: Mauricio "Vilez [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 07, 2004 3:10 PM
To: Multiple recipients of list ORACLE-L
Subject: Difference on ArchiveLogHello Everybody
Some days ago the database I work on had 3 logfiles that sized 100M and the database was generating 4G of archive daily.
I changed the size to 20M and the database began to generate 2G of archive daily, then I changed to 50M and It began to generate 3G of archive daily.
So I don't understand why this difference occurs.
The database I'm working on is oracle 8i and I'is on Windows NT.
Regards Mauricio Vélez
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
