July 23, 2008 at 1:03 pm
Hi, I was hoping some of the experts out there could assist a new DBA with an issue I am having.
Last week one of the DB on my SQL 2k5 went suspect. I had to put the DB in emergency mode, and recover some data.
We did a restore of backup to a new db, and pointed our web application at it. Last night we attempted to restore
the old db, from a recent copy. We were able to get it back online, and working, however when we ran one of our SSIS packages
to upload data into a table (1.7 million rows) we started seeing this 823 error again on this DB Primary file. The error message we are receiving is
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:823
Date:7/23/2008
Time:11:51:13 AM
User:N/A
Computer:SERVER
Description:
The operating system returned error 1(Incorrect function.) to SQL Server during a write at offset 0x0000000213c000 in file 'I:\SQLDATA\our_net1.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.
DBCC is failing due to an issue in creating the db snapshot. Reporting a space issue, however I can not identify any drive or disk space issues that could be contributing. Only strange occurence is that I noticed the I:\SQLDATA\our_net1.mdf has grown incredible large. 7GB while it is normally in the 1 GB range. I have looked at MS KB 828339, and it infers this is more likely an OS issue then a HW issue. Any advice?
July 23, 2008 at 1:36 pm
Call PSS. You may have hardware issues, but you don't want to lose data. I'd suspend database activity and call PSS for now to diagnose the issues.
July 24, 2008 at 8:41 am
One of my customers had an 823 error last week. In that case the reason was that the server lost temporarily the connection with the iSCSI disks.
Check your system eventlog for any disk related errors or warnings.
[font="Verdana"]Markus Bohse[/font]
July 24, 2008 at 10:36 am
An 823 error is often indicative of hardware problems, especially considering the suspect database you had last week. 823 means that the OS issued a read on a page and the page could not be read
Check the system event log, see if there are any disk warnings. If you're running on a SAN, check the SAN error logs. What's the error that CheckDB's returning?
My recommendation - restore a backup to another server, checkDB the backup, make sure there's no lurking corruption, then do some disk checks on your primary machine. 823 tends to be one of those 'abandon all hope' error messages
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
July 26, 2008 at 8:18 am
Well we recovered to a new DB and the 823 error messages have stopped. We are not seeing any hardware error messages in the event logs. Checking of the disks have passed. No errors from the hardware agents either. I did notice that the firmware of array and controllers are out of date, along with the drivers. Looks like I will have to update them to get any support out of DELL should I have a hardware problem. DBCC check on my restored copy of DB reveals no problems.
Did I mention in my previous post that the 823 error contained a message operating system error 1,INVALID_FUNCTION?
Right now my plan is to update the drivers, do a through check on the array hardware and disks. If that passes I am going to create a new db on array, restore old db, and see if I can reproduce the condition running my SSIS package. Then I will probally call MS PSS if it re-occurs.
Since the 823 error message was triggered last time by a large upload of data into one of my tables, I am suspecting that the primary db file grew on to an area of disk that my have bad sectors / problems.
Does this sound reasonable?
July 26, 2008 at 9:34 am
Sounds like a good plan.
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
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply