July 16, 2010 at 1:46 pm
I was updated an identity value on a table in my DB.
The drive the DB was on ran out of room.
I rebooted the server...and now my DB said it was 'In Recovery'
I let that finish...now it says "lock request time out period exceeded"
What can I do..this is production!
July 16, 2010 at 1:55 pm
Can you kill the offending spid?
July 16, 2010 at 1:58 pm
krypto69 (7/16/2010)
I was updated an identity value on a table in my DB.The drive the DB was on ran out of room.
I rebooted the server...and now my DB says 'In Recovery'
What can I do..this is production!
You shutdown the server in the middle of transaction. If you want everything get recovered, there will no other option than waiting to recover... You can check SQL Server Error Log to see the progress of recovery.
July 16, 2010 at 2:01 pm
Check Paul Randall's site - he has a lot of great posts about Recovery.
July 16, 2010 at 2:03 pm
I waited for the server to get out of recovery..which it did..
But when I expand on anything I get the "lockout time out period exceeded" error 1222
I tried changing the timeouit setting in options..but no help...
there are no locks/blocks
July 16, 2010 at 2:12 pm
Can you find the spid assigned to your transaction? select * from sysprocesses or better yet if you are in 2005
SELECT * FROM
(SELECT QS.*,
SUBSTRING(ST.text, (QS.statement_start_offset/2) + 1,
((CASE statement_end_offset
WHEN -1 THEN DATALENGTH(ST.text)
ELSE QS.statement_end_offset END
- QS.statement_start_offset)/2) + 1) AS statement_text
FROM sys.dm_exec_query_stats AS QS
CROSS APPLY sys.dm_exec_sql_text(QS.sql_handle) as ST) as query_stats
Look at the Text and see where your task is assigned and kill it.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply