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

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 3004, 1 year 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, 1 year ago
DSRA9350E: Operation Connection.commit is not allowed during a global transaction.
via Oracle Community by 3004, 1 year ago
ORA-01407: cannot update ("AAA"."CONTRACT_HISTORY"."EVENT_DESCRIPTION") to NULL {prepstmnt 159208982 UPDATE AAA.CONTRACT_HISTORY SET EVENT_DESCRIPTION = ?, LAST_UPDATE_DATE = ?, CONTRACT_ID = ? WHERE CONTRACT_HISTORY_ID = ? AND SEQ_NUMBER
via Oracle Community by 3004, 1 year ago
ORA-00600: internal error code, arguments: [kokleva], [], [], [], [], [], [], [] {prepstmnt 1173845 INSERT INTO EPSCHEDULE.SC_TMEMO (CONTENT, JDOVERSION, MCODE, MODIFYTIME, RCODE, RFLAG, TITLE, USERID, USERNAME, WDATE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)} [code=600, state=60000]
via Oracle Community by 3004, 1 year ago
ORA-00979: N'est pas une expression GROUP BY {prepstmnt 30102190 SELECT t1.DEPARTMENT_ID, t1.DEPARTMENT_NAME, t1.LOCATION_ID, t1.MANAGER_ID, MAX (t0.SALARY), t0.DEPARTMENT_ID FROM TESTKODO.HR_DEPARTMENTS t1, TESTKODO.HR_EMPLOYEES t0 WHERE t0.DEP
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)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.