SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Database in Recovery mode from last 7 days.


Database in Recovery mode from last 7 days.

Author
Message
parminder.parmindersingh
parminder.parmindersingh
Forum Newbie
Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)

Group: General Forum Members
Points: 6 Visits: 250
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.....(:
anthony.green
anthony.green
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10462 Visits: 6378
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
When a question, really isn't a question - Jeff Smith
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


Suresh B.
Suresh B.
SSCrazy
SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)

Group: General Forum Members
Points: 2040 Visits: 5326
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
GilaMonster
GilaMonster
SSC Guru
SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)

Group: General Forum Members
Points: 91685 Visits: 45285
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, 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


GilaMonster
GilaMonster
SSC Guru
SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)

Group: General Forum Members
Points: 91685 Visits: 45285
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, 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


SQLQuest29
SQLQuest29
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1118 Visits: 4324
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 :-)
hemanth.damecharla
hemanth.damecharla
Mr or Mrs. 500
Mr or Mrs. 500 (508 reputation)Mr or Mrs. 500 (508 reputation)Mr or Mrs. 500 (508 reputation)Mr or Mrs. 500 (508 reputation)Mr or Mrs. 500 (508 reputation)Mr or Mrs. 500 (508 reputation)Mr or Mrs. 500 (508 reputation)Mr or Mrs. 500 (508 reputation)

Group: General Forum Members
Points: 508 Visits: 324
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 Smooooth ~Hemanth
anthony.green
anthony.green
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10462 Visits: 6378
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
When a question, really isn't a question - Jeff Smith
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


parminder.parmindersingh
parminder.parmindersingh
Forum Newbie
Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)

Group: General Forum Members
Points: 6 Visits: 250
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.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)SSC Guru (91K reputation)

Group: General Forum Members
Points: 91685 Visits: 45285
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, 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


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