Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Database in Recovery Pending State


Database in Recovery Pending State

Author
Message
john.danley
john.danley
Valued Member
Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)

Group: General Forum Members
Points: 56 Visits: 343
iqbal1258 (10/19/2011)
Hey Guys Nothin to do....

Chek firs mdf and ldf is exist or not..
if exist run below coommand on master DB


ALTER DATABASE 'DATBASE NAME' SET OFFLINE WITH ROLLBACK IMMEDIATE
ALTER DATABASE 'DATBASE NAME' SET ONLINE WITH ROLLBACK IMMEDIATE



Funny you should post this today. I was asked to help with a similar issue this morning. DB would not come online posting error - insufficient disk space or memory. There was plenty of disc space, but memory was a bit over-taxed. One thing I did note was the ldf was 2+ times larger than the mdf at around 58GB which raises other flags. I ended up doing just this, setting the db offline then online. It took over an hour to come up, but did succeed and we were back in business after doing a little clean-up on the DB.
jswong05
jswong05
Valued Member
Valued Member (65 reputation)Valued Member (65 reputation)Valued Member (65 reputation)Valued Member (65 reputation)Valued Member (65 reputation)Valued Member (65 reputation)Valued Member (65 reputation)Valued Member (65 reputation)

Group: General Forum Members
Points: 65 Visits: 476
I had all databases in "recovery pending" not because of disks nor memory. It was from SQL Server upgrade running into an error. The error was caused by 3rd party software had customized SSRS config (non-microsoft tags in rsreportserver.config). I removed the cause, upgraded the database instance, remove the databases (make sure you don't damage all the data and log files), re-attach them back. Violla, they are working again like brand new.

Jason
http://dbace.us
:-P
ksrikanth77
ksrikanth77
SSC Journeyman
SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)

Group: General Forum Members
Points: 77 Visits: 249
Goodmorning,

We had a same issue when one of our VM had a problem with the drives and had some maintnenace, but it was resolved after a restart. However there is also a workaround which worked for me through GUI jus change the Recovery model to simple from or vice versa, this will resolve the issue.

Regards
Srikanth Reddy Kundur
dineshvishe
dineshvishe
Valued Member
Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)

Group: General Forum Members
Points: 68 Visits: 342
I had tried but it showing in restoring state...
jayantj
jayantj
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 5
Thanks Its working For me
shankar.gurav
shankar.gurav
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 9
Check this,

This might help
http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/835dee9b-0993-433f-baf7-a646dfa7f8f7
dwe71
dwe71
Grasshopper
Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)

Group: General Forum Members
Points: 10 Visits: 35
Thanks a lot - restarting the service worked for me. Still no idea why this happened, unless maybe I forgot to detach the database last time I opened SQL Server Management Studio, and/or used it in database view in Visual Studio in the meantime.
The service name for me was "MSSQL$SQLEXPRESS", with a display name "SQL Server (SQLEXPRESS)".
Cheers
David.
ericjorg
ericjorg
Grasshopper
Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)

Group: General Forum Members
Points: 18 Visits: 40
I had this issue on Sql 2012 and fixed it this way:

1) Stop SQL
2) Delete the recovering database's log file
3) Start SQL
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47305 Visits: 44392
ericjorg (4/9/2013)
I had this issue on Sql 2012 and fixed it this way:

1) Stop SQL
2) Delete the recovering database's log file
3) Start SQL


Good way to destroy a database...
http://sqlinthewild.co.za/index.php/2009/06/09/deleting-the-transaction-log/


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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


ericjorg
ericjorg
Grasshopper
Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)

Group: General Forum Members
Points: 18 Visits: 40
GilaMonster (4/9/2013)

Good way to destroy a database...
http://sqlinthewild.co.za/index.php/2009/06/09/deleting-the-transaction-log/


Yes, that is exactly right. In my case, this was a test database and the logfile was created in a different version of SQL server, so it was safe to wipe it out.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search