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

Update Statistics Error Expand / Collapse
Author
Message
Posted Tuesday, January 21, 2014 8:19 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, April 10, 2014 9:50 AM
Points: 40, Visits: 1,092
I got the following error running a scheduled Update statistics job on one of user databases. Can anyone have me on this issue? Thanks

The operating system returned error stale page (a page read returned a log sequence number (LSN) (219608:3136:1) that is older than the last one that was written (0:0:0)) to SQL Server during a read at offset 0x0000000b3f0000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\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.
Post #1533114
Posted Tuesday, January 21, 2014 8:31 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 8:20 PM
Points: 14,793, Visits: 27,268
I'd suggest following the recommendations in the error message and run DBCC CHECKDB. Depending on where the statistics are, and if there are any other underlying problems, you may be able to get away with just dropping the statistic or the index associated with it (if it's not a column statistic). But you need to start with the consistency check.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1533127
Posted Tuesday, January 21, 2014 8:35 AM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Yesterday @ 10:48 AM
Points: 534, Visits: 790
As Grant suggested I would run this:
DBCC CHECKDB WITH ALL_ERRORMSGS, NO_INFOMSGS; 

If you get anything back (other than "Command(s) completed successfully") post the entire message to this post.




Microsoft Certified Master - SQL Server 2008
Follow me on twitter: @keith_tate

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1533135
Posted Wednesday, January 22, 2014 9:41 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, April 10, 2014 9:50 AM
Points: 40, Visits: 1,092
Run DBCC CHECKDB on the user database? I just wonder why the error message refers to the tempdb.mdf file.
Post #1533731
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse