Hello everybody. One of my instances do not start. Five of them works as they should.
Event ID 824:
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x82337dac; actual: 0xd2682ea2). It occurred during a read of page (1:664) in database ID 4 at offset 0x00000000530000 in file 'E:\MSSQL11.FOLDERNAME\MSSQL\DATA\DBNAME.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.
Event ID 912:
Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 824, state 2, severity 24. 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.
Event ID 3417:
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.
If I start the instance with traceflag T902 it starts as normally so I think the master db is okay. Anybody passed by this problem before?
Try first restoring msdb system database, if it does not help restore a master database....
BTW, I see that one user database is having problems as well... Do you have latest good backup? What does DBCC CHECKDB on that db say?
Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Blog: Large scale of database and data cleansing
Remote DBA Services: Improves MS SQL Database Performance
But i dont think there is corruption in msdb . Corruption is there in master DB.It is possible that your Db was corrupted before it was upgraded to SP and CU AFAIK SP upgrade cannot cause database corruption.
Its best to restore master database with valid backup.Please before restoring check your master db backup consistency using below query (http://technet.microsoft.com/en-us/library/ms188902(v=sql.105).aspx)
restore verifyonly from disk='backuplocation'You can use this link for master db restore http://technet.microsoft.com/en-us/library/ms190679.aspx
Hey again. Thank you so much for the replies. I tried to restore msdb from successful SQL consistent backups as long back in time as was available. I even tried from two backup jobs since we have a 1Gbit network between sites and automatically stores both on-site and off-site backups. No luck. Did not want to restore every system database so I tried to use an empty msdb from another instance. That worked!!
I had to set up database mail and also backup and restore history is gone. Read more: http://technet.microsoft.com/en-us/library/ms187112.aspx
Service is up and running and all the application data is intact so when the end is good, all is good.
- Proposed as answer by Alberto MorilloMVP, Moderator Tuesday, September 17, 2013 10:51 AM