My Oracle Support Banner

Money Market: MT350 Message EMS_OUT Job Fails In MSTB_DLY_MSG_OUT (Doc ID 2749660.1)

Last updated on FEBRUARY 09, 2021

Applies to:

Oracle FLEXCUBE Universal Banking - Version 14.1.0.0.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR:
----------------------
MT350 message EMS_OUT job fails in Table(MSTB_DLY_MSG_OUT)

EXPECTED BEHAVIOR:
-------------------------
MT350 message EMS_OUT job should to update in MSTB_DLY_MSG_OUT

STEPS:
--------
The issue can be reproduced at will with the following steps:
1. As per the routing rule maintained, system is routing the MT350 message handoff into “/u01/FCUBS/EMS/OUT/FC” folder
2. after message handoff, the EMS_OUT job is not updating MSTB_DLY_MSG_OUT.MSG_STATUS from G to H.
3. re-picking the same message again for message handoff and failing in insert into mstb_dly_swift_msg_notif table with the primary key violation.

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


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