My Oracle Support Banner

BDF NameMatchStaging Error In Production (Doc ID 2593181.1)

Last updated on OCTOBER 29, 2019

Applies to:

Oracle Financial Services Behavior Detection Platform - Version 8.0 and later
Information in this document applies to any platform.

Symptoms

On : 8.0.* version, Web UI

ACTUAL BEHAVIOR
---------------
BDF NameMatchStaging error in production

While running FCCM 804 batch in prod, NameMatchStaging bdf job has given error.
There a lot of chainese and Japanese char in candidate file.
With same file sometimes it work sometime it does not work.

Error in the log

09/09/2019 20:36:25 WARN : Thread ID = 140129370892032:  fuzzy_match:   File = FNMThread.cc:  Line = 1618:  Unsupported character, skipping
09/09/2019 20:36:25 WARN : Thread ID = 140129360402176:  fuzzy_match:   File = FNMThread.cc:  Line = 1618:  Unsupported character, skipping
09/09/2019 20:36:25 WARN : Thread ID = 140129280718592:  fuzzy_match:   File = FNMThread.cc:  Line = 1618:  Unsupported character, skipping
09/09/2019 20:36:25 FATAL : Thread ID = 140129517684480:  fuzzy_match:   File = UtilityFunctions.cc:  Line = 71:  Unsupported byte sequence
09/09/2019 20:36:25 WARN : Thread ID = 140129370892032:  fuzzy_match:   File = FNMThread.cc:  Line = 1618:  Unsupported character, skipping

Changes

 

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
Changes
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.