My Oracle Support Banner

Materialized View refresh causing MFT transfers to fail with "ORA-04021: timeout occurred while waiting to lock object" (Doc ID 2637183.1)

Last updated on APRIL 29, 2024

Applies to:

Oracle Managed File Transfer Cloud Service - Version 16.1.3 and later
Information in this document applies to any platform.

Symptoms

MFT transfers stop working. In the managed server .log file, there are database issues as shown below where the Caused By is ORA-04021: timeout occurred while waiting to lock object  :-
            
            

####<Feb 8, 2019, 12:07:10,76 AM UTC> <Error> <JTA> <xxxxx-wls-1.compute-599464009.oraclecloud.internal> <XXXX_server_1> <JCA-work-instance:JMSAdapter-24> <> <BEA1-74DC3FE61C6590600759> <9eb9f428-04e2-4e08-a6c2-45c1b2c562bc-014e5ad6> <1577059630076> <[severity-value: 8] [rid: 0:5] [partition-id: 0] [partition-name: DOMAIN] > <BEA-111007> <The commit operation for one-phase transaction BEA1-74DC3FE61C6590600759-4D465444617461536F757263655F47424D46544D54505F646F6D61696E on resource MFTDataSource_XXXX_domain encountered an error. oracle.jdbc.xa.OracleXAException
oracle.jdbc.xa.OracleXAException
    at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1806)
    at oracle.jdbc.xa.client.OracleXAResource.commit(OracleXAResource.java:794)
    at weblogic.jdbc.jta.DataSource.commit(DataSource.java:1142)
    at weblogic.transaction.internal.XAServerResourceInfo.commit(XAServerResourceInfo.java:1558)
    at weblogic.transaction.internal.XAServerResourceInfo.commit(XAServerResourceInfo.java:625)
    at weblogic.transaction.internal.ServerSCInfo.startCommit(ServerSCInfo.java:644)
    at weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransactionImpl.java:2320)
    at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:3292)
    at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:3197)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:309)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:257)
    at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:389)
    at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:383)
    at oracle.tip.mft.system.TransactionManagerImpl.end(TransactionManagerImpl.java:161)
    at oracle.tip.mft.engine.qmessage.listener.BaseQueueMessageListener.onMessage(BaseQueueMessageListener.java:216)
    at oracle.tip.mft.jms.adapters.JCAJmsMessageProcessorService$1.onMessage(JCAJmsMessageProcessorService.java:71)
    at oracle.tip.mft.transport.adapter.impl.jms.JMSBindingListenerImpl.post(JMSBindingListenerImpl.java:84)
    at oracle.tip.adapter.sa.impl.inbound.JCAInboundListenerImpl.onMessage(JCAInboundListenerImpl.java:226)
    at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:666)
    at oracle.tip.adapter.jms.inbound.JmsConsumer.doSend(JmsConsumer.java:705)
    at oracle.tip.adapter.jms.inbound.JmsNativeConsumer.sendInboundMessage(JmsNativeConsumer.java:104)
    at oracle.tip.adapter.jms.inbound.JmsNativeConsumer.send(JmsNativeConsumer.java:66)
    at oracle.tip.adapter.jms.inbound.JmsConsumer.runInbound(JmsConsumer.java:929)
    at oracle.tip.adapter.jms.inbound.JmsConsumer.run(JmsConsumer.java:846)
    at oracle.tip.adapter.sa.impl.fw.jca.work.WorkerJob.go(WorkerJob.java:53)
    at oracle.tip.adapter.sa.impl.fw.common.ThreadPool.run(ThreadPool.java:281)
    at java.lang.Thread.run(Thread.java:748)
Caused By: java.sql.SQLException: ORA-04021: timeout occurred while waiting to lock object



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
References


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