COM.ibm.db2.jdbc.DB2Exception

[IBM][CLI Driver] CLI0114E Datetime field overflow. SQLSTATE=22008

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web216

  • via Oracle Community by 3004, 1 year ago
    [IBM][CLI Driver] CLI0114E Datetime field overflow. SQLSTATE=22008
  • via Google Groups by Pavanapuresan, 1 year ago
    [IBM][CLI Driver] CLI0113E An invalid datetime format was detected; that is, an invalid string representation or value was specified. SQLSTATE=22007
  • via Google Groups by anokun7, 1 year ago
    [IBM][CLI Driver] CLI0124E Invalid argument value. SQLSTATE=HY009
  • Stack trace

    • COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0114E Datetime field overflow. SQLSTATE=22008 at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(UnknownSource) at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(UnknownSource) at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(UnknownSource) at COM.ibm.db2.jdbc.app.DB2PreparedStatement.execute2(Unknown Source) at COM.ibm.db2.jdbc.app.DB2PreparedStatement.executeUpdate(UnknownSource) at com.solarmetric.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:361) at com.solarmetric.jdbc.PoolConnection$PoolPreparedStatement.executeUpdate(PoolConnection.java:374) at com.solarmetric.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:361) at com.solarmetric.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:361) at com.solarmetric.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:361) at com.solarmetric.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:645) at com.solarmetric.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:361) at kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java:164) at kodo.jdbc.runtime.PreparedStatementManager.flush(PreparedStatementManager.java:92) at kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:357) at kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:154) at kodo.jdbc.runtime.UpdateManagerImpl.flush(UpdateManagerImpl.java:72) at kodo.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:507) at kodo.runtime.DelegatingStoreManager.flush(DelegatingStoreManager.java:158) at kodo.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:412) at kodo.runtime.PersistenceManagerImpl.flushInternal(PersistenceManagerImpl.java:794) at kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:650) at kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69) at kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:422)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.