June 12, 2012 at 10:26 am
We have seen following error today while running a ad-hoc query on SQL SERVER 2008-
Msg 823, Level 24, State 7, Line 1
The operating system returned error stale page (a page read returned a log sequence number (LSN) (10108:44891:1) that is older than the last one that was written (0:0:0)) to SQL Server during a read at offset 0x00000836bf0000 in file 'T:\tempdb.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
How should I go about resolving this error?
June 12, 2012 at 10:40 am
There's a problem with your IO subsystem - it's returning old data (old versions of pages). I would suggest you get your storage vendor in to help you, it could be cache, it could be other things in the IO subsystem
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 12, 2012 at 10:47 am
First thing you should do is run a set of full backups. Then save that somewhere on the side or, better still, off-site.
After that, you can try to identify the issue by running DBCC CHECKDB as it suggests. I'm with Gail. Get a pro in to help you on this one.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 12, 2012 at 10:48 am
In this case I probably wouldn't bother with CheckDB, since this is TempDB. But there is an underlying IO subsystem problem here that needs identifying.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 12, 2012 at 10:54 am
Ah, missed that it was tempdb. Still, assuming my disks are going off, I'm running an extra backup. I may still run DBCC on the other databases too.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply