Not a BUF latch. Error Re-Indexing

We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
Advanced Server.
Weekly we have a job that drops all indexes on the database and recreates
them.
This job runs at the same time the daily backup and transaction log execute.
We received following error caused by the re-index:
"Time out occurred while waiting for buffer latch type 4..."
Please help me resolve these latch errors.
Thanks,
SQL Server errorlog
WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
continuing to wait.
Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0.
It not good practice to run such major maintenance operations as dropping
and recreating all indexes (I hope you use DBCC DBREINDEX btw) at the same
time as a backup. In general running the operations in parallel will not be
much quicker than running them in series (because your resources, specially
disk I/O, are limited). And if your backup finishes before the reindexing
finishes, part of your indexes will be reindexed and part not, but you don't
know exactly which.
Jacco Schalkwijk
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:AA424678-958D-478E-B6FF-574A7885455B@.microsoft.com...
> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log
> execute.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC
> 0x962263F0.
>
>
|||Hi
What does select @.@.version return for the SQL Server?
Have a look at:
http://support.microsoft.com/kb/310834/en-us
http://support.microsoft.com/kb/309093/EN-US/
Regards
Mike
"Joe K." wrote:

> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log execute.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0.
>
>