Lockheld in by In-doubt transaction [message #466447] |
Mon, 19 July 2010 13:05 |
paranidharan
Messages: 6 Registered: July 2010 Location: Chennai
|
Junior Member |
|
|
In my web application i am getting an error @ a particular page. I am using JTA user transaction to mark the transaction boundaries. On commit i am confronting the error "lock held in by In-Doubt transaction. I queried pending_trans$,dba_2pc_pending and force commit the transaction.Also i purged the transaction using Purge_Lost_db_entity. Still after doing all these i am facing the same problem with the new transaction no. What is the solution to this.. Can anyone help me out in this...
|
|
|
|
|
|
|
|
|
Re: Lockheld in by In-doubt transaction [message #466585 is a reply to message #466581] |
Tue, 20 July 2010 04:07 |
paranidharan
Messages: 6 Registered: July 2010 Location: Chennai
|
Junior Member |
|
|
I did follow the below steps:
SELECT * FROM PENDING_TRANS$
SELECT
LOCAL_TRAN_ID, GLOBAL_TRAN_ID, STATE, MIXED, HOST, COMMIT#
FROM
DBA_2PC_PENDING
WHERE
LOCAL _TRAN_ID = '??.';
SELECT LOCAL_TRAN_ID, IN_OUT, DATABASE, INTERFACE
FROM DBA_2PC_NEIGHBORS;
COMMIT FORCE 'local transactionID', 'SCN';
DBMS_TRANSACTION.PURGE_LOST_DB_ENTRY (local transactionID); OR
DBMS_TRANSACTION.PURGE_MIXED (local transactionID);
SELECT s.inst_id,
s.sid,
s.serial#,
p.spid,
s.username,
s.program
FROM gv$session s
JOIN gv$process p ON p.addr = s.paddr AND p.inst_id = s.inst_id
WHERE s.type != 'BACKGROUND'
and s.program='JDBC Thin Client'
ALTER SYSTEM KILL SESSION '102,10' IMMEDIATE;
Database shutdown and restart doesnt work..
|
|
|
|
|
|
|