Ora-01453

hi,
my development team mailed me that they are getting an error while uploading a template.
i am not understandng the exact reason why they are receiving this error.the error is listed below
ORA-01453: SET TRANSACTION must be first statement of transaction
Unable to begin transaction" for all the templates.
can any one suggest me regarding this error.
thanks in advance,
kishore.

All the statments should be commited/Rollbacked before you SET the transaction option. Check out wheter any DML operatiion happened before you Change the transaction level.. if so then
1. Perform commit/rollback based on the requirement before you SET the transaction OR
2. Move the SET TRANSACTION code prior to DML statement

Similar Messages

Ora-02062_and_pending_transactions

I've got oracle enterprise edition 10.2.04
In alert log I found ORA-02062: distributed recovery received DBID ...
I found transaction in DBA_2PC_PENDING and similar in DBA_2PC_NEIGHBORS;
select local_tran_id,state from dba_2pc_pending;LOCAL_TRAN_ID STATE
14.27.72754 collecting
when I try to remove it:
SQL> exec dbms_transaction.rollback_force('14.27.72754');
BEGIN dbms_transaction.rollback_force('14.27.72754'); END;
ERROR at line 1:
ORA-02043: must end current transaction before executing ROLLBACK FORCE
ORA-06512: at "SYS.DBMS_TRANSACTION", line 28
ORA-06512: at line 1
when I try:
SQL> exec dbms_transaction.purge_lost_db_entry('14.27.72754');
BEGIN dbms_transaction.purge_lost_db_entry('14.27.72754'); END;
ERROR at line 1:
ORA-01453: SET TRANSACTION must be first statement of transaction
ORA-06512: at "SYS.DBMS_TRANSACTION", line 65
ORA-06512: at "SYS.DBMS_TRANSACTION", line 87
ORA-06512: at line 1
when I try:
SQL> rollback force '14.27.72754';
rollback force '14.27.72754'
ERROR at line 1:
ORA-02043: must end current transaction before executing ROLLBACK FORCE
or
SQL> commit force '14.27.72754';
commit force '14.27.72754'
ERROR at line 1:
ORA-02043: must end current transaction before executing COMMIT FORCE
So
Have you got any idea how to remove this pending transaction, thanks

When you pay a company (rather than an ebay seller or individual), then it is always pending until that company processes your order and captures the pending payment.
If they don't process that order and capture the pending payment then the pending status times out at 30 days post-payment. Normally no funds are actually taken until the payment is captured. ************************************************ I give up my time to help you so a thank you or kudos would be cool.
Marking one of my replies as a solution would be appreciated if I sorted your problem.

Connection pooling unable to close connection on Oracle 9i 64bit

Hi there,
We have a Oracle 9i 64 bit server housed on a Solaris 64bit box. Earlier we had a 8i on a solaris 32 bit and things were fine. But after having migrated to 9i, we have been facing a peculiar issue where in the connections being opened by the application do not close/expire. We never had this problem on the 8i box.
System spec:
Solaris 64bit ver 8
JDK 1.4 JDBC thin drivers(ojdbc14.jar)
JDBC 2.0
Oracle 9.2.0.8 (64bit)
The application is housed on a 32 bit Solarix box and runs on Tomcat4.1.
Has anyone seen such probs before?? ...any ideas(quick ones) will be appreciated!
Anybody

Hi,
I did a oracle trace of the issue and this is what i get from the trace
DRVR OPER OracleConnection.setAutoCommit(autoCommit): return
DRVR OPER OracleConnection.setReadOnly(readOnly=false)
DRVR SQLS SQL: "SET TRANSACTION READ WRITE"
DRVR OPER OracleConnection.getDefaultFixedString() returning false
DRVR OPER ResultSetUtil.needIdentifier(typeCode=1): return: false
DRVR OPER OraclePreparedStatement.execute()
DRVR OPER OraclePreparedStatement.executeUpdate()
DRVR SQLS Input SQL: "SET TRANSACTION READ WRITE"
DRVR OPER OracleConnection.getAutoCommit() returned true
DRVR OPER OracleStatement.cleanupForBatching()
DRVR OPER OraclePreparedStatement.sendBatch()
DRVR SQLS SQL: "{call PKG_REASSIGN.I01_REASSIGN(?,?,?,?,?,?)}"
DRVR OPER OracleConnection.getDefaultFixedString() returning false
DRVR OPER ResultSetUtil.needIdentifier(typeCode=1): return: false
DRVR SQLS sql=<{call PKG_REASSIGN.I01_REASSIGN(?,?,?,?,?,?)}>
DRVR SQLS Input SQL: "{call PKG_REASSIGN.I01_REASSIGN(?,?,?,?,?,?)}"
DRVR SQLS sql=<{call PKG_REASSIGN.I01_REASSIGN(?,?,?,?,?,?)}>
DRVR OPER OraclePreparedStatement.setBigDecimal(paramIndex=1, x=790846)
DRVR OPER OraclePreparedStatement.setString(paramIndex=2, x=FBGJ)
DRVR OPER OraclePreparedStatement.setString(paramIndex=3, x=BALMKR01)
DRVR OPER OraclePreparedStatement.setString(paramIndex=4, x=IMRVER71)
DRVR OPER OraclePreparedStatement.setString(paramIndex=5, x=10.128.28.245)
DRVR OPER OracleCallableStatement.registerOutParameter(paramIndex=6, sqlType=2, scale=0, maxLength=-1)
DRVR OPER OracleCallableStatement.registerOutParameterBytes(paramIndex=6, sqlType=2, scale=0, maxLength=-1)
DRVR OPER OracleConnection.setAutoCommit(autoCommit=false)
DRVR OPER OracleConnection.setAutoCommit(autoCommit): return
DRVR OPER OraclePreparedStatement.execute()
DRVR OPER OraclePreparedStatement.executeUpdate()
DRVR OPER OracleConnection.getAutoCommit() returned false
DRVR OPER OracleStatement.cleanupForBatching()
DRVR OPER OracleCallableStatement.sendBatch()
Performing a pooledConnection.notifyListener() in ConnectionImpl.class
Doing a getConnection() in Jdbc2PoolDataSource
DRVR OPER OracleConnection.setAutoCommit(autoCommit=true)
DRVR OPER OracleConnection.setAutoCommit(autoCommit): return
DRVR OPER OracleConnection.setReadOnly(readOnly=false)
DRVR SQLS SQL: "SET TRANSACTION READ WRITE"
DRVR OPER OracleConnection.getDefaultFixedString() returning false
DRVR OPER ResultSetUtil.needIdentifier(typeCode=1): return: false
DRVR OPER OraclePreparedStatement.execute()
DRVR OPER OraclePreparedStatement.executeUpdate()
DRVR SQLS Input SQL: "SET TRANSACTION READ WRITE"
DRVR OPER OracleConnection.getAutoCommit() returned true
DRVR OPER OracleStatement.cleanupForBatching()
DRVR OPER OraclePreparedStatement.sendBatch()
com.*********.common.serviceexecutor.ServiceExecutorException: com.*********.common.exception.SCBBaseException: SQL Exception occured while getting connection from ConnectionPool in SQLMassRetrieveExecutor
at com.*********.common.serviceexecutor.Service.executeMethodsInOrder(Unknown Source)
at com.*********.common.serviceexecutor.Service.execute(Unknown Source)
at com.*********.common.serviceexecutor.ServiceDefinition.executeServices(Unknown Source)
at com.*********.common.serviceexecutor.StatelessServiceExecutorImpl.executeServiceDefinition(Unknown Source)
at com.*********.common.sessionutil.PageManager.executeServiceExecutor(Unknown Source)
at com.*********.common.sessionutil.PageManager.executeMethod(Unknown Source)
at com.*********.common.sessionutil.PageManager.getFirstPage(Unknown Source)
at com.*********.common.sessionutil.PageManager.getPages(Unknown Source)
at com.*********.sci.view.action.VerifyQueueListAction.perform(VerifyQueueListAction.java:124)
at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1787)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:432)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:356)
at org.apache.struts.action.ActionServlet.processActionForward(ActionServlet.java:1759)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1596)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at com.*********.sci.appservice.commonservices.FilterNew.doFilter(FilterNew.java:23)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:213)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:457)
at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:576)
at java.lang.Thread.run(Thread.java:536)
Caused by: com.*********.common.exception.SCBBaseException: SQL Exception occured while getting connection from ConnectionPool in SQLMassRetrieveExecutor
at com.*********.common.dbexecutor.SQLMassRetrieveExecutor.<init>(Unknown Source)
at com.*********.common.dbexecutor.ConnectionRetriever.getInstance(Unknown Source)
at com.*********.sci.appservice.queue.VerifyQueueListService.getDatabaseRowSetConnection(VerifyQueueListService.java:96)
at com.*********.sci.appservice.queue.VerifyQueueListService.getVerifyQueueList(VerifyQueueListService.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
... 51 more
Caused by: java.sql.SQLException: ORA-01453: SET TRANSACTION must be first statement of transaction
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:590)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1973)
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:1119)
at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2191)
at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:2064)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2989)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:658)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:736)
at oracle.jdbc.driver.OracleConnection.setReadOnly(OracleConnection.java:1631)
at com.*********.common.connectionpool.adapter.ConnectionImpl.setReadOnly(ConnectionImpl.java:203)
at com.*********.common.connectionpool.newp.Jdbc2PoolDataSource.getConnection(Jdbc2PoolDataSource.java:645)
at com.*********.common.connectionpool.newp.Jdbc2PoolDataSource.getConnection(Jdbc2PoolDataSource.java:534)
... 59 more
Is oracle missing a COMMIT before it is passing the SET TRANSACTION statement??. and is there any relation between the AutoCommit and the Isolation level?

Setting isolation level fails

Hi,
Im using Kodo 3.0.0 on Oracle 8.1.7.
I tried to define the isolation level in the kodo.properties:
e.g.: kodo.jdbc.TransactionIsolation: serializable
Unfortunately Oracle throws an exception which says, that "set
transaction" has to be the first statement called within a transaction. I
get this exception on almost every db access.
java.sql.SQLException: ORA-01453: SET TRANSACTION muss erste Anweisung der
Transaktion sein
at
kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:42)
at
kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:24)
at
kodo.jdbc.schema.LazySchemaFactory.findTable(LazySchemaFactory.java:1
50)
at
kodo.jdbc.meta.VerticalClassMapping.fromMappingInfo(VerticalClassMapp
ing.java:135)
at
kodo.jdbc.meta.RuntimeMappingProvider.getMapping(RuntimeMappingProvid
er.java:56)
at
kodo.jdbc.meta.MappingRepository.getMappingInternal(MappingRepository
java:342)
at
kodo.jdbc.meta.MappingRepository.getMapping(MappingRepository.java:29
7)
at
kodo.jdbc.meta.MappingRepository.getMappingInternal(MappingRepository
java:325)
at
kodo.jdbc.meta.MappingRepository.getMapping(MappingRepository.java:29
7)
at
kodo.jdbc.meta.MappingRepository.getMappings(MappingRepository.java:2
72)
at
kodo.jdbc.meta.MappingRepository.getMetaDatas(MappingRepository.java:
256)
at kodo.query.AbstractQuery.internalCompile(AbstractQuery.java:538)
at kodo.query.AbstractQuery.compile(AbstractQuery.java:502)
at kodo.datacache.CacheAwareQuery.compile(CacheAwareQuery.java:265)
-- Wolfgang

Marc,
Here you go...
kodo.util.FatalDataStoreException: ORA-01453: SET TRANSACTION must be
first statement of transaction
     at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:897)
     at kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
     at
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:566)
     at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction.initTestModel(AbstractConcurrentAction.java:290)
     at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction$InitRunnable.run(AbstractConcurrentAction.java:212)
     at
edu.sjsu.recon.util.ConcurrencyUtilities.executeSynchronized(ConcurrencyUtilities.java:20)
     at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction.setup(AbstractConcurrentAction.java:75)
     at
edu.sjsu.recon.execution.ServerExecutor.beforeExecute(ServerExecutor.java:27)
     at
edu.sjsu.recon.execution.AbstractExecutor.execute(AbstractExecutor.java:43)
     at
edu.sjsu.recon.execution.DefaultExecutionCoordinator.executeAction(DefaultExecutionCoordinator.java:25)
     at
edu.sjsu.recon.server.handler.ExecutionRequestHandler.handleRequest(ExecutionRequestHandler.java:63)
     at edu.sjsu.recon.server.RequestProcessor.run(RequestProcessor.java:90)
NestedThrowablesStackTrace:
kodo.util.DataStoreException: ORA-01453: SET TRANSACTION must be first
statement of transaction
     at
kodo.jdbc.sql.DBDictionary.newDataStoreException(DBDictionary.java:3004)
     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:871)
     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.flushInternal(PersistenceManagerImpl.java:1004)
     at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:885)
     at kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
     at
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:566)
     at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction.initTestModel(AbstractConcurrentAction.java:290)
     at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction$InitRunnable.run(AbstractConcurrentAction.java:212)
     at
edu.sjsu.recon.util.ConcurrencyUtilities.executeSynchronized(ConcurrencyUtilities.java:20)
     at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction.setup(AbstractConcurrentAction.java:75)
     at
edu.sjsu.recon.execution.ServerExecutor.beforeExecute(ServerExecutor.java:27)
     at
edu.sjsu.recon.execution.AbstractExecutor.execute(AbstractExecutor.java:43)
     at
edu.sjsu.recon.execution.DefaultExecutionCoordinator.executeAction(DefaultExecutionCoordinator.java:25)
     at
edu.sjsu.recon.server.handler.ExecutionRequestHandler.handleRequest(ExecutionRequestHandler.java:63)
     at edu.sjsu.recon.server.RequestProcessor.run(RequestProcessor.java:90)
NestedThrowablesStackTrace:
java.sql.SQLException: ORA-01453: SET TRANSACTION must be first statement
of transaction
     at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:305)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:272)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:623)
     at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:112)
     at oracle.jdbc.driver.T4CStatement.execute_for_rows(T4CStatement.java:474)
     at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1028)
     at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1516)
     at
oracle.jdbc.driver.PhysicalConnection.setTransactionIsolation(PhysicalConnection.java:1412)
     at
com.solarmetric.jdbc.DelegatingConnection.setTransactionIsolation(DelegatingConnection.java:266)
     at
com.solarmetric.jdbc.DelegatingConnection.setTransactionIsolation(DelegatingConnection.java:266)
     at
com.solarmetric.jdbc.DelegatingConnection.setTransactionIsolation(DelegatingConnection.java:266)
     at
com.solarmetric.jdbc.DelegatingConnection.setTransactionIsolation(DelegatingConnection.java:266)
     at
com.solarmetric.jdbc.ConfiguringConnectionDecorator.decorate(ConfiguringConnectionDecorator.java:93)
     at
com.solarmetric.jdbc.DecoratingDataSource.decorate(DecoratingDataSource.java:90)
     at
com.solarmetric.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:82)
     at
com.solarmetric.jdbc.DelegatingDataSource.getConnection(DelegatingDataSource.java:131)
     at
kodo.jdbc.schema.DataSourceFactory$DefaultsDataSource.getConnection(DataSourceFactory.java:305)
     at
kodo.jdbc.runtime.JDBCStoreManager.connectInternal(JDBCStoreManager.java:887)
     at kodo.jdbc.runtime.JDBCStoreManager.connect(JDBCStoreManager.java:865)
     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.flushInternal(PersistenceManagerImpl.java:1004)
     at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:885)
     at kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
     at
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:566)
     at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction.initTestModel(AbstractConcurrentAction.java:290)
     at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction$InitRunnable.run(AbstractConcurrentAction.java:212)
     at
edu.sjsu.recon.util.ConcurrencyUtilities.executeSynchronized(ConcurrencyUtilities.java:20)
     at
edu.sjsu.recon.contribution.action.jdo.v10.kodo.v32.oracle.v101.simple.concurrency.AbstractConcurrentAction.setup(AbstractConcurrentAction.java:75)
     at
edu.sjsu.recon.execution.ServerExecutor.beforeExecute(ServerExecutor.java:27)
     at
edu.sjsu.recon.execution.AbstractExecutor.execute(AbstractExecutor.java:43)
     at
edu.sjsu.recon.execution.DefaultExecutionCoordinator.executeAction(DefaultExecutionCoordinator.java:25)
     at
edu.sjsu.recon.server.handler.ExecutionRequestHandler.handleRequest(ExecutionRequestHandler.java:63)
     at edu.sjsu.recon.server.RequestProcessor.run(RequestProcessor.java:90)
Marc Prud'hommeaux wrote:
Cleo-
Can you post the complete stack (including all the nested stack traces)?
In article <[email protected]>, Cleo wrote:
Marc,
Here is the stack:
ORA-01453: SET TRANSACTION must be first statement of transaction
kodo.util.FatalDataStoreException
     at
kodo.runtime.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:897)
     at kodo.runtime.LocalManagedRuntime.commit(LocalManagedRuntime.java:69)
     at
kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:566)
This is the code being executed:
Transaction initTransaction = initPersistenceManager.currentTransaction();
initTransaction.begin();
initPersistenceManager.makePersistentAll(model);
initTransaction.commit(); //EXCEPTION HERE
initPersistenceManager.close();
thx
Marc Prud'hommeaux wrote:
Cleo-
Can you post the complete stack trace from the exception? I expect it is
different from the one posted previously (which was with a much earlier
version of Kodo).
In article <[email protected]>, Cleo wrote:
Has anybody figured out how to solve this?
I am having the same problem with:
KODO 3.2
Oracle JDBC Dirver 10.1.0.3
thx
PS: (I am on a deadline for the end of this week)
Stephen Kim wrote:
First I would suggest using Kodo 3.0.1. Second I would suggest trying
to use 9.0.1 drivers which work very well with 8.1.7.
Wolfgang Hutya wrote:
Hi,
Im using Kodo 3.0.0 on Oracle 8.1.7.
I tried to define the isolation level in the kodo.properties:
e.g.: kodo.jdbc.TransactionIsolation: serializable
Unfortunately Oracle throws an exception which says, that "set
transaction" has to be the first statement called within a
transaction.
I
get this exception on almost every db access.
java.sql.SQLException: ORA-01453: SET TRANSACTION muss erste
Anweisung
der
Transaktion sein
at
kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:42)
at
kodo.jdbc.sql.SQLExceptions.getFatalDataStore(SQLExceptions.java:24)
at
kodo.jdbc.schema.LazySchemaFactory.findTable(LazySchemaFactory.java:1
50)
at
kodo.jdbc.meta.VerticalClassMapping.fromMappingInfo(VerticalClassMapp
ing.java:135)
at
kodo.jdbc.meta.RuntimeMappingProvider.getMapping(RuntimeMappingProvid
er.java:56)
at
kodo.jdbc.meta.MappingRepository.getMappingInternal(MappingRepository
java:342)
at
kodo.jdbc.meta.MappingRepository.getMapping(MappingRepository.java:29
7)
at
kodo.jdbc.meta.MappingRepository.getMappingInternal(MappingRepository
java:325)
at
kodo.jdbc.meta.MappingRepository.getMapping(MappingRepository.java:29
7)
at
kodo.jdbc.meta.MappingRepository.getMappings(MappingRepository.java:2
72)
at
kodo.jdbc.meta.MappingRepository.getMetaDatas(MappingRepository.java:
256)
atkodo.query.AbstractQuery.internalCompile(AbstractQuery.java:538)
at kodo.query.AbstractQuery.compile(AbstractQuery.java:502)
atkodo.datacache.CacheAwareQuery.compile(CacheAwareQuery.java:265)
-- Wolfgang
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com
Marc Prud'hommeaux
SolarMetric Inc.
Marc Prud'hommeaux
SolarMetric Inc.

Rollback segment error

Hello experts,
My problem is as follows:
I need to perform a large transaction on one of my tables in my
database. I have to delete a large number of records using a
command as follows:
Delete from mytable where ordernumber like '2000%';
Each time i launch this command i have the following error:
ERROR at line 1:
ORA-01562: failed to extend rollback segment (id = 3)
ORA-01628: max # extents (30) reached for rollback segment R03
I know that i have a problem with my rollback segment. I have
thus created a large rollback segment so that my transaction can
use it.
I don't know how to tell my transaction use the large rollback
segment that i created.
(i know there is a command called set transation user rollback
segment large_rs1, i have tried it on sqlplus. it gives me
error: ORA-01453: SET TRANSACTION must be first statement of
transaction)
Please help
thanks in advance for a reply
Kind regards
Yogeeraj

First, you have to create a bigger rollback segment (i.e. RBBIG).
Then, before each query, you must type:
set transaction use rollback segment rbbig;
This will force the use of the specified rollback segment.
Hope this helps.

JdbcRowSetXImp (..): SET TRANSACTION must be first statement of transaction

Hi.
Im running JSC created application and getting in the log file this messages:
[date & time] warning (24167): CORE3238: stderr: JdbcRowSetXImpl (setTransactionIsolation): [Sun][Oracle JDBC Driver][Oracle]ORA-01453: SET TRANSACTION must be the first statement of transaction
As you may see, Im using JSC JDBC drivers. Im running on Sun One Web Server version 6.1 sp2 on Linux RedHat 3Ent. The application was builded with JSC me with latest patch applied.
It seems a bug in the JdbcRowSetXImpl.
Has someone similar problem?
Regards.

Hi John.
This message is present on all log file a few days after the application began in production use, almost a month ago.
The only change done in the configuration few days after the app was deployed was "Guarantee Isolation Level" in the JDBC connection pool configuration, switched from OFF to ON.
Yesterday I turn OFF again and have no more messages about SET TRANSACTION...
I guess that the SET TRANSACTION is issued two times, one by the web server before giving the connection to the app then by the row set impl.
I will let you known if the messages appears again (I guess not).
Regards.

Oracle 10:1:0:200 client works on windows 2003 not XP

Hi Group,
The backend oracle database is the same. The Serviced Components Middle Layer is on Windows 2003 and XP Professional SP1. The Clients are tested on the Middle Layer.
It works fine on Windows 2003. On XP the error is:
================
Failed to Open the Data Source connection error: Oracle.DataAccess.Client.OracleException ORA-01453: SET TRANSACTION must be first statement of
transaction at Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure)
at Oracle.DataAccess.Client.OracleCommand.ExecuteNonQuery()
================
thanks,
-Arvinder

The problem does not have to do with XP/Windows 2003. It is caused by:
==========
OracleCommand cmd = new
OracleCommand("SET TRANSACTION ISOLATION LEVEL READ COMMITTED", cnn);
cmd.ExecuteNonQuery();
==========
The COM+ transactions are defaulted to serializable. Our application reads a config file to choose the database and then issues the statement above. I know we can set the isolation attribute at the c# serviced component level at compile time. Is there a dynamic way to set the isolation at runtime? Microsofts SQL and Oracle providers do not fail with the SQL statement above.
thanks,
-Arvinder

Lost transaction, but unable to clear

Hello all,
I have a 10g database 10.1.0.5 insatalled on Sun solaris 9.
below is my case:
in alert log file: ORA-02062: distributed recovery received DBID 74ec2ff7, expected e6b20517
I did the below:
select LOCAL_TRAN_ID from DBA_2PC_PENDING
LOCAL_TRAN_ID
237.17.348763
226.18.237626
392.41.32069
318.36.153006
252.5.232383
237.36.370660
262.15.211266
255.24.267959
STATE column of all is "collecting"
MIXED column of all is null
now when I do:
SQL>conn sys as sysdba
SQL> exec DBMS_TRANSACTION.rollback_force('237.17.348763'); // or any other ID
ERROR at line 1:
ORA-02058: no prepared transaction found with ID 237.17.348763
ORA-06512: at "SYS.DBMS_TRANSACTION", line 28
ORA-06512: at line
then I tried:
SQL> exec dbms_transaction.purge_lost_db_entry('216.41.226667');
ERROR at line 1:
ORA-01453: SET TRANSACTION must be first statement of transaction
ORA-06512: at "SYS.DBMS_TRANSACTION", line 65
ORA-06512: at "SYS.DBMS_TRANSACTION", line 85
ORA-06512: at line 1
the transactions are existed in both SYS.PENDING_TRANS$ and SYS.PENDING_SESSIONS$
what should I do to clear it ?
many thanks in advance
Salloum
Edited by: user13364155 on Aug 5, 2011 4:31 PM

Are you sure you are checking for the right solution?
ORA-02062: distributed recovery received DBID string, expected string
Cause: a database link at a coordinator no longer points to the expected database. Link may have been redefined, or a different DB mounted.
Action: restore link definition or remote database.
Edited by: Aron Tunzi on Aug 6, 2011 2:22 AM

Non-XA or XA datasources?

Hi,
I have an enterprise application (deployed as a single .ear) that is two session beans and multiple servlets, running on Sun ONE Application Server 7.0.0_03c.
I have two databases (both oracle 9.2) that I need to be able to call in the one of the bean methods:
void loadX() {
Connection paCon = getConnection("java:comp/env/jdbc/pa");
x.loadDataFieldsFromPA(paCon, ...);
Connection efeCon = getConnection("java:comp/env/jdbc/efe");
x.loadDataFieldsFromEFE(efeCon, ...);
Connection getConnection(String name) {
InitialContext ic = new InitialContext();
DataSource dataSource = (DataSource)ic.lookup(dataSourceName);
return dataSource.getConnection();
If I define jdbc/efe and jdbc/pa as using XA datasources, I get:
"ORA-01453: SET TRANSACTION must be first statement of transaction"
on the first call.
If I define jdbc/efe and jdbc/pa as using non-XA datasources, I get:
"java.lang.IllegalStateException: Local transaction already has 1 non-XA Resource: cannot add more resources"
on opening the second connection.
Can anyone suggest what I might be doing wrong?
TIA

Hi,
I have an enterprise application (deployed as a single .ear) that is two session beans and multiple servlets, running on Sun ONE Application Server 7.0.0_03c.
I have two databases (both oracle 9.2) that I need to be able to call in the one of the bean methods:
void loadX() {
Connection paCon = getConnection("java:comp/env/jdbc/pa");
x.loadDataFieldsFromPA(paCon, ...);
Connection efeCon = getConnection("java:comp/env/jdbc/efe");
x.loadDataFieldsFromEFE(efeCon, ...);
Connection getConnection(String name) {
InitialContext ic = new InitialContext();
DataSource dataSource = (DataSource)ic.lookup(dataSourceName);
return dataSource.getConnection();
If I define jdbc/efe and jdbc/pa as using XA datasources, I get:
"ORA-01453: SET TRANSACTION must be first statement of transaction"
on the first call.
If I define jdbc/efe and jdbc/pa as using non-XA datasources, I get:
"java.lang.IllegalStateException: Local transaction already has 1 non-XA Resource: cannot add more resources"
on opening the second connection.
Can anyone suggest what I might be doing wrong?
TIA

Trying to understnd transactions better...

I was reading an article concerning how oracle handles transactions and the article said the following...
Transaction Isolation
The database ensures that no uncommitted data is visible to other sessions and that the data set remains
consistent for the lifetime of a transaction, depending on the isolation level chosen. Oracle supports two
transaction isolation levels:
• Read Committed — The session is able to query data that has been committed during the lifetime of the
transaction but the data set remains stable for the life of a statement. This means that the same query may
return different results if issued twice in the same transaction if data has been changed.
• Serializable — The data set is stable for the life of a transaction. A query will always return the same results
within the same transaction even if data has been changed and committed.
so My question is "how do you choose an isolation level"? Is this a parameter that I would set for oracle? How do I know if I am using etiher
"read commited" or "serializable"?
thx.

Changes you make with 'set transaction' have transaction duration only. So, 'set transaction isolation level serializable' would only affect that new transaction of your session.
(Note that 'set transaction ...' actually creates a new transaction, and, as such, must be the first statement in a transaction. If you try to run it after a transaction has begun, you'll get an error.
MBOBAK@inbound1> create table test_trans(a number);
Table created.
MBOBAK@inbound1> insert into test_trans values(1);
1 row created.
MBOBAK@inbound1> set transaction isolation level serializable;
set transaction isolation level serializable
ERROR at line 1:
ORA-01453: SET TRANSACTION must be first statement of transaction
MBOBAK@inbound1> commit;
Commit complete.
MBOBAK@inbound1> set transaction isolation level serializable;
Transaction set.Hope that helps,
-Mark

SET TRANSACTION must be first statement of transaction

I am using oracle8i db with sun one 7.0. i use the oracle thin driver to talk to the db. i have bunch of session beans which uses the oracle data source. when i invoke the session bean, i get this ORA-01453 error.
Here is my jdbc properties:
<jdbc-connection-pool steady-pool-size="8" max-pool-size="32" max-wait-time-in-millis="60000" pool-resize-quantity="2" idle-timeout-in-seconds="300" is-isolation-level-guaranteed="true" is-connection-validation-required="true" connection-validation-method="table" fail-all-connections="false" datasource-classname="oracle.jdbc.xa.client.OracleXADataSource" name="JSBContainerPool" res-type="javax.sql.XADataSource" validation-table-name="dual" transaction-isolation-level="read-committed">
<property value="jdbc:oracle:thin:@muruga:1521:DEV" name="URL"/>
<property value="muruga" name="User"/>
<property value="muruga" name="Password"/>
</jdbc-connection-pool>
<jdbc-resource enabled="true" pool-name="JSBContainerPool" jndi-name="jdbc/JSBContainerDataSource"/>
Error message:
The exception reported is: "java.sql.SQLException: ORA-01453: SET TRANSACTION
must be first statement of transaction
WARNING: CORE3283: stderr: at oracle.jdbc.dbaccess.DBError.throwSqlExceptio
n(DBError.java:168)
WARNING: CORE3283: stderr: at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.j
ava:208)
WARNING: CORE3283: stderr: at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543
WARNING: CORE3283: stderr: at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Pro
tocol.java:1405)
WARNING: CORE3283: stderr: at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFet
ch(TTC7Protocol.java:822)
WARNING: CORE3283: stderr: at oracle.jdbc.driver.OracleStatement.executeNon
Query(OracleStatement.java:1446)
WARNING: CORE3283: stderr: at oracle.jdbc.driver.OracleStatement.doExecuteO
ther(OracleStatement.java:1371)
WARNING: CORE3283: stderr: at oracle.jdbc.driver.OracleStatement.doExecuteW
ithTimeout(OracleStatement.java:1900)
WARNING: CORE3283: stderr: at oracle.jdbc.driver.OracleStatement.execute(Or
acleStatement.java:737)
WARNING: CORE3283: stderr: at oracle.jdbc.driver.OracleConnection.setTransa
ctionIsolation(OracleConnection.java:1081)
WARNING: CORE3283: stderr: at com.sun.enterprise.resource.Jdbc20XaAllocator
$ConnectionWrapper.setTransactionIsolation(Jdbc20XaAllocator.java:196)

In the connection pool setting in Admin server under the section Transaction Isolation deselect the option "Guarantee Isolation Level" .This should solve the problem.
regards
Kris

DBI Set up

Hi I would like to know the Navigation and Set up path for DBI - OPM,Distribution,Financials & HRMS in R12....
Please forward the navigation path to [email protected]

I have been able to successfully install DBD::Oracle
found two (small?) issues though...
OSX Server (10.2.2 - 6F21)
Oracle 9iR2 developper release for OSX.
Files I used and installed in that sequence:
From url: http://www.perl.com/CPAN/modules/by-module/...
1) Time-HiRes-1.39.tar.gz ## needed for DBI
install as usual
2) DBI-1.32.tar.gz
install as usual...
found a taint test failure (./t/10examp.t)
I don't know if this can be an issue...
3) DBD-Oracle-1.12.tar.gz
install according to README with "-p"
perl Makefile.PL -p
make
make test
sudo make install
=== ERROR ===
Expect an 'ORA-01453' error message:
ora_do: 1453: ORA-01453: SET TRANSACTION must be first statement of transaction (DBD ERROR: OCIStmtExecute)
csr out of scope...
ora_logoff...
lda out of scope...
=== FULL DETAILS ===
[./DBD-Oracle-1.12] oracle$ make test
PERL_DL_NONLAZY=1 /usr/bin/perl -Iblib/arch -Iblib/lib -I/System/Library/Perl/darwin -I/System/Library/Perl -e 'use Test::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;' t/*.t
t/base..............ok
t/general...........ok Long postings are being truncated to ~1 kB at this time.

Handling transaction

Dear:
Could some one give me a brife explanation of
ORA-01453. Does it really mean that one trasnaction is in process and another transaction is strating and previous transaction is holding a lock.
Thanks for any valuable suggestion.
Regards,
Ashaar Riaz

Are you issuing SET TRANSACTION in the middle of a transaction?
When you're using this statement, SET TRANSACTION must be the first statement in the transaction
i.e. -------------
SET TRANSACTION...
update...
savepoing...
update...
COMMIT.
if you do..
update...
savepoint...
SET TRANSACTION...
update...
savepoint...
... you will probably get error ORA-01453
Not sure what else could cause this error.
Lucio

PL/SQL report errors: ORA-01422

Hi all,
(before i you read i would like to say i have searched the net for this error code but nothing shows up like this problem..)
I am getting an error problem when i select certain Schemas from a list on an apex app. page, it only works for some schemas not all..
When i select one schema, it is supposed to display one row.. when i select [ALL] it is supposed to show them all.
It does work if i select '[ALL]' from the select list (p3_schema_name), just not for every single individual one.
the error code:
ORA-01422: exact fetch returns more than requested number of rows
declare
vSchema varchar2(20);
vStmt varchar2(1000);
vVersion number(5);
vDBName varchar2(20);
vHostName varchar2(80);
vStmt2 varchar2(1000);
vVersion2 number(5);
vDBName2 varchar2(20);
vServer2 varchar2(80);
vSchema2 varchar2(80);
CURSOR c_schemas IS
    select owner from dba_tables@P3_DB_NAME.db_link where table_name = 'DDL_LOG' and num_rows > 0 order by owner;
begin
IF :P3_SCHEMA_NAME != '[ALL]' AND :P3_DB_NAME IS NOT NULL AND :P3_SERVER_NAME IS NOT NULL THEN
    vServer2 := :P3_SERVER_NAME;
    vSchema2 := :P3_SCHEMA_NAME;
      vStmt2 := 'select distinct DDH_DB_NM, max(DDH_SCHEMA_NR)keep(dense_rank last order by ddh_runstart_td) AS "PATCH" from &P3_SCHEMA_NAME..ddl_log@&P3_DB_NAME.db_link GROUP BY DDH_DB_NM';
      Execute Immediate vStmt2 into vDBName2, vVersion2;
        htp.p('<br>');
        htp.p('<table border="1">');
        htp.p('<tr>');
        htp.p('<th bgcolor="#FFCC99">SERVER NAME</th>');
        htp.p('<th bgcolor="#FFCC99">DB NAME</th>');
        htp.p('<th bgcolor="#FFCC99">SCHEMA NAME</th>');
        htp.p('<th bgcolor="#FFCC99">PATCH</th>');
        htp.p('</tr>');
        htp.p('<tr>');
        htp.p('<td>');
        htp.p(vServer2);
        htp.p('</td>');
        htp.p('<td>');
        htp.p(vDBName2);
        htp.p('</td>');
        htp.p('<td>');
        htp.p(vSchema2);
        htp.p('</td>');
        htp.p('<td>');
        htp.p(vVersion2);
        htp.p('</td>');
        htp.p('<td>');
        htp.p('<BR>');
        htp.p('</td>');
        htp.p('</tr>');
        htp.p('</tr>');
        htp.p('</table>');
   ELSE IF :P3_SCHEMA_NAME = '[ALL]' AND :P3_DB_NAME IS NOT NULL AND :P3_SERVER_NAME IS NOT NULL THEN
   vHostName := :P3_SERVER_NAME;
   vDBName := :P3_DB_NAME;
     open c_schemas;
      htp.p('<br>');
      htp.p('<table border="1">');
      htp.p('<tr>');
      htp.p('<th bgcolor="#FFCC99">SERVER NAME</th>');
      htp.p('<th bgcolor="#FFCC99">DB NAME</th>');
      htp.p('<th bgcolor="#FFCC99">SCHEMA NAME</th>');
      htp.p('<th bgcolor="#FFCC99">PATCH</th>');
      htp.p('</tr>');
    LOOP
      FETCH c_schemas INTO vSchema;
      EXIT WHEN c_schemas%NOTFOUND;
      vStmt := 'select max(DDH_SCHEMA_NR)keep(dense_rank last order by ddh_runstart_td) AS "PATCH" from '||vSchema||'.ddl_log@&P3_DB_NAME.db_link where DDH_SCHEMA_NR = (select max(DDH_SCHEMA_NR) from '||vSchema||'.ddl_log@&P3_DB_NAME.db_link) and rownum < 2' ;
      Execute Immediate vStmt into vVersion ;
      htp.p('<tr>');
      htp.p('<td>');
      htp.p(vHostName);
      htp.p('</td>');
      htp.p('<td>');
      htp.p(vDBName);
      htp.p('</td>');
      htp.p('<td>');
      htp.p(vSchema);
      htp.p('</td>');
      htp.p('<td>');
      htp.p(vVersion);
      htp.p('</td>');
      htp.p('<td>');
      htp.p('<BR>');
      htp.p('</td>');
      htp.p('</tr>');
    END LOOP;
      htp.p('</tr>');
      htp.p('</table>');
CLOSE c_schemas;
END IF;
END IF;
END;I have checked the DDH_SCHEMA_NR for repeating entries of the highest number.. some of the ones that dont work do have repeating entries some don't.
Sorry if this is confusing, i have tried to explain it as best as i can.
Thanks in advance for any help.
Ashleigh

Hello Ashleigh,
Based on your code, I'd start by running this piece of SQL via command-line (thru SQL Workshop, SQL*Plus, Toad, etc.), replacing &P3_SCHEMA_NAME. and &P3_DB_NAME. with values that are currently causing the routine to fail and see if it returns more than one row. I don't know your data, but DISTINCT and GROUP BY are typically used to return multiple (though grouped/summarized) rows. It appears to be the only statement that would cause the error your seeing (more than one row being returned into single variables).
select distinct DDH_DB_NM, max(DDH_SCHEMA_NR)keep(dense_rank last order by ddh_runstart_td) AS "PATCH" from &P3_SCHEMA_NAME..ddl_log@&P3_DB_NAME.db_link GROUP BY DDH_DB_NM;I'm actually surprised that the code runs at all. I didn't think 'execute immediate' would know what to do with substitutions indicated as "&something." (I've typically seen that when substituting in dynamic HTML/Javascript code but maybe I'm learning something new). But since you already have vServer2 and vSchema2, I'd be more apt to code it as:
vStmt2 := 'select distinct DDH_DB_NM, max(DDH_SCHEMA_NR)keep(dense_rank last order by ddh_runstart_td) AS "PATCH" from ' ||
vSchema2 || '.ddl_log@' || vServer2 || '.db_link GROUP BY DDH_DB_NM';Hope this helps,
John

Ora-00604 error and ora 01000 error while report generation.

hi all,
I am trying to generate the multiple reports of same template through a program.
While this job is running, i get the following error at the BIP console and the reports don't get generated.
[101711_044115578][][EXCEPTION] java.sql.SQLException: ORA-00604: error occurred
at recursive SQL level 1
ORA-01000: maximum open cursors exceeded
ORA-00604: error occurred at recursive SQL level 1
ORA-01000: maximum open cursors exceeded
ORA-01000: maximum open cursors exceeded
Kindly help.
Thanks.

Lots of resources with a simple search to see what this is about, for example:
http://www.orafaq.com/wiki/ORA-01000
ORA-01000:     maximum open cursors exceeded
Cause:     A host language program attempted to open too many cursors. The initialization parameter OPEN_CURSORS determines the maximum number of cursors per user.
Action:     Modify the program to use fewer cursors. If this error occurs often, shut down Oracle, increase the value of OPEN_CURSORS, and then restart Oracle.
open_cursors parameter
http://download.oracle.com/docs/cd/E11882_01/server.112/e25513/initparams160.htm#REFRN10137
Oracle support note:
OERR: ORA-1000 maximum open cursors exceeded (Doc ID 18591.1)

Ora-01453

Similar Messages

Maybe you are looking for