buflatch error

Under what circumstances do we get this message?
Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec. on
latch 8130f2c0. Not a BUF latch.My first port of call will be to check H/W(controller, disk drives for bad
sectors)
switch on perfmon(current disk read/write queue length) see under what
circumstances this is happening(heavy read/write)
HTH
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
> Under what circumstances do we get this message?
> Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
> 2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec.
on
> latch 8130f2c0. Not a BUF latch.|||The output of sysprocesses might give some more information.
Here is an article that might be useful for you:
http://support.microsoft.com/?kbid=822101
A latch is a short-term lightweight synchronization object. The following
list describes the different types of latches:
? Non-buffer (Non-BUF) latch: The non-buffer latches provide
synchronization services to in-memory data structures or provide re-entrancy
protection for concurrency-sensitive code lines. These latches can be used
for a variety of things, but they are not used to synchronize access to
buffer pages.
This message indicates longer than expected thread wait in the system. If
you see a drop of performance due to this, please consider contact microsoft
support. The problem might have been fixed by existing hotfix or QFE
http://support.microsoft.com/kb/309093/EN-US/
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
> Under what circumstances do we get this message?
> Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
> 2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec.
> on
> latch 8130f2c0. Not a BUF latch.|||Thanks Wei. It helps
"wei xiao" wrote:
> The output of sysprocesses might give some more information.
> Here is an article that might be useful for you:
> http://support.microsoft.com/?kbid=822101
> A latch is a short-term lightweight synchronization object. The following
> list describes the different types of latches:
> ? Non-buffer (Non-BUF) latch: The non-buffer latches provide
> synchronization services to in-memory data structures or provide re-entrancy
> protection for concurrency-sensitive code lines. These latches can be used
> for a variety of things, but they are not used to synchronize access to
> buffer pages.
>
> This message indicates longer than expected thread wait in the system. If
> you see a drop of performance due to this, please consider contact microsoft
> support. The problem might have been fixed by existing hotfix or QFE
> http://support.microsoft.com/kb/309093/EN-US/
> --
> Wei Xiao [MSFT]
> SQL Server Storage Engine Development
> http://weblogs.asp.net/weix
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Bharath" <Bharath@.discussions.microsoft.com> wrote in message
> news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
> > Under what circumstances do we get this message?
> >
> > Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
> > 2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec.
> > on
> > latch 8130f2c0. Not a BUF latch.
>
>

buflatch error

Under what circumstances do we get this message?
Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec. on
latch 8130f2c0. Not a BUF latch.
My first port of call will be to check H/W(controller, disk drives for bad
sectors)
switch on perfmon(current disk read/write queue length) see under what
circumstances this is happening(heavy read/write)
HTH
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
> Under what circumstances do we get this message?
> Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
> 2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec.
on
> latch 8130f2c0. Not a BUF latch.
|||The output of sysprocesses might give some more information.
Here is an article that might be useful for you:
http://support.microsoft.com/?kbid=822101
A latch is a short-term lightweight synchronization object. The following
list describes the different types of latches:
? Non-buffer (Non-BUF) latch: The non-buffer latches provide
synchronization services to in-memory data structures or provide re-entrancy
protection for concurrency-sensitive code lines. These latches can be used
for a variety of things, but they are not used to synchronize access to
buffer pages.
This message indicates longer than expected thread wait in the system. If
you see a drop of performance due to this, please consider contact microsoft
support. The problem might have been fixed by existing hotfix or QFE
http://support.microsoft.com/kb/309093/EN-US/
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
> Under what circumstances do we get this message?
> Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
> 2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec.
> on
> latch 8130f2c0. Not a BUF latch.
|||Thanks Wei. It helps
"wei xiao" wrote:

> The output of sysprocesses might give some more information.
> Here is an article that might be useful for you:
> http://support.microsoft.com/?kbid=822101
> A latch is a short-term lightweight synchronization object. The following
> list describes the different types of latches:
> ? Non-buffer (Non-BUF) latch: The non-buffer latches provide
> synchronization services to in-memory data structures or provide re-entrancy
> protection for concurrency-sensitive code lines. These latches can be used
> for a variety of things, but they are not used to synchronize access to
> buffer pages.
>
> This message indicates longer than expected thread wait in the system. If
> you see a drop of performance due to this, please consider contact microsoft
> support. The problem might have been fixed by existing hotfix or QFE
> http://support.microsoft.com/kb/309093/EN-US/
> --
> Wei Xiao [MSFT]
> SQL Server Storage Engine Development
> http://weblogs.asp.net/weix
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Bharath" <Bharath@.discussions.microsoft.com> wrote in message
> news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
>
>

buflatch error

Under what circumstances do we get this message?
Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec. on
latch 8130f2c0. Not a BUF latch.My first port of call will be to check H/W(controller, disk drives for bad
sectors)
switch on perfmon(current disk read/write queue length) see under what
circumstances this is happening(heavy read/write)
HTH
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
> Under what circumstances do we get this message?
> Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
> 2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec.
on
> latch 8130f2c0. Not a BUF latch.|||The output of sysprocesses might give some more information.
Here is an article that might be useful for you:
http://support.microsoft.com/?kbid=822101
A latch is a short-term lightweight synchronization object. The following
list describes the different types of latches:
? Non-buffer (Non-BUF) latch: The non-buffer latches provide
synchronization services to in-memory data structures or provide re-entrancy
protection for concurrency-sensitive code lines. These latches can be used
for a variety of things, but they are not used to synchronize access to
buffer pages.
This message indicates longer than expected thread wait in the system. If
you see a drop of performance due to this, please consider contact microsoft
support. The problem might have been fixed by existing hotfix or QFE
http://support.microsoft.com/kb/309093/EN-US/
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
> Under what circumstances do we get this message?
> Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
> 2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec.
> on
> latch 8130f2c0. Not a BUF latch.|||Thanks Wei. It helps
"wei xiao" wrote:

> The output of sysprocesses might give some more information.
> Here is an article that might be useful for you:
> http://support.microsoft.com/?kbid=822101
> A latch is a short-term lightweight synchronization object. The following
> list describes the different types of latches:
> ? Non-buffer (Non-BUF) latch: The non-buffer latches provide
> synchronization services to in-memory data structures or provide re-entran
cy
> protection for concurrency-sensitive code lines. These latches can be used
> for a variety of things, but they are not used to synchronize access to
> buffer pages.
>
> This message indicates longer than expected thread wait in the system. If
> you see a drop of performance due to this, please consider contact microso
ft
> support. The problem might have been fixed by existing hotfix or QFE
> http://support.microsoft.com/kb/309093/EN-US/
> --
> Wei Xiao [MSFT]
> SQL Server Storage Engine Development
> http://weblogs.asp.net/weix
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Bharath" <Bharath@.discussions.microsoft.com> wrote in message
> news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
>
>