how to kill distributed transactions?

--openmail-part-17d7f4ad-00000001

Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline

        ;Creation-Date="Wed, 20 Dec 2000 09:46:38 -0600" Content-Transfer-Encoding: 7bit

One of our developers was performing a data load yesterday, by doing an insert across a database link. His script aborted after loading only a few thousand rows, apparently due to a data issue of some sort. When the transaction didn't roll back after 45 minutes or so, we decided to kill the session on the destination database. This morning we discovered that it STILL hadn't rolled back... this time we killed the dedicated server process at the OS level (kill -9), and the transaction was rolled back in less than a minute.

While we eventually got the desired result, the process seems rather unwieldy (and couldn't be used with MTS connections, if I'm not mistaken). What's the proper way to kill this sort of transaction?

Thanx!

--

My employers like me, but not enough to let me speak for them.

Greg Norris
Sprint LTD Database Administration
Phone: 913.345.6628
Internet: gregory.t.norris_at_mail.sprint.com OpenMail: Norris, Gregory T.

--openmail-part-17d7f4ad-00000001--
Received on Wed Dec 20 2000 - 09:46:40 CST