Parallel Index Operations

Got the following error messages when rebuilding indexes on SQL Server 2000 + SP3 server.
WARNING: EC 5c166098, 2 waited 300 sec. on latch 5c1694bc. Not a BUF latch.
Waiting for type 0x2, current count 0xa, current owning EC 0x5C16A098.
Refer to KB-810195, but it should be corrected in SP3. My server has already service pack 3 installed.
Johnny
We have seen this in relation to IO problems, have you checked the windows
system event log?
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:087B2B6A-32A4-4C14-841D-4FE2993B8E75@.microsoft.com...
> Got the following error messages when rebuilding indexes on SQL Server
2000 + SP3 server.
> WARNING: EC 5c166098, 2 waited 300 sec. on latch 5c1694bc. Not a BUF
latch.
> Waiting for type 0x2, current count 0xa, current owning EC 0x5C16A098.
> Refer to KB-810195, but it should be corrected in SP3. My server has
already service pack 3 installed.
> Johnny
>
|||There is no errors in the system & application event log around the time of running index rebuild.

Parallel Index Operations

Got the following error messages when rebuilding indexes on SQL Server 2000
+ SP3 server.
WARNING: EC 5c166098, 2 waited 300 sec. on latch 5c1694bc. Not a BUF latch.
Waiting for type 0x2, current count 0xa, current owning EC 0x5C16A098.
Refer to KB-810195, but it should be corrected in SP3. My server has alread
y service pack 3 installed.
JohnnyWe have seen this in relation to IO problems, have you checked the windows
system event log?
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:087B2B6A-32A4-4C14-841D-4FE2993B8E75@.microsoft.com...
> Got the following error messages when rebuilding indexes on SQL Server
2000 + SP3 server.
> WARNING: EC 5c166098, 2 waited 300 sec. on latch 5c1694bc. Not a BUF
latch.
> Waiting for type 0x2, current count 0xa, current owning EC 0x5C16A098.
> Refer to KB-810195, but it should be corrected in SP3. My server has
already service pack 3 installed.
> Johnny
>|||There is no errors in the system & application event log around the time of
running index rebuild.

Parallel Index Operations

Got the following error messages when rebuilding indexes on SQL Server 2000 + SP3 server.
WARNING: EC 5c166098, 2 waited 300 sec. on latch 5c1694bc. Not a BUF latch.
Waiting for type 0x2, current count 0xa, current owning EC 0x5C16A098.
Refer to KB-810195, but it should be corrected in SP3. My server has already service pack 3 installed.
JohnnyWe have seen this in relation to IO problems, have you checked the windows
system event log?
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:087B2B6A-32A4-4C14-841D-4FE2993B8E75@.microsoft.com...
> Got the following error messages when rebuilding indexes on SQL Server
2000 + SP3 server.
> WARNING: EC 5c166098, 2 waited 300 sec. on latch 5c1694bc. Not a BUF
latch.
> Waiting for type 0x2, current count 0xa, current owning EC 0x5C16A098.
> Refer to KB-810195, but it should be corrected in SP3. My server has
already service pack 3 installed.
> Johnny
>|||There is no errors in the system & application event log around the time of running index rebuild.

PAGEIOLATCH WAIT

Can someone help me understand the various causes of
pageio latch waits or point me in the direction of a good
resource on this subject (BOL info is not detailed
enough)? There are no other users on the system - and my
process is experiencing pageio latch waits. I'm guessing
that this issue is related to the disk subsystem, but
don't know for sure.superboy, you are right most times I have experienced pageiolatch issues hav
e been disk sub-system driver issues,
raid controller issue and usually anything related to H/W(disk) configuratio
n/problems|||See http://SQLDev.Net/misc/waittypes.htm
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"superboy" <anonymous@.discussions.microsoft.com> wrote in message
news:d5b601c3ef20$380b9160$a601280a@.phx.gbl...
> Can someone help me understand the various causes of
> pageio latch waits or point me in the direction of a good
> resource on this subject (BOL info is not detailed
> enough)? There are no other users on the system - and my
> process is experiencing pageio latch waits. I'm guessing
> that this issue is related to the disk subsystem, but
> don't know for sure.

PAGEIOLATCH WAIT

Can someone help me understand the various causes of
pageio latch waits or point me in the direction of a good
resource on this subject (BOL info is not detailed
enough)? There are no other users on the system - and my
process is experiencing pageio latch waits. I'm guessing
that this issue is related to the disk subsystem, but
don't know for sure.superboy, you are right most times I have experienced pageiolatch issues have been disk sub-system driver issues
raid controller issue and usually anything related to H/W(disk) configuration/problems|||See http://SQLDev.Net/misc/waittypes.htm
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2004 All rights reserved.
"superboy" <anonymous@.discussions.microsoft.com> wrote in message
news:d5b601c3ef20$380b9160$a601280a@.phx.gbl...
> Can someone help me understand the various causes of
> pageio latch waits or point me in the direction of a good
> resource on this subject (BOL info is not detailed
> enough)? There are no other users on the system - and my
> process is experiencing pageio latch waits. I'm guessing
> that this issue is related to the disk subsystem, but
> don't know for sure.