BDI_PRICING_CLR_TX_CYCLE_JOB Failed with java.lang.RuntimeException: DATA_SET_ID(%n) is associated with a different TRANSACTION_ID(%n)
(Doc ID 2937995.1)
Last updated on APRIL 03, 2023
Applies to:
Oracle Retail Integration Cloud Service - Version 19.1 to 19.1 [Release 19.1]Information in this document applies to any platform.
Goal
BDI_PRICING_CLR_TX_CYCLE_JOB has failed with below error in RMS BDI Job Admin log:
2023-03-20T15:15:50,741 [[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR DownloaderInterfaceJobListener - DATA_SET_ID(%n) is associated with a different TRANSACTION_ID(%n).
2023-03-20T15:15:50,742 [[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR DownloaderInterfaceJobListener - Error in beforeJob for JOB_NAME(Clearance_Tx_DownloaderAndTransporterToExternalJob) EXECUTION_ID(1283500) INTERFACE_MODULE(Clearance_Tx)
java.lang.RuntimeException: DATA_SET_ID(%n) is associated with a different TRANSACTION_ID(%n).
Solution
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
| Goal |
| Solution |
| References |