Postprocessing job 501 has been failed with maximum_match_score parameter for Match Scoring missing
(Doc ID 2835003.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
---------------
issue with the post processing job
/bns/aml/ofsaa/fccm8/behavior_detection/algorithms/MTS/bin/start_mantas.sh 501
01/10/2022 14:07:22 DEBUG : Thread ID = 139827022395136: mantas: File = dbparameter.cc: Line = 51: SELECT ALGORITHM_NM FROM amliatommso.KDD_PARAM_SET a WHERE PARAM_SET_ID = 750700001
01/10/2022 14:07:22 DEBUG : Thread ID = 139827022395136: mantas: File = dbparameter.cc: Line = 134: SELECT a.PARAM_NM, a.PARAM_TYPE_CD, b.DEFAULT_VALUE_TX FROM amliatommso.KDD_ALGORITHM_PARAM a, amliatommso.KDD_PARAM_DEFAULT b WHERE a.ALGORITHM_NM = 'Match Scoring' AND a.ALGORITHM_NM = b.ALGORITHM_NM AND a.PARAM_NM = b.PARAM_NM
01/10/2022 14:07:23 DEBUG : Thread ID = 139827022395136: mantas: File = dbparameter.cc: Line = 134: SELECT a.PARAM_NM, a.PARAM_TYPE_CD, b.PARAM_VALUE_TX FROM amliatommso.KDD_ALGORITHM_PARAM a, amliatommso.KDD_PARAM_BINDING b WHERE b.PARAM_SET_ID = 750700001 AND a.PARAM_NM = b.PARAM_NM AND a.ALGORITHM_NM = b.ALGORITHM_NM
01/10/2022 14:07:23 FATAL : Thread ID = 139827022395136: Match Scoring: File = MatchScoringRun.cc: Line = 224: Required maximum_match_score parameter for Match Scoring missing
01/10/2022 14:07:23 FATAL : Thread ID = 139827022395136: Match Scoring: File = mantas.cc: Line = 476: caught exception:
ERROR: { module: Match Scoring } { subsystem: N12MatchScoring15MatchScoringRu } { message: Required maximum_match_score parameter for Match Scoring missing }
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 |