kodo.util.FatalDataStoreException

Oracle Community | 3004 | 1 decade ago
  1. 0

    setting isolation level fails

    Oracle Community | 1 decade ago | 3004
    kodo.util.FatalDataStoreException
  2. 0

    Mapping util.Date to Oracle timestamp

    Oracle Community | 1 decade ago | 3004
    kodo.util.FatalDataStoreException: The transaction has been rolled back. See the nested exceptions for details on the errors that occu rred.
  3. 0

    NPE with application managed id using remote pm

    Oracle Community | 1 decade ago | 3004
    kodo.util.FatalDataStoreException: null
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Using native sequencing while persisting an object that spans 2 tables

    Oracle Community | 1 decade ago | 3004
    kodo.util.FatalDataStoreException: ORA-02289: sequence does not exist {prepstmnt 9493 select JDOSEQUENCE.NEXTVAL from DUAL [reused=0]} [code=2289, state=42000]
  6. 0

    cannot write to the database

    Oracle Community | 1 decade ago | 3004
    kodo.util.FatalDataStoreException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.

    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. kodo.util.FatalDataStoreException

      No message provided

      at kodo.runtime.PersistenceManagerImpl.beforeCompletion()
    2. kodo.runtime
      PersistenceManagerImpl.commit
      1. kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:897)
      2. kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
      3. kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:566)
      3 frames