November 16, 2005 at 9:23 am
Over the weekend a user ran an update command (Process 54) which was blocking another Process (59). On Monday, I identified the Blocking Lock. Then, I Killed Process 59 and attempted to Kill Process 54. After the Kill Command on Process 54, I noticed the status went to "Killed/Rollback". The status stayed like this for almost 2 hours. (Also, I noticed when I looked in the Locks / Process ID Folder under the Current Activity Folder in SQL EM, there were a ton of entries for Process 54. I only could Kill these entries one at a time.) This is when we decided to restart the Server. The Network Person said after 10 minutes of waiting for the server to shutdown/restart she finally pressed the off/on button. Do you think this (the database in rollback mode while the server is being turned off) would have had anything to do with putting the database in a "suspect" status? Would this have showed in the System Log or any other log?
In the Locks / Process ID Folder under the Current Activity Folder in SQL EM, there were a ton of entries for Process 54. Why were there so many entries for this one Process?
Thanks in advance, Kevin
November 16, 2005 at 3:08 pm
Hi
I am not sure about the correct answer but one of the potential reason for database in a suspect is torn pages. If there is power failure, any data pages corruption can cause a torn pages that would put the database in suspect.
November 16, 2005 at 3:24 pm
Your kill 54 probably needed 2+ hours to undo whatever it had done. Once you killed it, you can run "kill 54" again, and it will give you a progress update .... something like "Process 54 already rolling back. 27 % complete" (I don't remember the actual phrase). That will give you a bit of an idea of how long it will take. You should see the % change as you check it from time to time.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply