Ask your sa to run some disk and controller diagnostics on the
volume/controller that supports the LUN that tempdb is on. Also check
the System Event Log(s) and look for disk/controller/io errors.

Sounds like bad hardware to me...

-----Original Message-----
From: Schauss Peter
[mailto:mssqldba-ezmlmshield-x78837463.[Email address protected]
Sent: Friday, June 30, 2006 12:00 PM
To: LazyDBA Discussion
Subject: Error 823

My environment: SQL Server 2000 sp4 (8.00.2040) on Windows 2003.

From time to time our Integrity Check job (generated by the Maintenance
Wizard) fails with the following errors in the event log:

Sort read failure (bad page ID). pageid = (0x1:0x59e1), dbid = 2, file =
g:\MSSQL\data\tempdb.mdf. Retrying.

Error: 823, Severity: 24, State: 7

I/O error (bad page ID) detected during read at offset 0x0000000b3c2000
in file 'g:\MSSQL\data\tempdb.mdf'..

The Microsoft Knowledge Base suggests that this is due to i/o errors.
Does this mean that our disk or some related component is about to fail?
What should I ask our Windows SA to check?

Thanks,
Peter Schauss



---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY Website :
http://www.LazyDBA.com To unsubscribe:
http://www.lazydba.com/unsubscribe.html




---------------------------------------------------------------------------------------------------
NOTICE OF CONFIDENTIALITY
The information contained in this communication and any accompanying document(s) is proprietary and confidential and is intended solely for the above-named individual or entity. If you are not the intended receiver, recipient or entity, you are advised that any distribution, copying, disclosure or communication of this email is strictly prohibited. If you have received this email in error, please contact me at the telephone number listed above or 858.716.1500.
==============================================================================


MS Sql Server LazyDBA home page