kodo.util.FatalDataStoreException: ORA-01453: SET TRANSACTION must be first statement of transaction

Oracle Community | 3004 | 1 decade ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    setting isolation level fails

    Oracle Community | 1 decade ago | 3004
    kodo.util.FatalDataStoreException: ORA-01453: SET TRANSACTION must be first statement of transaction
  2. 0

    Exception before_completion operation, FatalDataStore: null

    Oracle Community | 1 decade ago | 666705
    kodo.util.FatalDataStoreException: null
  3. 0

    oracle clob problem

    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 o ccurred.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    blob saving problem

    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.
  6. 0

    Oracle CLOB problem

    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

      ORA-01453: SET TRANSACTION must be first statement of transaction

      at kodo.runtime.PersistenceManagerImpl.beforeCompletion()
    2. kodo.runtime
      PersistenceManagerImpl.beforeCompletion
      1. kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:897)
      1 frame