Time out occurred while waiting for buffer latch

Question

Time out occurred while waiting for buffer latch

Harris-358031

Old Hand

Points: 362
More actions
September 4, 2006 at 7:24 am

#115333

hi Im quite often gettig the following alert from the server.
Whats this all about??
SQLServer: SQLErrorLog:Warning: Time out occurred while waiting for buffer latch type 2,bp 0x180a940, page 1:1502), stat 0x1000f, object ID 5:1664724983:0, EC

Harris/
September 7, 2006 at 8:00 am

This was removed by the editor as SPAM

Viewing 15 posts - 1 through 15 (of 36 total)

You must be logged in to reply to this topic. Login to reply

Steve Jones - SSC Editor SSC Guru Points: 736183 More actions · Answer 1

I think this is an error on a blocking issue. The query was blocked by something else and timed out. Try increasing your query timeout and see if this helps.

Also, look for blocking when you are seeing this.,

Ben McGinnis SSC Journeyman Points: 76 More actions · Answer 2

I'm receiving a very similar error when running a sql server agent job. There doesn't appear to be anything else going on on the server so i don't think it's blocking. We're Running SQL Server 2005 Enterprise Edition x64 SP 2.

I've read elsewhere that it could be a driver issue. I've also read that it could be a problem with the fact that the databases were recently migrated from SQL 2000 to SQL 2005.

I haven't confirmed either is the cause yet. Any additional help would be appreciated!

http://www.sql-server-performance.com/faq/error_messages_heavy_load_p1.aspx -- could be drivers

http://support.microsoft.com/kb/940942 -- could be because of the upgrade.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

In my experience, buffer latch timeouts are often IO related. You may want to check you drive's performance if you get these more than once or twice.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Ben McGinnis SSC Journeyman Points: 76 More actions · Answer 4

I've got our system admins checking the drivers and looking for other disk performance issues but they haven't found anything yet. The machine is new (3 weeks old) and we're migrating a very large old database that was on 18 machines onto 1 machine. We've got 10 migrated and the latch error occurs when we run a processing job on any one of the migrated databases. It happens intermittently though, some times it does sometimes it doesn't.

Thanks!

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 5

If you can, run the SQLIOSim (of SQLIOStress, can't remember the name) and see what it tells you about the drives.

It's a stress test tool for drives that simulated the way SQL interacts with the drives.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

sudhakara SSCrazy Eights Points: 9425 More actions · Answer 6

how to resolve this issue ?. or what i have do to stop this error message ?

Thanks in advance .

neeraj_nagpal SSC Enthusiast Points: 137 More actions · Answer 7

I hope its not the case for you, but I got these errors when table had corruption. If you are seeing warnings for a particular object, please run checktable on that object

Marios Philippopoulos SSC Guru Points: 57190 More actions · Answer 8

neeraj_nagpal (7/10/2008)
I hope its not the case for you, but I got these errors when table had corruption. If you are seeing warnings for a particular object, please run checktable on that object

I have the same problem and there may be corruption in my table. Are the results below indicative of corruption? (The table has over 2,000,000 records)

DBCC results for 'tblName'.
There are 0 rows in 2 pages for object "tblName".

__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

sql_monkey SSC Eights! Points: 867 More actions · Answer 9

Just curious...I have gotten the same error recently, but not regularly. Based on what is happening in my db when I get this error, I have some suspicions that also point to I/O issues.

I only have one sproc that EVER returns this error. It is part of a series of sprocs that copy rows from table A to B, delete them from A, and insert new rows into A. These transactions occurr back-to-back as a series of child sprocs being called from a parent.

The reason I suspect this is an I/O issue in my case is that I inserted a count(*) with(nolock) into the last step that inserts recs into Table A and it has count(*) > 0 even though the previous sproc deletes all rows from that table. So, doesn't that mean it MUST be an I/O lag?

SPillai-341190 Valued Member Points: 55 More actions · Answer 10

The Common issue for this error is

Hardware that does not meet your input/output (I/O) and memory needs.

Improperly configured and tested settings.

Inefficient design.

Refer http://support.microsoft.com/default.aspx?scid=kb%3BEN-US%3BQ310834

matthew h-472392 Valued Member Points: 55 More actions · Answer 11

SPillai (10/10/2008)
The Common issue for this error is
Hardware that does not meet your input/output (I/O) and memory needs.
Improperly configured and tested settings.
Inefficient design.
Refer http://support.microsoft.com/default.aspx?scid=kb%3BEN-US%3BQ310834

thanks, that helps a lot

Schadenfreude-Mei SSChampion Points: 14083 More actions · Answer 12

Hey everyone, I can see that no-one has put much on here for a while, but just fyi:

We had a similar issue, ever since a reboot following some recent ms patches.

We ran a 'chkdsk /f' on the SQL data volume and after a restart it is now fine.

HTH.

Adam.

Adam Zacks-------------------------------------------Be Nice, Or Leave

sql_monkey SSC Eights! Points: 867 More actions · Answer 13

thanks for the advice

I tried so many things with no success that I got a little frustrated.

As I mentioned, the parent sproc calls child sproc 1, which deletes records. The parent then calls child 2 which still sees the records that were deleted, so it doesn't do the insert that it's supposed to do. Our systems guy swears that the SAN is fine, but when I add a 1 second WAIFOR DELAY for every 100K records to be deleted, my problem is solved.