Skip to main content

An error occurred during recovery, preventing the database 'msdb' from restarting


After many force restarts my laptop the MSDB database decided to that it was time and  let the owner know of the harassment and didn’t want come back up.

 

The error log read as following

An error occurred during recovery, preventing the database 'msdb' (database ID 4) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.

 

Solution

Following is a step by step guide to bring the database back online

  

1.       Put MSSQL into single user mode

1.       Click START ; Microsoft SQL Server 2005 Configuration Tools ; SQL Server Configuration Manager

2.       Right click on SQL Server and choose Properties

3.       Click on the Advanced tab. Under Startup Parameters you will be adding the following parameters to the beginning of the string: -m;-c;-T3608



 

2.       Restart SQL Server

3.       Connect to SQL server through the Management Console. From this point on we will be using TSQL to issue the commands so click the New Query button on the top left. At this point you should be in the master database inside the query window.

4.       Make sure the SQL Agent is down

5.       Login using the DAC connection

Note : if not in as DAC you will get the following message ( if not in sigle user mode)

Cannot detach an opened database when the server is in minimally configured mode.
 
6.       Detach the MSDB database using the following commands:
use master
go
sp_detach_db ‘msdb’
go
and click Execute

7.       We need to move (or rename, I prefer moving them) the existing MDF and LDF files for the MSDB database so that we can recreate it.

1.       Usually these files are located in the following directory:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
Your’s might differ.

2.       Move (or rename) the MSDBDATA.mdf and MSDBLOG.ldf files.

8.       Back to the Management Studio. Open up the instmsdb.sql file in a new query window. This file is usually located in the following directory:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install

9.       Execute the file. If you see any errors about xp_cmdshell, just ignore them. They are common and the script will take care of it.

10.   At this point you should have your MSDB database restored. The only thing left is cleanup.

11.   Execute the following command to make sure that xp_cmdshell is once again set to disable for security reasons:
EXEC sp_configure ‘show advanced options’, 1
GO
RECONFIGURE WITH OVERRIDE
GO
EXEC sp_configure ‘xp_cmdshell’, 0
GO
RECONFIGURE WITH OVERRIDE
GO

12.   Shutdown SQL Server

13.   Go back into your Startup Paremeters for your server in the SQL Server Configuration Manager and removed the -c;-m;-T3608 parameters we added earlier.

14.   Restart SQL Server

15.   If you have any SQL Server jobs and you need them recovered you will have to restore the MSDB database from a backup of the database

 

 

Reference 
- Many thanks to Rip’s Domain - http://rip747.wordpress.com/2008/05/26/rebulding-msdb-in-sql-server-2005/; I have added some extra steps for a seamless  transition
- http://msdn.microsoft.com/en-us/library/ms190737.aspx

Comments

Post a Comment

Popular posts from this blog

How To Execute A SQL Job Remotely

One of the clients needed its users to remotely execute a SQL job and as usual I picked this up hoping for a quick brownie point. Sure enough there was a catch and there was something to learn. Executing the job through SQLCMD was a no-brainer but getting it to execute on the remote machine was bit of challenge. On the coding Front 1    1.)     The bat file included the following code                 SQLCMD -S "[ServerName] " -E -Q "EXEC MSDB.dbo.sp_start_job @Job_Name = ' '[JobName]" 2    2.)     The Individual users were given minimum permissions  to execute the SQL job Ex. use msdb EXECUTE sp_addrolemember @rolename = 'SQLAgentOperatorRole', @membername = ' Domain\UserLogin ' At the client machine              This took a fair bit of time till our sysadmin got me an empty VM machine....
Post a Comment
Read more

Create a dacpac To Compare Schema Differences

It's been some time since i added anything to the blog and a lot has happened in the last few months. I have run into many number of challenging stuff at Xero and spread my self to learn new things. As a start i want to share a situation where I used a dacpac to compare the differences of a database schema's. - This involves of creating the two dacpacs for the different databases - Comparing the two dacpacs and generating a report to know the exact differences - Generate a script that would have all the changes How to generate a dacbpac The easiest way to create a dacpac for a database is through management studio ( right click on the databae --> task --> Extract data-tier-application). This will work under most cases but will error out when the database has difffrent settings. ie. if CDC is enabled To work around this blocker, you need to use command line to send the extra parameters. Bellow is the command used to generate the dacpac. "%ProgramFiles...
10 comments
Read more

High Watermarks For Incremental Models in dbt

The last few months it’s all been dbt. Dbt is a transform and load tool which is provided by fishtown analytics. For those that have created incremental models in dbt would have found the simplicity and easiness of how it drives the workload. Depending on the target datastore, the incremental model workload implementation changes. But all that said, the question is, should the incremental model use high-watermark as part of the implementation. How incremental models work behind the scenes is the best place to start this investigation. And when it’s not obvious, the next best place is to investigate the log after an test incremental model execution and find the implementation. Following are the internal steps followed for a datastore that does not support the merge statements. This was observed in the dbt log. - As the first step, It will copy all the data to a temp table generated from the incremental execution. - It will then delete all the data from the base table th...
4 comments
Read more