AW: V$Transaction entry

  • From: Petr Novak <Petr.Novak@xxxxxxxxxxxx>
  • To: Remigiusz Sokolowski <remigiusz.sokolowski@xxxxxxxxxx>
  • Date: Fri, 18 Feb 2011 09:21:04 +0000

Hallo Remigiusz,

I dont think this is the same issue. Maybe similar  issue caused the DB to be 
not consistent. The Application Servers where shot down one day ago. From this 
time the entry remains in V$transaction.
I suppose the DB should be able after 24 hours to clear V$transaction or place 
an entry in dba_2pc_pending. But there is still no entry in dba_2pc_pending.

Best Regards,
Petr Novak

Von: Remigiusz Sokolowski [remigiusz.sokolowski@xxxxxxxxxx]
Gesendet: Freitag, 18. Februar 2011 09:50
Bis: Petr Novak
Cc: oracle-l@xxxxxxxxxxxxx
Betreff: Re: V$Transaction entry

Petr Novak pisze:
> Hi,
> I have following problem:
> update on table waits for lock (only one row tested) , there is no lock on 
> the table in v$LOCK, analyze table validate structure gets ORA-00054,
> no rows in db_2pc_pending or pending_sessions , but there is one day old  
> entry in V$TRANSACTION and V$LOCKED_OBJECT shows  lock held  by nonexistent 
> session.
> Is there some possibility  how to delete this entry from v$transaction 
> without restarting the DB ? with dbms_transaction  (I have no rights on it) ?
> Best Regards,
> Petr Novak

Petr, I am almost certain that few weeks ago You sent me few links of
which one was very valuable in clearing that thing.

In general this issue happens when timeout settings on transaction
manager are longer than distributed_lock_timeout.

According to the paper the transaction id shows in dba_2pc_pending after
it is recognized as transaction in-doubt, etc - just look at the paper

Pole nakazi

Remigiusz Sokolowski <remigiusz.sokolowski@xxxxxxxxxx>
pos   : DBA at DIiUSI
addr  : Nordea Bank Polska SA, Luzycka 6A Street, 81-537 Gdynia, Poland
phone : +48 58 667 17 43
mobile: +48 602 42 42 77

Other related posts: