Solved

OLEDB Waittype, Status KILLED/ROLLBACK

Posted on 2004-10-14
1
1,119 Views
Last Modified: 2012-06-21
Hello,

I'm having 2 processed that have the Status KILLED/ROLLBACK, after a administrator killed these 2 sessions. The user aborted his application because it was taking to much time before it answered.
These connection where made over a OLEDB to a Oracle Database.

How can i clear/delete these 2 connections, because, even the oracle server is still reachable through the SQL server (in a select ....) the stored procedure that that application was calling/running is even in query analyzer not runnable. If you call that procedure the process hangs too.

Any idea/suggestion ??
0
Comment
Question by:HLEBOEUF
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 34

Accepted Solution

by:
arbert earned 125 total points
ID: 12315338
You can't.  Unfortunately, there are some transactions that remain (ghost transactions) after they're killed.  They usually don't go away until you restart the server or the SQL Service.
0

Featured Post

Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction SQL Server Integration Services can read XML files, that’s known by every BI developer.  (If you didn’t, don’t worry, I’m aiming this article at newcomers as well.) But how far can you go?  When does the XML Source component become …
For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Viewers will learn how to use the SELECT statement in SQL and will be exposed to the many uses the SELECT statement has.

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question