You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-user@db.apache.org by Matthew Baird <Ma...@motiva.com> on 2003/06/27 00:32:53 UTC

RE: DB2 Error - Can Anybody Help?

That's the "something happened that's so severe that you should call db2 service" error.

it appears to be happening during the execution of a batch. You could try turning off batch, although I think you may have to do that in code and recompile.

m

-----Original Message-----
From: Shane Mingins [mailto:shane.mingins@assureinternational.com]
Sent: Thursday, June 26, 2003 3:34 PM
To: 'OJB Users List'
Subject: DB2 Error - Can Anybody Help?


Hi

This is one of those "not sure how to describe the problem" problem *grin*

I have a set of tests in a TestCase that were displaying unusual behaviour.
One that failed when the entire case was run did not fail when executed
solely on its own.

So I changed the order and have found the following error:

.[org.apache.ojb.odmg.ObjectEnvelopeTable] ERROR: Commit on object level
failed for tx org.apache.ojb.odmg.TransactionImpl@82d37
[SQL0901] SQL system error.
java.sql.BatchUpdateException: [SQL0901] SQL system error.
	at
com.ibm.as400.access.AS400JDBCPreparedStatement.executeBatch(AS400JDBCPrepar
edStatement.java:988)


I have replicated the problem with other versions of OJB so no problem
there.

I then changed the database to MySQL and everything works fine.

I have searched the IBM site and a SQL0901 error can be caused by a range of
things, nothing I could see sparked any eureka moments.

It is my "gut" feeling that it is not anything to do with the actual
generated SQL but somehow the order in which they are being executed ...
like something has a lock on a table still???????

I am at a bit of a loss as to where to go to next.  

Has anybody come across this error with the AS400 and/or DB2?

Or can anyone point me in some direction to help me find out more info about
this?

TIA
Shane

Shane Mingins
Analyst Programmer
Assure NZ Ltd
Ph 644 494 2522



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

Re: DB2 Error - Can Anybody Help?

Posted by Armin Waibel <ar...@code-au-lait.de>.
----- Original Message -----
From: "Matthew Baird" <Ma...@motiva.com>
To: "OJB Users List" <oj...@db.apache.org>
Sent: Friday, June 27, 2003 12:32 AM
Subject: RE: DB2 Error - Can Anybody Help?


That's the "something happened that's so severe that you should call db2
service" error.

it appears to be happening during the execution of a batch. You could
try turning off batch, although I think you may have to do that in code
and recompile.
#####
when using CVS this could be done by set
batch-mode=false
then all setBatch(...) statements in code ignored.

If using rc3, get latest ConnectionManagerImpl from
CVS or patch setBatchMode-method to
     public void setBatchMode(boolean mode)
    {
        batchMode = mode && jcd.getBatchMode();
    }

regards,
Armin


m

-----Original Message-----
From: Shane Mingins [mailto:shane.mingins@assureinternational.com]
Sent: Thursday, June 26, 2003 3:34 PM
To: 'OJB Users List'
Subject: DB2 Error - Can Anybody Help?


Hi

This is one of those "not sure how to describe the problem" problem
*grin*

I have a set of tests in a TestCase that were displaying unusual
behaviour.
One that failed when the entire case was run did not fail when executed
solely on its own.

So I changed the order and have found the following error:

.[org.apache.ojb.odmg.ObjectEnvelopeTable] ERROR: Commit on object level
failed for tx org.apache.ojb.odmg.TransactionImpl@82d37
[SQL0901] SQL system error.
java.sql.BatchUpdateException: [SQL0901] SQL system error.
at
com.ibm.as400.access.AS400JDBCPreparedStatement.executeBatch(AS400JDBCPr
epar
edStatement.java:988)


I have replicated the problem with other versions of OJB so no problem
there.

I then changed the database to MySQL and everything works fine.

I have searched the IBM site and a SQL0901 error can be caused by a
range of
things, nothing I could see sparked any eureka moments.

It is my "gut" feeling that it is not anything to do with the actual
generated SQL but somehow the order in which they are being executed ...
like something has a lock on a table still???????

I am at a bit of a loss as to where to go to next.

Has anybody come across this error with the AS400 and/or DB2?

Or can anyone point me in some direction to help me find out more info
about
this?

TIA
Shane

Shane Mingins
Analyst Programmer
Assure NZ Ltd
Ph 644 494 2522



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


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