db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florin Vancea" <fvan...@maxiq.ro>
Subject Re: ORA-01002 when Oracle is i in serialised mode
Date Fri, 13 May 2005 14:27:24 GMT
I've seen that, but not with Torque.
In my case, it was the following sequence of operations:

one connection opened with DB
some statement performed outside transaction (using implicit commit mode)
transaction started
some select
Bang --> ORA-01002

My workaround was to close the connection and open it again at the same time
the transaction was started.

----- Original Message ----- 
From: <raphael.x.mankin@gsk.com>
To: "Apache Torque Users List" <torque-user@db.apache.org>
Sent: Friday, May 13, 2005 3:56 PM
Subject: ORA-01002 when Oracle is i in serialised mode


> We have been quite happily running an application based on Torque for
about
> a year now. Recently, we found what looked like a  bug in Oracle's
> transaction management. To work around this we changed the database mode
> from the default Oracle locking to SERIALIZABLE. We now cannot get Torque
> to do anything with the DB.
>
> The following code gives 'ORA-01002 fetch out of sequence'
>
> Criteria    crit  = new Criteria()
> List  l     = PersonPeer.doSelect(crit);
>
> Resetting the DB into Oracle's default locking mode clears the problem -
> but of course leaves us with the original transaction mgt problem.
>
>
> Any suggestions?
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org


Mime
View raw message