File Naming Issue Post Deadlock Conditions While Rating An EDR Through Pipeline (Doc ID 2152335.1)

Last updated on JUNE 26, 2024

Applies to:

Goal

Having few records getting ignored by rating pipeline due to the error "Edr has been ignored due to discount account deadlock.Could not get balance for BG/Resource due to deadlock, the transaction will be cancelled and retried".
The IgnoreEDROnDeadlock flag is set to TRUE for all the pipelines. Understand from some of the documents that this deadlock issue is common when multiple pipelines run in parallel and have to recycle these records at a later point of time.

However, the issue is with the name of the file containing the event data records (EDR) which were rejected. The issue is as below:

1. First let us say a file F1 is being processed by a pipeline. All the EDRs ignored in this file due to deadlock condition will be moved to a file F1_<seqno1> in the OutputPath configured in the EXT_OutFileManager. The seqno1 is the sequence being generated by the corresponding deadlock sequence defined.

2. Once we recycle the file F1_<seqno1>, suppose there are EDRs from this file which are again ignored by rating pipeline due to deadlock condition, then a new file F1_<seqno1>_<seqno2> is being generated with those ignored records.

3. Now, as few EDRs are being ignored after every recycle of the ignored EDRs, the file name keeps getting bigger. i.e., after 5 recycles it will be like F1_seqno1_seqno2_seqno3_seqno4_seqno5.

As we understand that these discount deadlocks cannot be avoided, we want to know if the file naming logic can be modified i.e., instead of sequence getting appended to the filename, can we get the sequence replaced. Ex: After 5 recycles, can we have the file name as F1_seqno5 instead of F1_seqno1_seqno2_seqno3_seqno4_seqno5?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.