we use Toplink (TopLink - 4.6.0 (Build 417) with a DB2 Database 7.2. i
know really old versions, but we could change to e newer one ;-)
Sometimes we got some problems with update or insert statements --
numeric value out of range. The SQL statements should be right. We
took the statements and we tried to execute it manually. It works...
in our programm sometimes it crashed and we get a Database Exception:
CLI0111E Numeric value out of range
i will attach the stacktrace, perhaps somebody cna help us....
EXCEPTION [TOPLINK-4002] (TopLink - 4.6.0 (Build 417)):
com.webgain.integrator.exceptions.DatabaseException
EXCEPTION DESCRIPTION: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI
Driver] CLI0111E Numeric value out of range. SQLSTATE=22003
INTERNAL EXCEPTION: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver]
CLI0111E Numeric value out of range. SQLSTATE=22003
ERROR CODE: -99999
at
com.webgain.integrator.exceptions.DatabaseException.sqlException(Unknown
Source)
at
com.webgain.integrator.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(Unknown
Source)
at
com.webgain.integrator.internal.databaseaccess.DatabaseAccessor.executeNoSelect(Unknown
Source)
at
com.webgain.integrator.internal.databaseaccess.DatabaseAccessor.executeCall(Unknown
Source)
at
com.webgain.integrator.publicinterface.UnitOfWork.executeCall(Unknown
Source)
at
com.webgain.integrator.internal.queryframework.CallQueryMechanism.executeCall(Unknown
Source)
at
com.webgain.integrator.internal.queryframework.CallQueryMechanism.executeCall(Unknown
Source)
at
com.webgain.integrator.internal.queryframework.CallQueryMechanism.insertObject(Unknown
Source)
at
com.webgain.integrator.internal.queryframework.StatementQueryMechanism.insertObject(Unknown
Source)
at
com.webgain.integrator.internal.queryframework.DatabaseQueryMechanism.insertObjectForWrite(Unknown
Source)
at
com.webgain.integrator.queryframework.InsertObjectQuery.executeCommit(Unknown
Source)
at
com.webgain.integrator.internal.queryframework.DatabaseQueryMechanism.performUserDefinedWrite(Unknown
Source)
at
com.webgain.integrator.internal.queryframework.DatabaseQueryMechanism.performUserDefinedInsert(Unknown
Source)
at
com.webgain.integrator.internal.queryframework.DatabaseQueryMechanism.insertObjectForWrite(Unknown
Source)
at
com.webgain.integrator.queryframework.WriteObjectQuery.executeCommit(Unknown
Source)
at
com.webgain.integrator.internal.queryframework.DatabaseQueryMechanism.executeWrite(Unknown
Source)
at
com.webgain.integrator.queryframework.WriteObjectQuery.execute(Unknown
Source)
at
com.webgain.integrator.queryframework.DatabaseQuery.execute(Unknown
Source)
at
com.webgain.integrator.publicinterface.Session.internalExecuteQuery(Unknown
Source)
at
com.webgain.integrator.publicinterface.UnitOfWork.internalExecuteQuery(Unknown
Source)
at
com.webgain.integrator.publicinterface.Session.executeQuery(Unknown
Source)
at
com.webgain.integrator.publicinterface.Session.executeQuery(Unknown
Source)
at
com.webgain.integrator.internal.sessions.CommitManager.commitAllObjects(Unknown
Source)
at
com.webgain.integrator.publicinterface.Session.writeAllObjects(Unknown
Source)
at
com.webgain.integrator.publicinterface.UnitOfWork.commitToDatabase(Unknown
Source)
at
com.webgain.integrator.publicinterface.UnitOfWork.commitRootUnitOfWork(Unknown
Source)
at com.webgain.integrator.publicinterface.UnitOfWork.commit(Unknown
Source)
THe data is larger than the field def. Could be a data problem, DB2
field def or a host variable.
Because the SQL run manually works, I would think that there is a
problem with the data. The other possibility is that the data values
have grown and the field def needs to be expended.
Good Luck,
Penn