Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Error 845: Time out occurred while waiting for buffer latch type 1 for page (0:-1688993522), database ID 5, object ID 0, index ID 0 Expand / Collapse
Author
Message
Posted Monday, January 5, 2009 5:42 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, December 9, 2014 7:48 AM
Points: 1,135, Visits: 3,148
(SQL Server 7 SP4)

Last night, my scheduled optimisations job failed while reindexing with the following error:

[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 5180: [Microsoft][ODBC SQL Server Driver][SQL Server]Could not open FCB for invalid file ID 0 in database 'PLMS'. Table or database may be corrupted.
[Microsoft][ODBC SQL Server Driver][SQL Server]Index (ID = 1) is being rebuilt.
[Microsoft][ODBC SQL Server Driver][SQL Server]Index (ID = 2) is being rebuilt.

** Execution Time: 0 hrs, 8 mins, 12 secs **

[Microsoft SQL-DMO (ODBC SQLState: 08S01)] Error 0: [Microsoft][ODBC SQL Server Driver]Communication link failure


Now my hourly transaction log backup fails every time with the following:

[1] Database PLMS: Transaction Log Backup...
Destination: [D:\PLMS_BACKUP\PLMS\PLMS_tlog_200901051000.TRN]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 845: [Microsoft][ODBC SQL Server Driver][SQL Server]Time out occurred while waiting for buffer latch type 1 for page (0:-1688993522), database ID 5, object ID 0, index ID 0.
[Microsoft][ODBC SQL Server Driver][SQL Server]Backup or restore operation terminating abnormally.
Deleting old text reports... 2 file(s) deleted.


And my SQL log contains the following every few minutes:
2009-01-05 10:12:12.61 spid5 Error: 845, Severity: 17, State: 2
2009-01-05 10:12:12.61 spid5 Time out occurred while waiting for buffer latch type 1 for page (0:-1688993522), database ID 5, object ID 0, index ID 0..
2009-01-05 10:22:12.89 spid63 Time out occurred while waiting for buffer latch type 1, bp 0x145ec580, page (0:-1688993522), stat 0x40d, object ID 5:0:0, waittime 500. Continuing to wait.
2009-01-05 10:33:53.31 spid5 Time out occurred while waiting for buffer latch type 1, bp 0x145ec580, page (0:-1688993522), stat 0x40d, object ID 5:0:0, waittime 500. Continuing to wait.


I've successfully reindexed the table in question, but my concern is that my Checkpoint process is sitting with a lastwaittype of PAGEIOLATCH_EX and the waitresource 5:0:-1688993522. What would happen if I restarted the server while the Checkpoint process cannot complete? Is the negative page number a sign of corruption or do pages in a certain state have a negative number?

I've checked the disks and there are no problems with them. The server has a healthy amount of available ram and as far as I can see, it is not under any greater load than usual.

Thanks,
Simon
Post #629707
Posted Monday, January 5, 2009 11:01 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 5:23 AM
Points: 40,609, Visits: 37,061
Eeep. That does not look good.
There's no way that I know of to get a negative page number, as the page number is an incremental count of 8k chunks of the data file.

Can you run a checkDB on that database? If possible, before you restart the service.

DBCC CHECKDB (< Database Name > ) WITH NO_INFOMSGS, ALL_ERRORMSGS




Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #629999
Posted Tuesday, January 6, 2009 2:34 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, December 9, 2014 7:48 AM
Points: 1,135, Visits: 3,148
Hi Gail,

I ran the DBCC CHECKDB this morning and it came back completely clean. I restarted the server (had to use WITH NOWAIT as the checkpoint was still throwing an error) and when it came back up, everything seems to be okay. The data is all there and the database was accessible almost immediately, as if the checkpoint had been set successfully before shutdown.

Still baffled by what happened but at least the server appears to be well again - will be keeping a close eye on it though.

Thanks for your help.

Simon
Post #630382
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse