July 24, 2017 at 7:23 pm
Good Morning Experts,
One of our databases went into "Recovery Pending" Status. Could you please share the steps to fix it.
July 25, 2017 at 1:39 am
coolchaitu - Monday, July 24, 2017 7:23 PMGood Morning Experts,
One of our databases went into "Recovery Pending" Status. Could you please share the steps to fix it.
Recovery pending means that something is preventing the database being brought online. Do both your data and log files exist?
What happened before the database went into Recovery Pending? Did the server unexpectedly shut down?
Thanks
July 25, 2017 at 2:59 am
NorthernSoul - Tuesday, July 25, 2017 1:39 AMcoolchaitu - Monday, July 24, 2017 7:23 PMGood Morning Experts,
One of our databases went into "Recovery Pending" Status. Could you please share the steps to fix it.
Recovery pending means that something is preventing the database being brought online. Do both your data and log files exist?
What happened before the database went into Recovery Pending? Did the server unexpectedly shut down?Thanks
Both data and log files exist. The server unexpectedly shut down
July 25, 2017 at 3:05 am
coolchaitu - Tuesday, July 25, 2017 2:59 AMNorthernSoul - Tuesday, July 25, 2017 1:39 AMcoolchaitu - Monday, July 24, 2017 7:23 PMGood Morning Experts,
One of our databases went into "Recovery Pending" Status. Could you please share the steps to fix it.
Recovery pending means that something is preventing the database being brought online. Do both your data and log files exist?
What happened before the database went into Recovery Pending? Did the server unexpectedly shut down?Thanks
Both data and log files exist. The server unexpectedly shut down
Try re-starting SQL Server. It might have been that the service started before the disk was available following the reboot of the server.
Thanks
July 25, 2017 at 3:06 am
Before you restart, what messages are there related to the DB in the error log?
There will be messages in the error log saying why the DB couldn't recover. Always a good idea to investigate before trying random options.
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
July 25, 2017 at 3:21 am
GilaMonster - Tuesday, July 25, 2017 3:06 AMBefore you restart, what messages are there related to the DB in the error log?
There will be messages in the error log saying why the DB couldn't recover. Always a good idea to investigate before trying random options.
Hi Gail,
Thanks for your reply. Unfortunately, error log got truncated and there is nothing there
July 25, 2017 at 4:01 am
How does an error log get truncated?
Unless you've messed with the default settings, it should contain 6 older logs and the current one, and the recovery pending messages will be on the current one.
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
July 25, 2017 at 5:23 pm
GilaMonster - Tuesday, July 25, 2017 4:01 AMHow does an error log get truncated?
Unless you've messed with the default settings, it should contain 6 older logs and the current one, and the recovery pending messages will be on the current one.
No idea Gail. Looks like someone restarted SQL Server.
July 25, 2017 at 10:07 pm
coolchaitu - Tuesday, July 25, 2017 5:23 PMGilaMonster - Tuesday, July 25, 2017 4:01 AMHow does an error log get truncated?
Unless you've messed with the default settings, it should contain 6 older logs and the current one, and the recovery pending messages will be on the current one.No idea Gail. Looks like someone restarted SQL Server.
And someone deleted the error logs from the physical location. Could you please advise on fixing
July 26, 2017 at 1:19 am
Someone restarted the server and deleted old error logs?
If that was my server, I'd be talking it IT security at this point, as it smells like someone's trying to cover their tracks after doing something they shouldn't. Maybe HR and management too.
As for the DB, with no logs, restart SQL and hope it comes up. If it doesn't, check the error logs as to why.
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
July 26, 2017 at 7:54 am
GilaMonster - Wednesday, July 26, 2017 1:19 AMSomeone restarted the server and deleted old error logs?
If that was my server, I'd be talking it IT security at this point, as it smells like someone's trying to cover their tracks after doing something they shouldn't. Maybe HR and management too.As for the DB, with no logs, restart SQL and hope it comes up. If it doesn't, check the error logs as to why.
Thanks for replying Gail. Unfortunately this is a pre-prod server and we cannot restart it. Is there any other way, for e.g.bringing db in emergency mode or any other way.
July 26, 2017 at 12:55 pm
coolchaitu - Wednesday, July 26, 2017 7:54 AMGilaMonster - Wednesday, July 26, 2017 1:19 AMSomeone restarted the server and deleted old error logs?
If that was my server, I'd be talking it IT security at this point, as it smells like someone's trying to cover their tracks after doing something they shouldn't. Maybe HR and management too.As for the DB, with no logs, restart SQL and hope it comes up. If it doesn't, check the error logs as to why.
Thanks for replying Gail. Unfortunately this is a pre-prod server and we cannot restart it. Is there any other way, for e.g.bringing db in emergency mode or any other way.
Sure. Look in the error log and see why it's in that state.
Oh, you can't because someone restarted SQL and deleted the error log (and you really should be more worried about that)
Restart SQL, not the server, just the SQL service and see whether that fixes the DB.
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
October 13, 2017 at 12:51 am
This was removed by the editor as SPAM
October 13, 2017 at 12:51 am
This was removed by the editor as SPAM
October 13, 2017 at 1:33 am
(off
Johnson Welch - Friday, October 13, 2017 12:51 AMIn my case it helped to set it to "Local System" (as a workaround). Seems to be some rights issue. Here is how to recover database from recovery pending mode
That blog post is both wrong and dangerous. I would recommend anyone reading ignore it.
Emergency mode is for fixing suspect DBs, not recovery_pending (offline/online is sufficient if the root cause has been fixed), and if there really is something wrong with the DB, detaching it is a good way to ensure you never get it back.
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 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply