Geek asks and answers

Failed to kill SQL server, status remains dead / rollback

I cannot kill some SQL Server Agent jobs. The status of the task continues to run, and the command remains in KILLED / ROLLBACK. The job makes requests to the OI PI system through the OLEDB server and Oracle. The only way I found to kill these jobs is to restart the SQL server (not the preferred method).

+5
source share
5 answers

I found the following article https://connect.microsoft.com/SQLServer/feedback/details/187192/openquery-to-linked-server-hangs-leaving-spid-with-open-tran-that-cannot-be-killed- then-templog-ldf-grows-without-limit-requires-sql-server-restart-on-production-servers

-, , openquery , SQL Server. , BReuter :

, BReuter 30.01.2007 2:21 * , .

:

1) , Microsoft OLEDB Provider Oracle, Oracle Provider for Oracle ( 9.2.0.4 - , ).

2) " ". , SQL, .

3) SQL 2005 SP1 W2K3, , OLEDB , . , Oracle OLEDB- (OraOLEDB) - . , MS DTC .

  • - > - >

  • →

    . - >

  • MSDTC → ( )

    . Network DTC Access - .

    . / - .

    . - Windows 2000.

    . XA - , OraOLEDB.

  • → - > - > DCOM

    . MSDAINITALIZE- >

  • "" ( )

    . → .

    . " ".

    . SQL Server " ".

    . " ". *

+3

, , , .

+1

OLEDB , , , SQL-,

i OPENQUERY , oracle, SharePoint, , , , ,

0

Transactions that get stuck in KILLED / ROLLBACK can be canceled by killing transactions on the local server. If the request is a cross server and you do not want to wait for a rollback, you need to go to the remote server and kill the transaction, as well as kill it on the local server.

This applies to any database system.

0
source

More articles:


All Articles