Bulk Recovery Job Fails with Cannot set auto-commit mode when using distributed transactions
(Doc ID 3061882.1)
Last updated on DECEMBER 03, 2024
Applies to:
Oracle SOA Suite - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
Performing bulk retry from em console is throwing below error in the logs:
<Error> <oracle.soa.scheduler> <BEA-000000> <ESS-05110 An error occurred while retrieving the metadata object with name Schedule://oracle/apps/ess/custom/soa/BULKRECOVERY of type Schedule.
oracle.as.scheduler.MetadataServiceException: ESS-05110 An error occurred while retrieving the metadata object with name Schedule://oracle/apps/ess/custom/soa/BULKRECOVERY of type Schedule.
at oracle.as.scheduler.metadata.mds.MetadataGetDelegator.getMetadataObject(MetadataGetDelegator.java:273)
at oracle.as.scheduler.metadata.mds.MetadataGetDelegator.getMetadataObject(MetadataGetDelegator.java:187)
at oracle.as.scheduler.metadata.mds.MetadataGetDelegator._get(MetadataGetDelegator.java:175)
at oracle.as.scheduler.metadata.mds.MetadataGetDelegator.get(MetadataGetDelegator.java:135)
at oracle.as.scheduler.metadata.mds.CoreMDSMetadataServiceImpl.getMetadata(CoreMDSMetadataServiceImpl.java:349)
at oracle.as.scheduler.metadata.mds.MDSMetadataServiceImpl.getMetadata(MDSMetadataServiceImpl.java:187)
at oracle.as.scheduler.metadata.mds.MDSMetadataServiceImpl.getScheduleDefinition(MDSMetadataServiceImpl.java:764)
at oracle.as.scheduler.metadata.MetadataServiceSecurityForwarder$47.run(MetadataServiceSecurityForwarder.java:1264)
at oracle.as.scheduler.metadata.MetadataServiceSecurityForwarder$47.run(MetadataServiceSecurityForwarder.java:1259)
Caused By: oracle.mds.exception.MDSRuntimeException: java.sql.SQLException: Cannot set auto-commit mode when using distributed transactions
at oracle.mds.persistence.stores.DBMetadataStore.initializePartitionID(DBMetadataStore.java:1540)
at oracle.mds.persistence.stores.DBMetadataStore.getPartitionID(DBMetadataStore.java:824)
at oracle.mds.persistence.stores.DBMetadataStore.getConnection(DBMetadataStore.java:772)
at oracle.mds.persistence.MetadataStore.getConnection(MetadataStore.java:527)
at oracle.mds.internal.persistence.PersistenceUtils.getConnection(PersistenceUtils.java:1087)
at oracle.mds.persistence.DelegatingMetadataStoreConnection.getOrCreateDelegatee(DelegatingMetadataStoreConnection.java:260)
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 |
Cause |
Solution |