kodo.util.DataStoreException: 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

    SET TRANSACTION must be first statement of transaction

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

    setting isolation level fails

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

    Mapping util.Date to Oracle timestamp

    Oracle Community | 1 decade ago | 3004
    kodo.util.DataStoreException: Invalid column type
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    kodo.util.DataStoreException: Invalid Oracle URL specified

    Oracle Community | 1 decade ago | 3004
    kodo.util.DataStoreException: Invalid Oracle URL specified
  6. 0

    Protocol Exception Error

    wpthm.com | 1 year ago
    kodo.util.DataStoreException: Protocol violation at kodo.jdbc.sql.DBDictionary.newDataStoreException(DBDictionary.java:3414)

    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.DataStoreException

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

      at kodo.jdbc.sql.DBDictionary.newDataStoreException()
    2. kodo.jdbc.sql
      SQLExceptions.getDataStore
      1. kodo.jdbc.sql.DBDictionary.newDataStoreException(DBDictionary.java:3081)
      2. kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:77)
      3. kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:63)
      4. kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:43)
      4 frames
    3. kodo.jdbc.runtime
      JDBCStoreManager.begin
      1. kodo.jdbc.runtime.JDBCStoreManager.connect(JDBCStoreManager.java:890)
      2. kodo.jdbc.runtime.JDBCStoreManager.retainConnection(JDBCStoreManager.java:189)
      3. kodo.jdbc.runtime.JDBCStoreManager.begin(JDBCStoreManager.java:114)
      3 frames
    4. kodo.runtime
      PersistenceManagerImpl.begin
      1. kodo.runtime.DelegatingStoreManager.begin(DelegatingStoreManager.java:95)
      2. kodo.runtime.PersistenceManagerImpl.beginStoreManagerTransaction(PersistenceManagerImpl.java:531)
      3. kodo.runtime.PersistenceManagerImpl.begin(PersistenceManagerImpl.java:501)
      3 frames
    5. com.tti.act
      MethodTask.run
      1. com.tti.act.flow.methods.impl.MethodEntity.openTransaction(MethodEntity.java:1843)
      2. com.tti.act.flow.TransactionAtomicCommandManager.executeAtomicCommandWithAutoCommitOnJob(TransactionAtomicCommandManager.java:52)
      3. com.tti.act.flow.JobFlow.innerInvokeMethod(JobFlow.java:955)
      4. com.tti.act.flow.FlowManager.innerInvokeMethod(FlowManager.java:1421)
      5. com.tti.act.flow.methods.impl.MethodTask.run(MethodTask.java:147)
      5 frames
    6. tti.jcore.mt
      QuartzJob.execute
      1. tti.jcore.mt.scheduler.ejb.JobExecutorBean.executeJob(JobExecutorBean.java:121)
      2. tti.jcore.mt.scheduler.ejb.JobExecutor_u19lg0_EOImpl.executeJob(JobExecutor_u19lg0_EOImpl.java:46)
      3. tti.jcore.mt.scheduler.impl.QuartzJob.execute(QuartzJob.java:101)
      3 frames
    7. quartz
      SimpleThreadPool$WorkerThread.run
      1. org.quartz.core.JobRunShell.run(JobRunShell.java:178)
      2. org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:487)
      2 frames