Finishing service pack installation prohibited by corrupt database - by Stan Segers

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 628098 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 12/3/2010 12:52:36 PM
Access Restriction Public


When a seriously corrupted database is attached to an engine that undergoes a service pack upgrade, the engine will not become available until the corrupt database files are removed. Following sequence of events was observed from the SQL Error Log.

2010-12-03 21:02:07.34 spid7s      Error: 824, Severity: 24, State: 2.
2010-12-03 21:02:07.34 spid7s      SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:2064; actual 0:0). It occurred during a read of page (1:2064) in database ID 21 at offset 0x00000001020000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\some_database.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe 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.
2010-12-03 21:02:07.34 spid7s      Error: 912, Severity: 21, State: 2.
2010-12-03 21:02:07.34 spid7s      Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 824, state 2, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2010-12-03 21:02:07.35 spid7s      Error: 3417, Severity: 21, State: 3.
2010-12-03 21:02:07.35 spid7s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
Sign in to post a comment.
Posted by Lee [MSFT] on 2/26/2011 at 7:25 AM
Thank you Stan. We will add this scenario into evaluations for servicing robustness enhancements in a future release of SQL Server, however given the seriousness of this consistency-based page corruption, not much can be done as the files must be updated for the SP. With regard to the corrupted dataabse state, the comments in the log detailing what to look for in previous ERRORLOGs, recovering backups, et al are all that I can offer at this time.
Posted by Stan Segers on 2/18/2011 at 2:07 AM
Errorlog attached. .dmp or .mdmp files were not created.
Posted by Lee [MSFT] on 2/16/2011 at 11:08 AM
Stan, could you possibly attach the .dmp or .mdmp file, as well as all Engine ERRORLOG files? This will help us factor in this exact failure when evaluating a more robust (corrupted) database upgrade design in a future release.

Thank You
Microsoft SQL Server
Posted by Korhan [MSFT] on 2/11/2011 at 9:33 AM
Hello Stan,

Thank you very much for your feedback. We are investigating this issue and will contact you as appropriate.

Best regards,
Microsoft SQL Server