April 26, 2012 at 5:16 am
Hi I have killed one spid bu its still showing this KILLED/ROLLBACK status
Sugest me to resolve this with out restating the server please.....
[Foun a link here but it's not resolved my issue http://social.msdn.microsoft.com/forums/en-US/sqldatabaseengine/thread/71d3cd0b-ce4d-4202-8e3b-38b38da90a5b%5D
Thank you in Advance .
April 26, 2012 at 6:01 am
Wait. It's rolling back and has to finish the rollback. Don't restart SQL, that will just result in the rollback continuing after the restart, possibly with the database offline.
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
April 26, 2012 at 6:54 am
Thank you for replay
It's stil showing same. last four hours this is in same situation......
April 26, 2012 at 7:15 am
You have to wait for it to finish.
If you kill the process again it will show you the rollback completion % and estimated time.
What exactly was the process that you killed doing?
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
April 26, 2012 at 7:25 am
DBCC CheckDB (DBName , REPAIR_ALLOW_DATA_LOSS) .......
And event type is Language Event
Last wattype is LOGMGR
Thank you
April 26, 2012 at 7:27 am
Wait for it to finish the rollback.
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
April 26, 2012 at 7:31 am
OK Tahnk you. Will update the situation ....
April 26, 2012 at 10:02 am
Still this is in same state .....KILLED/ROLLBACK status
April 26, 2012 at 10:28 am
GilaMonster (4/26/2012)
You have to wait for it to finish.If you kill the process again it will show you the rollback completion % and estimated time.
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
April 27, 2012 at 5:58 am
Issue is still in same state.
1. DBCC OPENTRAN is showing this results....
Transaction information for database 'master'.
Oldest active transaction:
SPID (server process ID): 56
UID (user ID) : -1
Name : ChangeDbState
LSN : (628:376:1)
Start time : Apr 26 2012 10:49:29:140AM
SID : 0x01050000000000051500000079e3fc5354190e29be043e32823f0000
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
2. DBCC INPUTBUFFER (56)
DBCC CheckDB (QFM162RES14 , REPAIR_ALLOW_DATA_LOSS)
3. KILL 56
SPID 56: transaction rollback in progress. Estimated rollback completion: 0%. Estimated time remaining: 0 seconds.
Thank You
April 27, 2012 at 6:05 am
ive had this a few times and never got a sucessfull explanation for it ...
it normally happens to me if i'm running an xp in 2000 (such as xp_cmdshell) if the xp crashes sql2000 doesn't seem to want to do anything with it.
i've always had to reboot (despite searching for an eternity for the fix)
perhaps since then someone has found a fix
MVDBA
April 27, 2012 at 6:11 am
I also encounterd same issue we left the killed\rollback transaction for a weak but no progress at all than we decided to recycle the SQL services. After restart that spid was no more exist.
April 30, 2012 at 4:30 am
Thank you very much for all .....
Issue is resolved and Now This DB is up and running .........
http://www.sqlskills.com/BLOGS/PAUL/post/Do-transactions-rollback-when-DBCC-CHECKDB-runs.aspx
Krishna
April 30, 2012 at 4:52 am
krishnaprasad14 (4/30/2012)
Issue is resolved and Now This DB is up and running .........
That's talking about the snapshot creation upon running a normal checkDB. If you run checkDB with any of the repair operations and cancel that, it really does have to roll back any of the repairs it did.
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
April 30, 2012 at 6:23 am
There's a good chance that when a "rollback" hangs up like this, that it's waiting on something in another spid to complete. It's sometimes difficult to find but you need to find that spid and kill it in order for the spid you killed to complete its rollback.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 15 posts - 1 through 15 (of 22 total)
You must be logged in to reply to this topic. Login to reply