823 Error but DBCC clean

  • This morning on one of our virtual servers I saw that the differential backup job failed. The job does an integrity check and then backs up databases. There were no reindexing or other jobs running at the same time and it's a pretty low activity point for the server. Upon looking into it, I saw the following error messages:

    Error 823, Severity 24, State 7

    "Operating system error 'stale page (a page read returned a log sequence number (LSN) (2148:976:1) that is older than the last one that was written (0:0:0))' resulted from attempt to read the following: sort run page (1:588496), in file 'E:\tempdb.mdf', in database with ID 2. Sort is retrying the read."

    and then directly after that is:

    "DBCC CHECKDB (<userdb>) WITH no_infomsgs executed by (<user>) found 1 errors and repaired 0 errors. Elapsed time: 0 hours 8 minutes 27 seconds. Internal database snapshot has split point LSN = 000c1737:000001b3:0001 and first LSN = 000c1737:000001b2:0001."

    All the other DBCC CHECKDB commands processed with 0 errors found. I've been looking through other posts on how to handle this. The first thing I did is run DBCC CHECKDB WITH ALL_ERRORMESSAGES, NO_INFOMSGS. I expected the database from last nights issue to have corruption. However, that database and all the others came back fine. I reached out to my SAN admins and they checked the SAN, SAN switch and ESX host the server is on and they did not see any errors in the logs. They've offered to move the datastore if I'd like, but I'm not sure where to proceed. I'm kind of stumped on why it would throw an 823 error but all the databases came back ok. Could it be something intermittent? If so, why wouldn't it show up in any of the storage logs?

    The server is running SQL Server 2008 (10.0.5500.0)

Viewing 0 posts

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