You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-user@db.apache.org by ra...@gsk.com on 2005/05/13 14:56:20 UTC
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
Re: ORA-01002 when Oracle is i in serialised mode
Posted by Thomas Fischer <fi...@seitenbau.net>.
Raphael,
which pool are you using ? I have tried to reproduce your issue using the
dbcp pool and am not able to get a serializable connection which is not in
auto-commit mode. If I set the transaction isolation to serializable and
leave auto-commit true, then I am not able to reproduce your issue (but I
do not see any point in this configuration)
I have used the following lines to configure this
torque.dsfactory.bookstore.pool.defaultTransactionIsolation = 8
torque.dsfactory.bookstore.pool.defaultAutoCommit = false
Not being able to get a serializable connection which is not auto-commit
seems a dbcp issue to me, but I have to dive deeper into that to be sure.
Thomas
"Raphael Mankin,,," <ra...@webwright-uk.com> schrieb am 13.05.2005 17:31:54:
>
> On 13-May-2005 Florin Vancea wrote:
> > 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 thesame
time
> > the transaction was started.
>
> Your solution will, of course, not work with torque, because of the
connection
> pooling.
>
> In my case, I have not got as far as starting any explicit transactions,
other
> than those Torque does for one. In my example, the pari of statements I
wrote
> will be a transaction all by themselves.
>
>
> I was really wondering whether this was a Torque problem, in which case
we
> can find a fix, or do I have to shout at Oracle, which is much more
difficult.
>
>
> >
> > ----- Original Message -----
> > From: <ra...@gsk.com>
> > To: "Apache Torque Users List" <to...@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
>
> --
> Lead us not into temptation; we
> can find our own way.
>
>
> Raphael Mankin
> ----------------------------------
>
> ---------------------------------------------------------------------
> 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
Re: ORA-01002 when Oracle is i in serialised mode
Posted by Raphael Mankin <ra...@mankin.org.uk>.
On 13-May-2005 Florin Vancea wrote:
> 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.
Your solution will, of course, not work with torque, because of the connection
pooling.
In my case, I have not got as far as starting any explicit transactions, other
than those Torque does for one. In my example, the pari of statements I wrote
will be a transaction all by themselves.
I was really wondering whether this was a Torque problem, in which case we
can find a fix, or do I have to shout at Oracle, which is much more difficult.
>
> ----- Original Message -----
> From: <ra...@gsk.com>
> To: "Apache Torque Users List" <to...@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
--
Lead us not into temptation; we
can find our own way.
Raphael Mankin
----------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org
Re: ORA-01002 when Oracle is i in serialised mode
Posted by Florin Vancea <fv...@maxiq.ro>.
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: <ra...@gsk.com>
To: "Apache Torque Users List" <to...@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