Re: waiting for log buffer??

james wrote: > There are 8 log files of 500 MB each. I'd prefer 80 at 50Mb. Apart from the water marks, there's another granularity effect that kicks in that might be a problem with only 8. Probably doubtful though... Waiting for a log buffer .... hmmmmm. Exactly what is in the load script? How is it being loaded? Just a plain LOAD statement in SQL, or are you using dbload? -- Hell hath no imppotent fury like a geek scorned.

The 'load' is really a select into, creating aggregates for a weekly summary. However, at the point where trouble ocurrs, the load script is building an index on a temporary table. What could hold up a log buffer flush, or what would prevent access to a log buffer? I imagine a log switch would prevent access to a log buffer, if they were all full at that point in execution. But I can't fathom how that could happen. And it was not a short period of time where other sessions were in stasis, it was minutes. On Mon, 28 Jul 2003 12:11:16 +1000, "Andrew Hamm" <ahamm@mail.com> wrote: >james wrote: >> There are 8 log files of 500 MB each. > >I'd prefer 80 at 50Mb. Apart from the water marks, there's another >granularity effect that kicks in that might be a problem with only 8. >Probably doubtful though... > >Waiting for a log buffer .... hmmmmm. > >Exactly what is in the load script? How is it being loaded? Just a plain >LOAD statement in SQL, or are you using dbload? Regards, James White white_a_james@notsohotmail.com