Time out occurred while waiting for buffer latch

Question

Time out occurred while waiting for buffer latch

Viewing 15 posts - 16 through 30 (of 36 total)

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

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

Sounds to me like the SAN is caching the transactions and not doing the write operation when the tran goes through. Therefore SQL thinks its done but it isnt.

Check the write-ahead settings and consider balance loading the SAN controller switches (assuming you use two).

Have seen issues like that when load testing our new cluster. SQL handeled everything we through at it but the load on the SAN disks was enough to send Exchange RPC latency to 50+. We solved it by balancing the load of various servers between our two SAN switches.

Speak to your SAN guys and see what they think.

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

Tim Walker. SSCertifiable Points: 5173 More actions · Answer 2

I've had this error recently on SQL Server 2005 SP2. It seems to have been a function of installing Diskeeper 2009 Server Edition (Diskeeper 2008 Server Edition works fine). They have included some additional defragmentation methods in the latest release.

I'm guessing that in this case SQL doesn't cope with the fact that the underlying data files (MDF in my case) may have physically moved on the disk.

As per previous posts there are a number of other potential causes too.

.

randy.lee Valued Member Points: 67 More actions · Answer 3

For SAN drives: Check for HBA reset messages in your system or adapter logs

For local drives: Usually an IO issues or possibility a error on the disk that check disk would not pick up.

😎

Thanks guy for leading me in the right directions.

jsheldon SSCertifiable Points: 5250 More actions · Answer 4

We are g etting this problem as well AND just applied Diskeeper 2009 Admin Server tool to the server.

I am going to remove the diskeeper product, restart the SQL server and then give an earful to Diskeeper support 😉

Tim Walker. SSCertifiable Points: 5173 More actions · Answer 5

Interesting that you have got the same problem. I was 90% sure that Diskeeper 2009 had prompted it but not certain.

Note that the problem machine was SQL Server 2005 SP2 NOT SP3.

Can you confirm which your machine is?

Also as per my previous post Diskeeper 2008 seems fine.

I'd be very interested in your outcome with Diskeeper so please post it.

Thanks

.

jsheldon SSCertifiable Points: 5250 More actions · Answer 6

Will do...It is SQL Server 2005 SP2 I haven't done any applying of any new service packs

This didn't have a problem with 2008 diskeeper

Sent tech case with support will update when I find something.

Tim Walker. SSCertifiable Points: 5173 More actions · Answer 7

Tim Walker.

SSCertifiable

Points: 5173

February 10, 2009 at 8:28 am

#941276

Great, thanks

.

Ajay Prakash SSC Eights! Points: 891 More actions · Answer 8

Interesting.. Will wait for the answer..

Kindest Regards,

Ajay Prakash

jsheldon SSCertifiable Points: 5250 More actions · Answer 9

****Got an answer!!! *******:w00t:

On the phone with Diskeeper they ARE able to duplicate the stack dump problem. Tech support indicates that 2009 version is holding on to various sql binaries which is causing the dumps.

They are sending me the latest build for me to test. I can test this on a non-critical production server (just has network tools, backup exec) awaiting the email from diskeeper will update again after I apply the latest build

but by the sounds of it they don't seem to have the cause of this problem yet.

jsheldon SSCertifiable Points: 5250 More actions · Answer 10

Update---

Installed 839 build of Diskeeper 2009 on a SQL Server 2005 with SP2 and after 18 hours no stack dump. Continue to monitoring the situation. Not sure if Diskeeper will push this as an update...

more to follow...

Tim Walker. SSCertifiable Points: 5173 More actions · Answer 11

Thanks for the update. The Diskeeper build that failed for me was 13.0.835. It sounds like you are running a later one.

Diskeeper asked me for some further information early last week, but I was on holiday so haven't supplied it yet. Since they requested it you have made progress .. which is excellent.

I'd like to make sure that the guy handling my case (Naveen Julien Louis) is aware of your case to save time collating information that may be irrelevant.

Have you a named contact at Diskeeper support I can give him?

Thanks.

.

jsheldon SSCertifiable Points: 5250 More actions · Answer 12

My support ticket number is 16723622 and Ben Fiandaca is my tech support rep. I must now place this build within the administration and then push out to the servers.

Tim Walker. SSCertifiable Points: 5173 More actions · Answer 13

Thank you very much for your help. I have emailed my contact with the information supplied.

I gather that since you are now putting the build into production, you must be happy with it!

.

jsheldon SSCertifiable Points: 5250 More actions · Answer 14

Well yes and no, it is on our SQL server that has several 'grunt' programs..I haven't yet taken the dive to put it on our ERP server yet but I will update again my progress..

david.francis SSC Rookie Points: 48 More actions · Answer 15

I've just had connection loss on a SQL 2000 SP4 box that has recently had Diskeeper 2009 Enterprise trialled on it. Have now removed the product again.