Transfer Purge Job Is Running Long In Hourly Cycle - 12
(Doc ID 2847715.1)
Last updated on FEBRUARY 09, 2022
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version 19.1 and laterInformation in this document applies to any platform.
Symptoms
Below points are not working as expected.
1) If any scheduled job is running long, It has to notify via long-running alert, but it’s not working.
Currently, Transfer_purge_job is been running long in Hourly Cycle - 12 (More than 150 mins) but has not yet been completed
2) If any job is running long in the previous cycle, the next cycles shouldn’t start, and moreover, if the previous cycle is taking longer than normal, the next cycles have to be skipped. But it’s not working.
Transfer_purge_job is been running long in Hourly Cycle - 12 but in the next cycles (13,14 & 15 cycles) other than this job, 3 more jobs – cost change, cost event & item loc purge jobs have been enabled to run, those are already completed till 15 cycles.
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 |
| References |