ORA-08177 problem (Serializable transactions)

For those who ventured too far - just hope they know their way back :)

Moderator: neilg

ORA-08177 problem (Serializable transactions)

Postby tharris » Tue Jan 04, 2005 5:11 am

Hi,
I keep getting Oracle 08177 errors on "long" running transactions like initial inventory load and trial balance against all accounts. I have read a lot about the "initrans" parameter for a table but there is confilicting information. Is it OK to run the Oracle database in "READ_COMMITED" isolation rather than "SERIALIZEABLE" isolation with Compiere?

Thank you for your help and I am really glad I found this forum.
Tom
tharris
 
Posts: 1
Joined: Tue Jan 04, 2005 5:01 am

Postby red1 » Tue Jan 04, 2005 6:35 am

Hi Tom,
Thanks for your compliments in the guestbook.

I m no Oracle fan, i mean ODBA, but from your message it seems to be a simple logical issue. In lieu of u getting more authoritative answers from the likes of www.searchoracle.com i will suggest u try both options on some backups. But seriously, searching in Oracle do come up with real answers. My humble apologies :cry:

red1
red1
Site Admin
 
Posts: 2760
Joined: Tue Jul 06, 2004 3:01 pm
Location: Kuala Lumpur, Malaysia

Cant serialize access for this transaction

Postby neilg » Mon Jun 20, 2005 4:33 am

I understand they did some work on fixing the serialize access for this transaction issue on the new version of Compiere 2.5.2c, if I understand the question correctly.
neilg
Regular
 
Posts: 141
Joined: Thu Jun 16, 2005 1:58 pm

DB.java - changes

Postby neilg » Mon Nov 28, 2005 8:10 pm

A colleague of mine made these changes to DB.java (for 2.5.1g) and it appears to be working:

Code: Select all
             {
                 // if (s_connectionRW.getTransactionIsolation() !=
Connection.TRANSACTION_SERIALIZABLE)
                     //
s_connectionRW.setTransactionIsolation(Connection.TRANSACTION_SERIALIZABLE);
                 // Martin to prevent cant serialize error
                 if (s_connectionRW.getTransactionIsolation() !=
Connection.TRANSACTION_READ_COMMITTED)
                   
  s_connectionRW.setTransactionIsolation(Connection.TRANSACTION_READ_COMMITTED);
             }
         }
neilg
Regular
 
Posts: 141
Joined: Thu Jun 16, 2005 1:58 pm


Return to Strictly Technical

Who is online

Users browsing this forum: No registered users and 2 guests

cron