My Oracle Support Banner

Polling using Database Adapter Fails: java.sql.SQLException: [SQL0913] Row or object (Doc ID 2801916.1)

Last updated on AUGUST 25, 2021

Applies to:

Oracle SOA Suite - Version 12.2.1.4.0 and later
Information in this document applies to any platform.

Symptoms

After upgrading to SOA 12.2.1.4.0 and JDE 9.2, database polling via the DbAdapter fails with the following error.


ERROR
-----------------------
[2021-05-25T14:20:00.803-05:00] [WLS_SOA1] [ERROR] [] [oracle.soa.adapter.db.inbound] [tid: DaemonWorkThread: '81' of WorkManager: 'default_Adapters'] [userId: ] [ecid: 9ea24eb3-09c3-411a-937b-df95a9d902ea-00003cf0,0] [APP: soa-infra] [partition-name: DOMAIN] [tenant-name: GLOBAL] [composite_name: ...] [composite_version: ...] [service_name: ...] Encountered a fatal exception while polling. Will continue polling but with minimal logging. Please investigate the fault and manually stop polling from the console if in development and this appears to be a modeling mistake. BINDING.JCA-11624[[
DBActivationSpec Polling Exception.
Query name: [...], Descriptor name: [...]. Polling the database for events failed on this iteration.
Caused by java.sql.SQLException: [SQL0913] Row or object ... in ... type *FILE in use..
  This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "--913" to your deployment descriptor (i.e. weblogic-ra.xml). This polling process will shut down, unless the fault is related to processing a particular row, in which case polling will continue but the row will be rejected (faulted).

at oracle.tip.adapter.db.exceptions.DBResourceException.createNonRetriableException(DBResourceException.java:690)
at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:656)
at oracle.tip.adapter.db.exceptions.DBResourceException.inboundReadException(DBResourceException.java:491)
at oracle.tip.adapter.db.InboundWork.handleException(InboundWork.java:1023)
at oracle.tip.adapter.db.InboundWork.runOnce(InboundWork.java:917)
at oracle.tip.adapter.db.InboundWork.run(InboundWork.java:635)
at oracle.tip.adapter.db.inbound.InboundWorkWrapper.run(InboundWorkWrapper.java:43)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:184)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:209)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:633)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:39)
Caused by: java.sql.SQLException: [SQL0913] Row or object ... in ... type *FILE in use.
at com.ibm.as400.access.JDError.createSQLExceptionSubClass(JDError.java:895)
at com.ibm.as400.access.JDError.throwSQLException(JDError.java:682)
at com.ibm.as400.access.AS400JDBCStatement.commonExecute(AS400JDBCStatement.java:1032)
at com.ibm.as400.access.AS400JDBCPreparedStatement.executeUpdate(AS400JDBCPreparedStatement.java:1827)
at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:170)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:892)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
at org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
at org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.writesCompleted(DatabaseAccessor.java:1845)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.commitTransaction(DatabaseAccessor.java:428)
at org.eclipse.persistence.internal.sessions.AbstractSession.basicCommitTransaction(AbstractSession.java:820)
at org.eclipse.persistence.sessions.server.ClientSession.basicCommitTransaction(ClientSession.java:185)
at org.eclipse.persistence.internal.sessions.AbstractSession.commitTransaction(AbstractSession.java:1024)
at oracle.tip.adapter.db.inbound.PollingStrategy.commitTransaction(PollingStrategy.java:527)
at oracle.tip.adapter.db.InboundWork.transactionalUnitDirectly(InboundWork.java:1828)
at oracle.tip.adapter.db.InboundWork.transactionalUnit(InboundWork.java:1671)
at oracle.tip.adapter.db.InboundWork.runOnce(InboundWork.java:894)
... 11 more

]]



BUSINESS IMPACT
-----------------------
The issue has the following business impact:
This is occurring in production. There is a workaround in place but this issue needs to be resolved in the long-term.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.