RE: lock held by in-doubt distributed transaction

Is tracking.tracked_lacosa_request a local table or remote?  If remote did
you check the dba_pending* views on the remote system.  The bug I was
thinking of showed entries in the pending views but your problem does not so
it is likely a different bug.
 
I checked metalink for the ORA-01591error and got around 47 hits.  I glanced
at a few but I did not see a perfect match.  I think you will need to open
an iTAR and get help directly from Oracle.  Please let the board know how
this is resolved.
 
HTH -- Mark D Powell --
 
-----Original Message-----
From: Tony.Adolph@xxxxxx [mailto:Tony.Adolph@xxxxxx]
Sent: Wednesday, February 09, 2005 3:37 AM
To: mark.powell@xxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx; oracle-l-bounce@xxxxxxxxxxxxx
Subject: RE: lock held by in-doubt distributed transaction



Hi Mark, 

Thanks for the feedback. I tried... 

SQL> alter session set "_smu_debug_mode" = 4; 

Session altered. 

SQL> exec dbms_transaction.purge_lost_db_entry('4.18.4935'); 
BEGIN dbms_transaction.purge_lost_db_entry('4.18.4935'); END; 

* 
ERROR at line 1: 
ORA-06510: PL/SQL: unhandled user-defined exception 
ORA-06512: at "SYS.DBMS_TRANSACTION", line 94 
ORA-06512: at line 1 

:-( 

Tony 



"Powell, Mark D" <mark.powell@xxxxxxx> 
Sent by: oracle-l-bounce@xxxxxxxxxxxxx 


02/08/2005 06:48 PM 


Please respond to
mark.powell@xxxxxxx



To
oracle-l@xxxxxxxxxxxxx 

cc

Subject
RE: lock held by in-doubt distributed transaction

        




I believe this is a bug.  The first solution I saw was support telling
people to convert their systems to using regular rollback segments but I
believe that you can issue ' alter session set "_smu_debug_mode" = 4; ' to
get around the problem.  I do not have the bug number so before you alter
your session you may want to check metalink on the hidden parameter.
HTH -- Mark D Powell --


-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Tony.Adolph@xxxxxx
Sent: Tuesday, February 08, 2005 11:55 AM
To: oracle-l@xxxxxxxxxxxxx
Cc: Maxim.Demenko@xxxxxx
Subject: lock held by in-doubt distributed transaction


Hi folks,
One of our developers has just reported this error after a simple select:

select COUNT(*) FROM tracking.tracked_lacosa_request
                             *
ERROR at line 1:
ORA-01591: lock held by in-doubt distributed transaction 4.18.4935

So I looked for the in doubt transaction as follows:

select * from dba_2pc_neighbors;

and

select * from dba_2pc_pending;

but both returned no rows.

I tried the same query and also get the same error.  I bounced the 
database (immediate) and still get the error and all the time with the 
same transaction id 4.18.4935.  I got the developers to bounce their jboss 
but no joy. 

I tried dbms_transaction.purge_lost_db_entry:

SQL> exec dbms_transaction.purge_lost_db_entry('4.18.4935');
BEGIN dbms_transaction.purge_lost_db_entry('4.18.4935'); END;

*
ERROR at line 1:
ORA-30019: Illegal rollback Segment operation in Automatic Undo mode
ORA-06512: at "SYS.DBMS_TRANSACTION", line 65
ORA-06512: at "SYS.DBMS_TRANSACTION", line 85
ORA-06512: at line 1

Any ideas folks?

Cheers
Tony

--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l





--
http://www.freelists.org/webpage/oracle-l

Other related posts: