We have this production box having SQL Server 7 SP3 on
Windows NT 4 SP6 and running in a cluster.

This week we have observed error 9002 (for log) although
database autogrowth is set 'ON' and there is enough space
on the disk for the log file to grow by a factor of 10%.
We could'nt find anything wrong with the databases.

Any ideas on why this happened and how we can resolve
this ?

TIA

Kohinoor

Report this post to a moderator

Well, not really.

But you might just verify that there is nothing else happening on that disk
drive. (e.g. the paging data set is not there, it is not used for other
temporary files, etc.) Something like this could cause the space to be
unavailable when needed, but available again when you go to check.

A second thought, if you have ever monitored autogrow in a heavy logging
situation you will discover that it may not grow by just the percentage you
selected. I had a situation in which the log grew something like:
100 Meg
500 Meg
300 Meg
100 Meg
600 Meg - but that filled the disk.

Russell Fields

"Kohinoor" <tok_ano@nospam.hotmail.com> wrote in message
news:12b7d01c21dce$283585e0$b1
e62ecf@tkmsftngxa04...
> We have this production box having SQL Server 7 SP3 on
> Windows NT 4 SP6 and running in a cluster.
>
> This week we have observed error 9002 (for log) although
> database autogrowth is set 'ON' and there is enough space
> on the disk for the log file to grow by a factor of 10%.
> We could'nt find anything wrong with the databases.
>
> Any ideas on why this happened and how we can resolve
> this ?
>
> TIA
>
> Kohinoor
>
>

Report this post to a moderator

Thanks Russel.

I am contemplating perhaps 'autogrowth' could not find
contiguous space at that time. However, I will keep a tab
on this.

Regards

Kohinoor

>-----Original Message-----
>Well, not really.
>
>But you might just verify that there is nothing else
happening on that disk
>drive. (e.g. the paging data set is not there, it is not
used for other
>temporary files, etc.) Something like this could cause
the space to be
>unavailable when needed, but available again when you go
to check.
>
>A second thought, if you have ever monitored autogrow in
a heavy logging
>situation you will discover that it may not grow by just
the percentage you
>selected. I had a situation in which the log grew
something like:
>100 Meg
>500 Meg
>300 Meg
>100 Meg
>600 Meg - but that filled the disk.
>
>Russell Fields
>
>"Kohinoor" <tok_ano@nospam.hotmail.com> wrote in message
> news:12b7d01c21dce$283585e0$b1
e62ecf@tkmsftngxa04...
>> We have this production box having SQL Server 7 SP3 on
>> Windows NT 4 SP6 and running in a cluster.
>>
>> This week we have observed error 9002 (for log) although
>> database autogrowth is set 'ON' and there is enough
space

>> on the disk for the log file to grow by a factor of 10%.
>> We could'nt find anything wrong with the databases.
>>
>> Any ideas on why this happened and how we can resolve
>> this ?
>>
>> TIA
>>
>> Kohinoor
>>
>>
>
>
>.
>

Report this post to a moderator