March 15, 2011 at 10:45 pm
Hi,
I am on sql 2005 9.0.4285
I got to work this morning and got complaints that noone could use the system. I found the following error in the log:
Found severity 22 state 1 error in the log. Inconsistency detected during an internal operation on database
I verified backups and failed over the database.
Anyway after further investigation I found in the default trace
2011-03-16 05:31:05.89 spid2s Error: 832, Severity: 24, State: 1.
2011-03-16 05:31:05.89 spid2s A page that should have been constant has changed (expected checksum: bf9b389b, actual checksum: ff98649d, database 13, file 'f:\databases\repstraining.mdf', page (1:67588)). This usually indicates a memory failure or other hardware or OS corruption.
Does anyone know what I should be looking at to progress on this problem? I saw mention of the problem being a scribbler.
March 15, 2011 at 11:59 pm
That's a memory-related error. It's saying that a page in memory has been changed when it should not. That's a nasty problem to have, hard to track.
It could be faulty memory chips. It could be either something that's in-process with SQL Server (extended proc, linked server driver, etc) or a kernal-level process that's scribbling over SQL's memory.
I strongly suggest you call Microsoft's Customer support and get them to help you out with this one.
http://sqlskills.com/BLOGS/PAUL/post/Dont-confuse-error-823-and-error-832.aspx
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
March 16, 2011 at 6:17 pm
thanks - I took your advice and got the boss to fork out the cash. Just waiting on microsoft to get back to me.
March 21, 2011 at 12:20 pm
Useful info available in KB http://support.microsoft.com/default.aspx?scid=kb;en-US;2015759
Let us know how you worked on this issue 🙂
March 24, 2011 at 5:33 pm
Thanks,
I did see that microsoft article while researching the issue.
After getting some support from microsoft about this issue. They had a look and said it was probably due to hardware issue. Our infrastructure guys found nothing though.
Microsoft checked event logs, sql logs, hardware config. The got me to run a sqliosim which showed nothing. They also got to check all firmware updates were up to date - which they were. After that they gave up and told me to run
DBCC TRACEON(2544, 2546, -1)
so that if it happened again I will have a full memory dump for them to look at. So at this point we restored the database back on the orginal server and failed back to the principal.
Just on a side note I read somewhere databases can be corrupted due to bad index maintenance - how does that happen?
March 24, 2011 at 11:36 pm
djordan 4543 (3/24/2011)
Just on a side note I read somewhere databases can be corrupted due to bad index maintenance - how does that happen?
Nope. Bugs (in SQL, in-process 3rd party tool or kernel-level stuff) or faulty hardware.
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