<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Administering
»
Database in Recovery mode from last 7 days.
23 posts, Page 1 of 3
1
2
3
»
»»
Database in Recovery mode from last 7 days.
Rate Topic
Display Mode
Topic Options
Author
Message
parminder.parmindersingh
parminder.parmindersingh
Posted Wednesday, February 06, 2013 11:49 PM
Forum Newbie
Group: General Forum Members
Last Login: Wednesday, April 03, 2013 6:10 AM
Points: 6,
Visits: 180
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
anthony.green
anthony.green
Posted Thursday, February 07, 2013 1:35 AM
SSCertifiable
Group: General Forum Members
Last Login: Friday, April 12, 2013 3:51 AM
Points: 5,075,
Visits: 4,831
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
Suresh B.
Suresh B.
Posted Thursday, February 07, 2013 7:46 AM
Ten Centuries
Group: General Forum Members
Last Login: Tuesday, April 30, 2013 5:59 AM
Points: 1,075,
Visits: 5,114
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
GilaMonster
GilaMonster
Posted Thursday, February 07, 2013 8:25 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 4:15 PM
Points: 37,651,
Visits: 29,903
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
GilaMonster
GilaMonster
Posted Thursday, February 07, 2013 8:31 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 4:15 PM
Points: 37,651,
Visits: 29,903
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
SQLQuest29
SQLQuest29
Posted Thursday, February 07, 2013 9:37 AM
Say Hey Kid
Group: General Forum Members
Last Login: Yesterday @ 9:32 PM
Points: 713,
Visits: 2,843
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,
Cheers !
"Never take life too seriously, nobody gets out of it anyways !
When your love and skills unite, expect a masterpiece !"
Post #1417193
hemanth.damecharla
hemanth.damecharla
Posted Thursday, February 07, 2013 12:03 PM
SSC-Addicted
Group: General Forum Members
Last Login: Wednesday, February 27, 2013 8:41 PM
Points: 448,
Visits: 320
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
anthony.green
anthony.green
Posted Friday, February 08, 2013 3:34 AM
SSCertifiable
Group: General Forum Members
Last Login: Friday, April 12, 2013 3:51 AM
Points: 5,075,
Visits: 4,831
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
parminder.parmindersingh
parminder.parmindersingh
Posted Friday, February 08, 2013 8:23 AM
Forum Newbie
Group: General Forum Members
Last Login: Wednesday, April 03, 2013 6:10 AM
Points: 6,
Visits: 180
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
GilaMonster
GilaMonster
Posted Friday, February 08, 2013 8:45 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 4:15 PM
Points: 37,651,
Visits: 29,903
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 »
23 posts, Page 1 of 3
1
2
3
»
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
