March 12, 2002 at 8:54 am
I am running Sql2000 sp2 ent ed., on a Win2000 sp2 adv server. This is an active/active cluster. I am receiving the following errors in the sqlserver log.
2002-03-11 17:00:00.47 spid75 Time out occurred while waiting for buffer latch type 2, bp 0x18e3bc0, page 1:261), stat 0x40d, object ID 20:903010298:0, EC 0x704CD5A8 : 0, waittime 300. Not continuing to wait.
2002-03-11 17:01:36.44 spid64 Time out occurred while waiting for buffer latch type 2, bp 0x1604b80, page 1:54), stat 0x40d, object ID 17:903010298:0, EC 0x59C87500 : 0, waittime 300. Not continuing to wait.
2002-03-11 17:03:08.91 spid111 Time out occurred while waiting for buffer latch type 2, bp 0xf66dc0, page 1:226774), stat 0x40d, object ID 8:654625375:0, EC 0x70919510 : 0, waittime 300. Not continuing to wait.
2002-03-11 17:03:51.24 spid124 Time out occurred while waiting for buffer latch type 2, bp 0xf66dc0, page 1:226774), stat 0x40d, object ID 8:654625375:0, EC 0x62E25510 : 0, waittime 300. Not continuing to wait.
2002-03-11 17:04:50.65 spid131 Time out occurred while waiting for buffer latch type 2, bp 0xf66dc0, page 1:226774), stat 0x40d, object ID 8:654625375:0, EC 0x637F9510 : 0, waittime 300. Not continuing to wait.
2002-03-11 17:05:00.76 spid101 Time out occurred while waiting for buffer latch type 2, bp 0x1002440, page 1:320), stat 0x40d, object ID 20:0:0, EC 0x396B9598 : 0, waittime 300. Not continuing to wait.
This is just three lines of error log, I cannot get a connection to the cluster administrator inorder to fail the machine over to the other node. Has anyone seen these errors, or could point me to some references.
Thanks
Tom
March 12, 2002 at 4:31 pm
Check these to see if they fit your problem
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q310834
Or if you have AWE enabled
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q309093
Or could be a SQL 7 problem that somehow got put back in on 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q276499
If none of these fit in any way then the problem is deeper. But I believe the problem will be in case one with auto shrink or auto grow enabled on your cluster.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
March 13, 2002 at 7:11 am
Thanks for the links, but I've already looked at all of those.
We don't have AWE enabled. We don't have the auto shrink, but do use autogrow. This problem has only happened twice over 3 months, but the result is to totally power off the machine to get it back.
I did find another article at google, that said it was a bug with microsoft when using temporary tables of the #table_type, and using a select statement with multiple unions which we also use.
I'll keep looking and let you know what I can come up with.
Tom Goltl
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply