My Oracle Support Banner

UCM Batch Manager Is Not Marking Record as Suspect (Doc ID 1460785.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Data Quality Matching Server - Version 8.1.1.7 [21238] and later
Information in this document applies to any platform.
***Checked for relevance on 13-Dec-2013***

Symptoms

When running UCM Batch Process to load a record that should be reviewed it's not working.

Suspect Match functionality is enabled this way the record should be marked as Suspect and a record should be created in table S_DEDUP_RESULT.

Logs shows the process passing by the Review step but no record was created in S_DEDUP_RESULT nor the record was marked as Suspect.

StpExec Create 4 000003b34fb506f4:0 2012-05-18 15:01:22 Instantiating step definition 'Match on?'.
StpExec Create 4 000003b34fb506f4:0 2012-05-18 15:01:22 Instantiating step definition 'CDM Match'.
StpExec Create 4 000003b34fb506f4:0 2012-05-18 15:01:25 Instantiating step definition 'Enumarate Match Output Propset'.
StpExec Create 4 000003b34fb506f4:0 2012-05-18 15:01:25 Instantiating step definition 'Match Result?'.
StpExec Create 4 000003b34fb506f4:0 2012-05-18 15:01:25 Instantiating step definition 'Prep Propset [Review]'.
StpExec Create 4 000003b34fb506f4:0 2012-05-18 15:01:25 Instantiating step definition 'HasMore?'.
StpExec Create 4 000003b34fb506f4:0 2012-05-18 15:01:25 Instantiating step definition 'Execute Propsets'.

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


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.