Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Hommer
Aged Yak Warrior
808 Posts |
 Posted - 2005-03-07 : 12:29:42
|
| I got this error this morning after we restart the server. The server did not use AWE, but all info I googled are pointing to awe related issue. And we have sp2. Time-out occurred while waiting for buffer latch type 2 for page (1:750528), database ID 5.And my last tlog backups did not run due to the same error.Thank you for any help. |
|
|
TG
Master Smack Fu Yak Hacker
6065 Posts |
Posted - 2005-03-07 : 13:36:18
|
| I think this one's over my head but I'm curious,Was that a Sql Service restart or a box reboot?Was the restart to solve a different problem?Is Sql up and running now?Edit - Saw this on another forum:SQL Server may hold a latch while attempting to remove an object from the cache. If that cached object contains information that is stored in memory from a shared memory allocation block, the cache removal may block or deadlock with another system server process ID (SPID) that is accessing the same memory block. As a result, the latch is held longer than anticipated, which may lead to latch warnings and timeouts for other users. check the SQL Server memory settings, make sure SQL Server has enough memory allotted to it, if the query is too memory intensive to run on the system you may have to add more RAM. Check the SQL Server errolog for other errors like 17832 . Be One with the OptimizerTG |
 |
|
|
Hommer
Aged Yak Warrior
808 Posts |
Posted - 2005-03-07 : 13:51:07
|
| We restarted sql server and reboot the 2003 server for the overall slow response time.Now I think I have nerrored it down to a table. When a select statement is run against it in QA, I got,Server: Msg 845, Level 17, State 1, Line 1Time-out occurred while waiting for buffer latch type 2 for page (1:750528), database ID 5.In activity log, i also saw numoursous:Waiting for type 0x3, current count 0x100022, current owning EC 0x82A6A098.andTime out occurred while waiting for buffer latch type 3,bp 0x119dc80, page 1:750528), stat 0x60d, object ID 5:0:0, EC 0x801783C0 : 0, waittime 300. Not continuing to wait.I checked the memory. I think it is fine. I am going to backup that table, then drop it. and see what will hapen from there. |
|
|
|
Hommer
Aged Yak Warrior
808 Posts |
Posted - 2005-03-07 : 14:32:08
|
| I don't know these two have any significance, I saw these two error entries right after the restart and before other errors emerged.Warning: unable to allocate 'min server memory' of 2048MB.The log file for database 'tempdb' is full. Back up the transaction log for the database to free up some log space.On the second one, the templog.ldf is only 43,200 kb, and is set to auto grow 10% in C drive with 30 Gb free.I’d appreciate any help. |
|
|
|
Hommer
Aged Yak Warrior
808 Posts |
Posted - 2005-03-08 : 10:44:13
|
| After we kicked everybody out last night, and restart the server, it recovered itself!SQL Server is smarter than we thought. |
|
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2005-03-08 : 10:49:53
|
| If it re-occurs, check your event logs for drive errors.-------Moo. :) |
|
|
|
|
|
|
|
|
buffer latch error