Applies to Product - FnO Platform
What’s happening?
The batch job UMAX: Age customer balances (weekly) encountered errors, specifically with the 'ICM_DIC_CustAgingSnapshot' class, resulting in multiple subtasks failing due to database deadlocks.
Reason:
The underlying cause of this was identified as database deadlocks occurring during the execution of the batch job, where multiple processes were competing for the same lock resources.
Resolution:
- This was noted to have occurred only twice and has not been reported in the last couple of weeks.
- The customer agreed to archive the case as the problem appears to be intermittent.
- It is recommended to monitor the batch job for any future occurrences of deadlocks. If the issue persists, further investigation into the database locking mechanisms may be necessary.
- If the issue reoccurs then we should redirect this kind of issues to Job Owning Team(AX - GFM - Accounts Receivable - Collections & Aging) as these kind of issues might happen due to some slow queries or long running queries or blockings from Job Owning Team tables and also it depends on parameters defined while generating the report.