kodo.util.DataStoreException

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

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 web7

  • via Oracle Community by 3004, 2 weeks ago
    ORA-01453: SET TRANSACTION must be first statement of transaction
  • via Oracle Community by 3004, 1 year ago
    ORA-01453: SET TRANSACTION must be first statement of transaction
  • via Oracle Community by 666705, 11 months ago
    DSRA9350E: Operation Connection.commit is not allowed during a global transaction.
  • Stack trace

    • kodo.util.DataStoreException: ORA-01453: SET TRANSACTION must be first statement of transaction at kodo.jdbc.sql.DBDictionary.newDataStoreException(DBDictionary.java:3081) at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:77) at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:63) at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:43) at kodo.jdbc.runtime.JDBCStoreManager.connect(JDBCStoreManager.java:890) at kodo.jdbc.runtime.JDBCStoreManager.retainConnection(JDBCStoreManager.java:189) at kodo.jdbc.runtime.JDBCStoreManager.begin(JDBCStoreManager.java:114) at kodo.runtime.DelegatingStoreManager.begin(DelegatingStoreManager.java:95) at kodo.runtime.PersistenceManagerImpl.beginStoreManagerTransaction(PersistenceManagerImpl.java:531) at kodo.runtime.PersistenceManagerImpl.begin(PersistenceManagerImpl.java:501) at com.tti.act.flow.methods.impl.MethodEntity.openTransaction(MethodEntity.java:1843) at com.tti.act.flow.TransactionAtomicCommandManager.executeAtomicCommandWithAutoCommitOnJob(TransactionAtomicCommandManager.java:52) at com.tti.act.flow.JobFlow.innerInvokeMethod(JobFlow.java:955) at com.tti.act.flow.FlowManager.innerInvokeMethod(FlowManager.java:1421) at com.tti.act.flow.methods.impl.MethodTask.run(MethodTask.java:147) at tti.jcore.mt.scheduler.ejb.JobExecutorBean.executeJob(JobExecutorBean.java:121) at tti.jcore.mt.scheduler.ejb.JobExecutor_u19lg0_EOImpl.executeJob(JobExecutor_u19lg0_EOImpl.java:46) at tti.jcore.mt.scheduler.impl.QuartzJob.execute(QuartzJob.java:101) at org.quartz.core.JobRunShell.run(JobRunShell.java:178) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:487)

    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.