PROD-POM-BDI_PRICING_CLR_TX_CYCLE_JOB Failed In 1st Cycle
(Doc ID 2949899.1)
Last updated on MAY 19, 2023
Applies to:
Oracle Retail Integration Cloud Service - Version NA and laterInformation in this document applies to any platform.
Goal
PROD-POM-BDI_PRICING_CLR_TX_CYCLE_JOB failed in 1st cycle
We see this job is failed in 1st cycle and cloud team reported there is issue - failing due to below error. Since external is deployed at customer end, can you please check as the below importer job failure.
2023-05-16T06:32:34,426 [Thread-618] DEBUG Logger$debug - Status URL <URL>/external-batch-job-admin/resources/batch/jobs/Clearance_Tx_ImporterJob/267591
2023-05-16T06:32:34,426 [Thread-618] DEBUG Logger$debug - Checking status...
2023-05-16T06:32:34,451 [Thread-618] DEBUG Logger$debug - STATUS = STARTING
2023-05-16T06:32:34,452 [Thread-618] DEBUG Logger$debug - sleeping until status is COMPLETED or FAILED
2023-05-16T06:33:34,453 [Thread-618] DEBUG Logger$debug - Checking status...
2023-05-16T06:33:34,495 [Thread-618] DEBUG Logger$debug - STATUS = FAILED
2023-05-16T06:33:34,498 [Thread-618] ERROR Logger$error$0 - Error calling activity.
java.lang.RuntimeException: Error: ProcessName(Clearance_Tx_SubProcessFlow_From_RMS_To_EXTERNAL) ActivityName(Clearance_Tx_CheckImporterStatusActivity) : Batch job failed
--The importer job is failing at customer end. Please ask the customer to check as they own the importer packages
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 |