RE: Arch log files sizes

From: Mark W. Farnham <>
Date: Wed, 12 Nov 2008 06:02:24 -0500
Message-ID: <>

I'd *guess* that Prabhu means, not ten thousand two hundred four. ;)  

As for growth in archive log size, that can be for a lot of different reasons. The simplest explanation is increased insert and update load. If you do not believe it is from increased load then the likely suspects are things like turning on replication or dataguard so that everything has to be logged or someone changing an etl or similar jobs so that it no longer uses direct paths, or breaking up a monolith that previously used global temp into a phased job that now relys in an interim table that must logged. As for the size of individual arch sizes, that is either an increase in logged changes per unit time or an increase in the length of time for an artificial switch. I would be more concerned about the rate of redo per unit time overall than the size of the arch files.  

I suppose the other thing that you should check is the 'drain' rate. That is, if you're shoveling the arch files somewhere so you can delete them, has something slowed that process down?  

Good luck, and please don't consider my laundry list above an attempt to be comprehensive. Those are just examples of things that *might* tend to cause the change you have reported.  


From: [] On Behalf Of Nizar Ahmed
Sent: Wednesday, November 12, 2008 5:25 AM To:; Subject: RE: Arch log files sizes  

Something's is not right here. 10204 instances - that's fat-fetched.    

G. Nizar A. Baig  

From: [] On Behalf Of Prabhu, Krishnaswamy
Sent: Wednesday, November 12, 2008 9:33 AM To:
Subject: Arch log files sizes  


We are running 10204 instances, recently the arch log destination got filled up 100% and we noticed few arch logs files sizes are varying, the sizes are twice larger than the average file size, archive_lag_target is set to 0. Can anyone please throw more insight on this.  


Team India gets set to thwart Australia's quest for the final frontier. Catch the action on MSN Try it now! <>

  • Disclaimer: The information in this email and in any files transmitted with it, is intended only for the addressee and may contain confidential and/or privileged material. Access to this email by anyone else is unauthorized. If you receive this in error, please contact the sender immediately and delete the material from any computer. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is strictly prohibited. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of STC.
Received on Wed Nov 12 2008 - 05:02:24 CST

Original text of this message