Hi,

I think Oracle has an "in-built "transaction isoation level of 2
trying to set the value to 5 gives an exception
just try it with isolation 2 and check for any exceptions are thrown

Regards
pradeep


>From: "dube, shachi" <shachi.dube@h...>
>Reply-To: "Enterprise Java Beans" <enterprise_java_beans@p...>
>To: "Enterprise Java Beans" <enterprise_java_beans@p...>
>Subject: [enterprise_java_beans] RE: error.
>Date: Tue, 10 Sep 2002 16:04:38 +0530
>
>Oracle uses optimistic concurrency. As a consequence, even with a setting 
>of
>TRANSACTION_SERIALIZABLE, Oracle does not detect serialization problems
>until commit time. Hence the message :
>java.sql.SQLException: ORA-08177: can't serialize access for this
>transaction
>Even if you use the TRANSACTION_SERIALIZABLE setting for an EJB, you may
>receive exceptions or rollbacks in the EJB client if contention occurs
>between clients for the same rows. To avoid these problems, make sure that
>the code in your client application catches and examines the SQL 
>exceptions,
>and take you take the appropriate action to resolve the exceptions, such as
>restarting the transaction.
>With WebLogic Server, you can set the isolation level for transactions to
>TRANSACTION_READ_COMMITTED_FOR_UPDATE for methods on which this option is
>defined. When set, every SELECT query from that point on will have
>FOR_UPDATE added to require locks on the selected data. This condition
>remains in effect until the transaction does a COMMIT or ROLLBACK.
>
>
>
>
> > -----Original Message-----
> > From: santanu.goswami@i...
> > [SMTP:santanu.goswami@i...]
> > Sent: Tuesday, September 10, 2002 3:53 PM
> > To: Enterprise Java Beans
> > Subject: [enterprise_java_beans] error.
> >
> > Hi,
> > Can anyone shed any light on the error ...
> >
> > [java.sql.SQLException: ORA-08177: can't serialize access for this
> > transaction]
> >
> > thanks
> > santanu
> >
>



_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com