com.solarmetric.jdbc.ReportingSQLException

[IBM][CLI Driver] CLI0114E Datetime field overflow. SQLSTATE=22008 {prepstmnt 17678065 INSERT INTO COR.T_PROJECTCOST (AMOUNT_F, APPROVALINFO_VC, BILLABLE_B, DATE_DT, DESCRIPTION_VC, ID_I, NAME_VC, PROJECTCOSTTYPE_ID_I, PROJECT_ID_I, ROWVERSION_I) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [reused=0]} [code=-99999, state=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 web49

  • via Oracle Community by 3004, 11 months ago
    [IBM][CLI Driver] CLI0114E Datetime field overflow. SQLSTATE=22008 {prepstmnt 17678065 INSERT INTO COR.T_PROJECTCOST (AMOUNT_F, APPROVALINFO_VC, BILLABLE_B, DATE_DT, DESCRIPTION_VC, ID_I, NAME_VC, PROJECTCOSTTYPE_ID_I, PROJECT_ID_I, ROWVERSION_I) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [reused=0]} [code=-99999, state=22008]
  • via Oracle Community by 3004, 2 weeks ago
    .default_billingcode_id_i, t1.duedate_dt, t1.modifiedby_person_id_i, t1.percentcomplete_f, t1.priority_id_i, t1.projectedstartdate_dt, t1.snapshotdate_dt, t1.status_id_i, t1.task_id_i FROM cor.t_task t0 INNER JOIN cor.t_tasksnapshot t1 ON t0.id_i = t1.task_id_i WHERE t0.project_id_i = ? [reused=2]} [code=0, state=HY000]
  • via Oracle Community by 3004, 1 week ago
    Unknown column 'Infinity' in 'field list' {prepstmnt 10808772 INSERT INTO variablesimple (ACTIVITYID, DIMENSION, IDENTIFIER, JDOID, MAXVALUE, MINVALUE, NAME0, SUCCESSIVEVALUES_JDOID, VARIATIONMODE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) [reused=0]} [code=1054, state=42S22]
  • Stack trace

    • com.solarmetric.jdbc.ReportingSQLException: [IBM][CLI Driver] CLI0114E Datetime field overflow. SQLSTATE=22008 {prepstmnt 17678065 INSERT INTO COR.T_PROJECTCOST (AMOUNT_F, APPROVALINFO_VC, BILLABLE_B, DATE_DT, DESCRIPTION_VC, ID_I, NAME_VC, PROJECTCOSTTYPE_ID_I, PROJECT_ID_I, ROWVERSION_I) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [reused=0]} [code=-99999, state=22008] at com.solarmetric.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:67) at com.solarmetric.jdbc.LoggingConnectionDecorator.access$400(LoggingConnectionDecorator.java:19) at com.solarmetric.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:649) 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.