Error: 823, Severity: 24, State: 2 Disk I/O error

Question

Error: 823, Severity: 24, State: 2 Disk I/O error

Andrew W

SSC Veteran

Points: 204
More actions
September 18, 2005 at 7:20 pm

#95245

Hi Everyone,
I have a client who is running SQL Server 2000 8.0.0.194 on a SBS 2k sp4 box. The SQL Server error logs are displaying the above error on 1 database and an event for this is being written to the application log.
I run a dbcc check db command and 69 consistency errors are reported.
I thought that this was serious so I got the client to create a backup of the database and send it in on cd so I can analyse it in-house.
When I restored the database into my SQL Server and did another dbcc checkdb, 0 errors are returned on the database. This is suggesting that the error is environmental.
I remoted into their server and noticed that there was minimal HDD space on c (about 212 meg) where the pagefile was located. The data file that is reporting error is on drive d which has adequate space ~5gig.
I have made a suggestion to their IT staff that before we can move forward with this, we need to free up drive c space, and/or move the pagefile to a drive that has enough space. No event is being written about not being able to write to pagefile.
I have also recommended that they apply SQL Server SP4 re this article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;826433
I am just wondering if anyone here has had experience with not being able to replicate this issue outside of the environment, and if it would be likely that if we apply the service pack and free up space for the pagefile that it would go away. I don't see why these errors would need to be repaired if I they are removed when the db is taken out of the environment.
I have read another article here in which they a repair the error, but it doesn't seem to apply in my case.
Any suggestions would be appreciated
Thanks in advance,
Andrew.

Viewing 3 posts - 1 through 3 (of 3 total)

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

Rudyx - the Doctor SSC-Forever Points: 43695 More actions · Answer 1

For starters, you are executing the RTM version (original CD installation, with no service packs). Upgrading to SP4 may or may not be advisable. You defintely want to search this sight. There are a number of threads concerning 'issues' or potential 'issues' with SP4. You will have to determine if any are relevant in your case. At a minimum I'd suggest SP3a and possibly 'hot fix' 818 (it's a security thing). Also while you have the server for maintenance I'd also run Windows Update for the OS to get all of the latest and greatest 'fixes' for W2K SP4 as well. (you're probably looking at at least 2 reboots). The first for the new windows installer, then as many as are called for after that.

Now back to one of your original questions. Freeing up space on the C: drive and moving the pagefile. Yes you should definitely free up space on the C: drive. Moving the pagefile has a couple of ramifications. First and foremost, another reboot. Second, if you ever need a memopry dump for MS PSS you will not get one unless you have a pagefile on the C: drive.

RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

Andrew W SSC Veteran Points: 204 More actions · Answer 2

Thanks for the reply rudy,

I should've made it clear that I will not be responsible for the implentation and investigation of possible issues that may or may not arise from the application of any service packs or pagefile location.

My main concern and questions was if anyone has come across the scenario explained in my original post where if the db was taken out of the enviroment, the consistency errors are no longer reported.

Suggestions on how I would resolve this issue within this environment once space is freed up and service packs are applied are very welcome, as I don't see the need to run a dbcc checkdb with repair_allow_data_loss in this case.

Thanks

Andrew.