java.sql.SQLException: ORA-01861: literal does not match format string

Apereo Issues | Brad Johnson | 1 decade ago
  1. 0

    Like is done in RDBMServices, I think this SQL should have had "{ts " added to the beginning and "}" added to the end of the timestamp when the database supports it to allow it to work with our Oracle setup. I think the query should have looked like this: SELECT ENTITY_TYPE_ID, ENTITY_KEY, INVALIDATION_TIME FROM UP_ENTITY_CACHE_INVALIDATION WHERE 1 = 1 AND ENTITY_TYPE_ID = 5 AND INVALIDATION_TIME > '{ts 2003-01-15 08:29:45.638}' Here is the exception and other messages from the log: ============================== DEBUG [Thread-54] root.[] Jan/15 10:30:45 - RDBMInvalidCacheableEntityStore.primSelect(): SELECT ENTITY_TYPE_ID, ENTITY_KEY, INVALIDATION_TIME FROM UP_ENTITY_CACHE_INVALIDATION WHERE 1 = 1 AND ENTITY_TYPE_ID = 5 AND INVALIDATION_TIME > '2003-01-15 08:29:45.638' ERROR [Thread-54] root.[] Jan/15 10:30:45 - EXCEPTION: java.sql.SQLException: ORA-01861: literal does not match format string java.sql.SQLException: ORA-01861: literal does not match format string at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180) at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208) at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543) at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1451) at oracle.jdbc.ttc7.TTC7Protocol.fetch(TTC7Protocol.java:943) at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2119) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2324) at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:627) at org.apache.commons.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:162) at org.jasig.portal.concurrency.caching.RDBMCachedEntityInvalidationStore.primSelect(RDBMCachedEntityInvalidationStore.java:393) at org.jasig.portal.concurrency.caching.RDBMCachedEntityInvalidationStore.selectAfter(RDBMCachedEntityInvalidationStore.java:528) at org.jasig.portal.concurrency.caching.RDBMCachedEntityInvalidationStore.findAfter(RDBMCachedEntityInvalidationStore.java:196) at org.jasig.portal.concurrency.caching.ReferenceInvalidatingEntityCache.removeInvalidEntities(ReferenceInvalidatingEntityCache.java:205) at org.jasig.portal.concurrency.caching.ReferenceInvalidatingEntityCache.cleanupCache(ReferenceInvalidatingEntityCache.java:121) at org.jasig.portal.concurrency.caching.ReferenceEntityCache$CacheSweeper.run(ReferenceEntityCache.java:75) at java.lang.Thread.run(Thread.java:536) ERROR [Thread-54] root.[] Jan/15 10:30:45 - ReferenceInvalidatingEntityCache.removeInvalidEntries(): Problem retrieving Invalid Entities ORA-01861: literal does not match format string ==============================

    Apereo Issues | 1 decade ago | Brad Johnson
    java.sql.SQLException: ORA-01861: literal does not match format string
  2. 0

    Like is done in RDBMServices, I think this SQL should have had "{ts " added to the beginning and "}" added to the end of the timestamp when the database supports it to allow it to work with our Oracle setup. I think the query should have looked like this: SELECT ENTITY_TYPE_ID, ENTITY_KEY, INVALIDATION_TIME FROM UP_ENTITY_CACHE_INVALIDATION WHERE 1 = 1 AND ENTITY_TYPE_ID = 5 AND INVALIDATION_TIME > '{ts 2003-01-15 08:29:45.638}' Here is the exception and other messages from the log: ============================== DEBUG [Thread-54] root.[] Jan/15 10:30:45 - RDBMInvalidCacheableEntityStore.primSelect(): SELECT ENTITY_TYPE_ID, ENTITY_KEY, INVALIDATION_TIME FROM UP_ENTITY_CACHE_INVALIDATION WHERE 1 = 1 AND ENTITY_TYPE_ID = 5 AND INVALIDATION_TIME > '2003-01-15 08:29:45.638' ERROR [Thread-54] root.[] Jan/15 10:30:45 - EXCEPTION: java.sql.SQLException: ORA-01861: literal does not match format string java.sql.SQLException: ORA-01861: literal does not match format string at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180) at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208) at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543) at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1451) at oracle.jdbc.ttc7.TTC7Protocol.fetch(TTC7Protocol.java:943) at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2119) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2324) at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:627) at org.apache.commons.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:162) at org.jasig.portal.concurrency.caching.RDBMCachedEntityInvalidationStore.primSelect(RDBMCachedEntityInvalidationStore.java:393) at org.jasig.portal.concurrency.caching.RDBMCachedEntityInvalidationStore.selectAfter(RDBMCachedEntityInvalidationStore.java:528) at org.jasig.portal.concurrency.caching.RDBMCachedEntityInvalidationStore.findAfter(RDBMCachedEntityInvalidationStore.java:196) at org.jasig.portal.concurrency.caching.ReferenceInvalidatingEntityCache.removeInvalidEntities(ReferenceInvalidatingEntityCache.java:205) at org.jasig.portal.concurrency.caching.ReferenceInvalidatingEntityCache.cleanupCache(ReferenceInvalidatingEntityCache.java:121) at org.jasig.portal.concurrency.caching.ReferenceEntityCache$CacheSweeper.run(ReferenceEntityCache.java:75) at java.lang.Thread.run(Thread.java:536) ERROR [Thread-54] root.[] Jan/15 10:30:45 - ReferenceInvalidatingEntityCache.removeInvalidEntries(): Problem retrieving Invalid Entities ORA-01861: literal does not match format string ==============================

    Apereo Issues | 1 decade ago | Brad Johnson
    java.sql.SQLException: ORA-01861: literal does not match format string
  3. 0

    Problem with JBuilder2005 and Oracle 9i on Windows 2000 workstation

    Google Groups | 1 decade ago | nemrod2100
    java.sql.SQLException: ORA-00600: internal code error, arguments : [ttcgcshnd-1], [0], [], [], [], [], [], []
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    db:: 3.10::Unusual exception while running java jdbc- ORA-28000: the account is locked am

    hivmr.com | 8 months ago
    java.sql.SQLException: ORA-00600: internal error code, arguments: [ttcgcshnd-1], [0], [], [], [], [], [], []

  1. rp 1 times, last 2 weeks ago
26 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. java.sql.SQLException

    ORA-01861: literal does not match format string

    at oracle.jdbc.dbaccess.DBError.throwSqlException()
  2. oracle.jdbc.dbaccess
    DBError.throwSqlException
    1. oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
    1 frame
  3. oracle.jdbc.ttc7
    TTC7Protocol.fetch
    1. oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
    2. oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)
    3. oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1451)
    4. oracle.jdbc.ttc7.TTC7Protocol.fetch(TTC7Protocol.java:943)
    4 frames
  4. Oracle jdbc
    OracleStatement.executeQuery
    1. oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2119)
    2. oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2324)
    3. oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:627)
    3 frames