January 30, 2004 at 3:04 am
Hi,
Iām dealing with some kind of ghost process inside my SQL*Serve instance.
The process comes from a windows desktop and contains a select to a linked Oracle Server.
All connections from this desktop to the SQL*server are stopped (we already did a reboot of the client) but the process is still there.
A kill of this process was also unsuccessful. The only result was that the command is changed into killed/Rollback (see result of sp_who2 54)
54 RUNNABLE BELGACOM\id041 BGC-DBS01 . master KILLED/ROLLBACK 531 72 01/27
-------------- ---------- -----------------------------------------------------------------
Language Event 0 exec master..sp_tables_ex N'AEBP' , null, null, null, '''TABLE'''
Who can I get rid of this without restarting the SQL*Server instance, can some one please help me?
January 30, 2004 at 9:53 am
It should go away once the rollback is complete. Can you kill the like process on the oracle side?
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
February 2, 2004 at 1:02 am
If it stays in rollback-state to long according to your expectation, you may need to stop and start your sqlserver-instance.
(I've had to do this frequently because some of my users used msaccess to update some tables, and for whatever reason, their connection got into rollback-state, blocking other users to do their thing)
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution š
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply