Re: Thread 1 cannot allocate new log

--0-1189641421-960825248=:5322
Content-Type: text/plain; charset=us-ascii

 20mb is not all that big. Not only is the archiver having trouble keeping up, but you're also checkpointing at each log switch. I'd start with the logs at 100mb and increase from there if you need to. The only downside is that recovery will take longer, but how often do you have to recover v. how often are you checkpointing?  

rsands_at_lendleaserei.com wrote:

Listers,

What's the best approach to deal with the archiver not keeping up with the redo log switches? Currently, redo logs are 20 MB, originally had four groups. We have one process that runs twice a day and results in one or two 'cannot allocate new log' errors. The switch occurs seconds later without causing the update to fail, and the process completes in less than 10 minutes. Tried increasing the size of the logs, no improvement. Added two more log groups, errors stopped for a time, but then reoccurred. This process populates a denormalized table for queries, and the problem began after additional data was added to the base tables. Typically, I see only 4 to 12 switches within a 24 hour period, so I'm not sure if I should continue to added more groups or increase the size. If I increase the size, should I worry about checkpoints occurring too infrequently? (Only occur at log switches now). Both copies of the redo logs and the archived redo logs are all on separate disks.

Robyn

Lend Lease REI
Atlanta, GA

-- 
Author: 
INET: rsands_at_lendleaserei.com

Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing). 




---------------------------------
Do You Yahoo!?
Yahoo! Photos -- now, 100 FREE prints!
--0-1189641421-960825248=:5322
Content-Type: text/html; charset=us-ascii



<P> 20mb is not all that big. Not only is the archiver having trouble keeping up, but you're also checkpointing at each log switch. I'd start with the logs at 100mb and increase from there if you need to. The only downside is that recovery will take longer, but how often do you have to recover v. how often are you checkpointing?<BR>

<P> <BR><B><I>rsands_at_lendleaserei.com</I></B> wrote: <BR>

<BLOCKQUOTE style="BORDER-LEFT: #1010ff 2px solid; MARGIN-LEFT: 5px; PADDING-LEFT: 5px"><BR><BR><BR>Listers,<BR><BR>What's the best approach to deal with the archiver not keeping up with the redo<BR>log switches? Currently, redo logs are 20 MB, originally had four groups. We<BR>have one process that runs twice a day and results in one or two 'cannot<BR>allocate new log' errors. The switch occurs seconds later without causing the<BR>update to fail, and the process completes in less than 10 minutes. Tried<BR>increasing the size of the logs, no improvement. Added two more log groups,<BR>errors stopped for a time, but then reoccurred. This process populates a<BR>denormalized table for queries, and the problem began after additional data was<BR>added to the base tables. Typically, I see only 4 to 12 switches within a 24<BR>hour period, so I'm not sure if I should continue to added more groups or<BR>increase the size. If I increase the size, should I worry about checkpoints<BR>occur!

ring too infrequently? (Only occur at log switches now). Both copies of<BR>the redo logs and the archived redo logs are all on separate disks.<BR><BR>Robyn<BR><BR>Lend Lease REI<BR>Atlanta, GA<BR><BR><BR>-- <BR>Author: <BR>INET: rsands_at_lendleaserei.com<BR><BR>Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051<BR>San Diego, California -- Public Internet access / Mailing Lists<BR>--------------------------------------------------------------------<BR>To REMOVE yourself from this mailing list, send an E-Mail message<BR>to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in<BR>the message BODY, include a line containing: UNSUB ORACLE-L<BR>(or the name of mailing list you want to be removed from). You may<BR>also send the HELP command for other information (like subscribing). <BR></BLOCKQUOTE><BR><p><br><hr size=1><b>Do You Yahoo!?</b><br>


<a href="http://photos.yahoo.com/">Yahoo! Photos</a> -- now, 100 FREE prints!