4 Replies Latest reply: Mar 18, 2013 3:21 AM by 996039 RSS

    After lost connection to Db, row lock still preset in data table

      I am using Odp 11.2 on 11g database and I have simple .Net application which using OracleTransaction doing a simple update on one row in data table in database. After statement ExecuteNonQuery with update command and before application succeed to commits transaction (Transaction.Commit()), application server lost connection to database and update fails as expected.

      The problem:
      In database in table in specific row which was simple application tried to update is till present lock. In this example lock was present for about 35 minutes. Also in v$transaction there was still present mentioned transaction despite application was already closed.

      Is there some setting or job on database side that cleans lost transactions?
      What is solution to avoid that kind of locks in scenario that application could lost connection before commits or rollback pending work.