My Oracle Support Banner

"NameMatchStaging" Failing with returned status: 255 (Doc ID 2589126.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

"NameMatchStaging" failing in production environment.

Error in NameMatchStaging.log.

2019-08-22 17:30:21,628 [main] FATAL - NameMatchStaging - Message 10020: Error executing command ../fuzzy_match/bin/fuzzy_match.sh -t /OFSAA/ofsaaapp/OFSAAPROD/bdf/data/temp/NameMatchStaging.t
arget -c /OFSAA/ofsaaapp/OFSAAPROD/bdf/data/temp/NameMatchStaging.candidate -r /OFSAA/ofsaaapp/OFSAAPROD/bdf/data/temp/NameMatchStaging.result, returned status: 255
2019-08-22 17:30:21,630 [main] FATAL - NameMatchStaging - Message 10200: com.ofss.bdf.common.FatalException: Error executing command ../fuzzy_match/bin/fuzzy_match.sh -t /OFSAA/ofsaaapp/OFSAAP
ROD/bdf/data/temp/NameMatchStaging.target -c /OFSAA/ofsaaapp/OFSAAPROD/bdf/data/temp/NameMatchStaging.candidate -r /OFSAA/ofsaaapp/OFSAAPROD/bdf/data/temp/NameMatchStaging.result, returned sta
tus: 255
       at com.ofss.bdf.datamap.NameMatchProcessor.doProcessing(Unknown Source)
       at com.ofss.bdf.datamap.DerivedProcessor.process(Unknown Source)
       at com.ofss.bdf.datamap.DataMapProcessor.process(Unknown Source)
       at com.ofss.bdf.common.BDFProcessLauncher.main(Unknown Source)

2019-08-22 17:30:21,632 [main] FATAL - NameMatchStaging - Message 10018: Component exited with an error

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.