Messages Did Not Received In The IPEs Screening in TF (Doc ID 2987962.1)

Last updated on NOVEMBER 23, 2023

Applies to:

Symptoms

User reported issue with communications issue which generated connectivity problems in the different infrastructure components for the Sanction Screening solution

we faced a communications issue which generated connectivity problems in the different infrastructure components for the Sanction Screening solution. Among others (failure of jobs, retriggering of multiple messages, etc), this issue prevented some payments which were received in the IPEs Screening platform to be properly recorded in the Oracle DB, and therefore these messages were never screened. Neither any information of such messages were recorded in the DB and we experienced data loss for such messages.

So at the end, the current product solution never responded to the caller system, and we do not have any means of re-processing these messages. The only information we have of those messages which were received is the one stored in the IPEs logs during the occurrence of the issue, which is not helpful to generate a timely response.

We urgently require Oracle to evolve the product and/or develop a solution which will ensure the resilience of the product when such external events occur. This is, record or keep (queue, memory, ?) these unprocessed messages so the system will relaunch / reattempt so they are recorded properly in the DB and process in subsequent screening process (parsing + screening). Otherwise, we will not be able to provide the required responses for the transaction filtering real time functionality in this critical system.

Changes

NA

Cause

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