Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 123»»»

Database in Recovery mode from last 7 days. Expand / Collapse
Author
Message
Posted Wednesday, February 6, 2013 11:49 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, June 30, 2014 5:23 AM
Points: 6, Visits: 209
Hello,

Please any one can help me, how to recover databases or change status from in recovery to normal. i had go through all the articals which is suggested by google.

In SQL server error log shows below information, please suggest something in positive manner.

"2013-02-07 11:43:51.61 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4789 ms. Process Utilization 0%. System Idle 98%. Interval: 411390903 ms.
2013-02-07 11:44:51.70 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4789 ms. Process Utilization 0%. System Idle 98%. Interval: 411450994 ms.
2013-02-07 11:45:51.79 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4804 ms. Process Utilization 0%. System Idle 98%. Interval: 411511084 ms.
2013-02-07 11:46:51.88 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4804 ms. Process Utilization 0%. System Idle 98%. Interval: 411571175 ms.
2013-02-07 11:47:51.97 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4804 ms. Process Utilization 0%. System Idle 98%. Interval: 411631266 ms.
2013-02-07 11:48:52.06 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4804 ms. Process Utilization 0%. System Idle 98%. Interval: 411691357 ms.
2013-02-07 11:49:52.15 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4804 ms. Process Utilization 0%. System Idle 98%. Interval: 411751448 ms.
2013-02-07 11:50:52.24 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4804 ms. Process Utilization 0%. System Idle 98%. Interval: 411811539 ms."

Please help.....(:
Post #1416824
Posted Thursday, February 7, 2013 1:35 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Friday, July 25, 2014 9:12 AM
Points: 5,142, Visits: 4,930
What caused the database to go into recovery?

Someone restore the DB and not issue a RECOVERY command?
Someone backup the tail log and issues with NORECOVERY?

Restarted the SQL service?




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1416866
Posted Thursday, February 7, 2013 7:46 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, July 8, 2014 4:17 AM
Points: 1,101, Visits: 5,279
The message in the SQL Server log might not be related the database status.

Is the database Log-Shipped (Secondary Server)?

Following command is used to bring the database online:
RESTORE DATABASE <dbname> WITH RECOVERY
Post #1417078
Posted Thursday, February 7, 2013 8:25 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 2:38 AM
Points: 42,459, Visits: 35,519
Suresh B. (2/7/2013)
The message in the SQL Server log might not be related the database status.

Is the database Log-Shipped (Secondary Server)?

Following command is used to bring the database online:
RESTORE DATABASE <dbname> WITH RECOVERY


That's for a database in the RESTORING state, not for a database in the RECOVERING state.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1417112
Posted Thursday, February 7, 2013 8:31 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 2:38 AM
Points: 42,459, Visits: 35,519
anthony.green (2/7/2013)
Someone restore the DB and not issue a RECOVERY command?
Someone backup the tail log and issues with NORECOVERY?


Both result in the RESTORING state, not the RECOVERING state.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1417118
Posted Thursday, February 7, 2013 9:37 AM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Friday, July 25, 2014 9:43 AM
Points: 736, Visits: 3,689
parminder.parmindersingh (2/6/2013)
Hello,

Please any one can help me, how to recover databases or change status from in recovery to normal. i had go through all the articals which is suggested by google.

In SQL server error log shows below information, please suggest something in positive manner.

"2013-02-07 11:43:51.61 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4789 ms. Process Utilization 0%. System Idle 98%. Interval: 411390903 ms.
2013-02-07 11:44:51.70 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4789 ms. Process Utilization 0%. System Idle 98%. Interval: 411450994 ms.
2013-02-07 11:45:51.79 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4804 ms. Process Utilization 0%. System Idle 98%. Interval: 411511084 ms.
2013-02-07 11:46:51.88 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4804 ms. Process Utilization 0%. System Idle 98%. Interval: 411571175 ms.
2013-02-07 11:47:51.97 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4804 ms. Process Utilization 0%. System Idle 98%. Interval: 411631266 ms.
2013-02-07 11:48:52.06 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4804 ms. Process Utilization 0%. System Idle 98%. Interval: 411691357 ms.
2013-02-07 11:49:52.15 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4804 ms. Process Utilization 0%. System Idle 98%. Interval: 411751448 ms.
2013-02-07 11:50:52.24 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 62 ms, user 4804 ms. Process Utilization 0%. System Idle 98%. Interval: 411811539 ms."

Please help.....(:



Can you let us know --
What is the sql server version ?
Is there a dump file associated with the non-yielding scheduler ?



______________________________________________________________________________________________________________________________________________________________________________________
HTH !
Kin
MCTS : 2005, 2008
Active SQL Server Community Contributor
Post #1417193
Posted Thursday, February 7, 2013 12:03 PM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, March 18, 2014 1:42 AM
Points: 448, Visits: 322
Parminder,
Could you provide us some more information as to how the database went into recovering mode?

Are there any messages in the errorlog that say that the DB was shutdown? Do you see any disk I/O requests taking longer than 15 seconds kind of messages?

What do you see in exec_requests (or) sysprocesses? Anything interesting?

A little bit more information from your errorlog other than the non-yeilding scheduler messages would help the community understand your problem a little bit better.

Regards,


-Hope is a heuristic search ~Hemanth
Post #1417285
Posted Friday, February 8, 2013 3:34 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Friday, July 25, 2014 9:12 AM
Points: 5,142, Visits: 4,930
GilaMonster (2/7/2013)
anthony.green (2/7/2013)
Someone restore the DB and not issue a RECOVERY command?
Someone backup the tail log and issues with NORECOVERY?


Both result in the RESTORING state, not the RECOVERING state.


Doh..




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1417570
Posted Friday, February 8, 2013 8:23 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, June 30, 2014 5:23 AM
Points: 6, Visits: 209
I was shrinking a database, where its stuck and SSMS goes in not responding. I had wait till half an hour but no luck.
then i just went to the respective server and restart the SQL server service into the SQL Configuration management. When i came back to my pc and contact to server it shows 4 database "In Recovery" mode. I was shocked, because all my live databases. These all databases on SQL Server 2005 SP1.

And checked SQL error log got those details which i had posted on my earlier post. Please guide me, how i can make it correct.
Post #1417738
Posted Friday, February 8, 2013 8:45 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 2:38 AM
Points: 42,459, Visits: 35,519
The only thing you can do for a recovering database is wait. If the schedulers are still hung may require another restart, bear in mind that'll undo any recovery work that's already completed.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1417750
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse