FOTP Records Dropping Due To Special Chars
(Doc ID 2832337.1)
Last updated on NOVEMBER 28, 2022
Applies to:
Oracle Financial Services Behavior Detection Platform - Version 8.0 and laterInformation in this document applies to any platform.
Symptoms
On : 8.0.4 version, Web UI
ACTUAL BEHAVIOR
---------------
FOTP records dropping due to special chars being normalized by Data ingestion.
For the column Street Line1, due to the presence of German characters Data ingestion is normalizing it by introducing an extra char. Due to this extra char introduced by system the total length is getting exceeded leading to the complete FOTP record getting rejected.
Example:
upstream system are sending:
aaaaaaaa bbbbb ccccc dddddd Otto-Braun-StraÃe 99 99999 Berli = 60 chars
Data ingestion is loading:
AAAAAAAA BBBBB CCCCC DDDDDD OTTO-BRAUN-STRASSE 99 99999 BERLI = 61 chars
This is error in log.
2021-10-26 04:36:15,627 [BDFThread0] WARN : 31102FrontOfficeTransactionParty
- Message 31102: failed DB
validation. Reason: StreetLine1 [Exceeds Maximum DB Length of 60]: XABC
YABCDRÖM WEILE RAABESTRASSE 3 00000 TYSKLAND C/O STRACHW. Record will be
rejected.
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 |