IIR Multi Search Mode

(Doc ID 2165801.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Data Quality - Version 15.9 [IP2015] and later
Information in this document applies to any platform.


After upgrading to IP15, Search operation value is not getting appended as seen below (this value is provided in searchoperation tag in request xml):

e.g from non-upgraded env log file:

e.g from upgraded env log file:

It is expected that the "searchoperation" is appended to the RECORD_TYPE tag:


The issue can be reproduced at will with the following steps:

1) ssadq_cfg.xml file has the following:


2) Admin - DQ > Third Party > Vendor Parameter, added:

Append Contact Record Type Field 1 = WBC Search Operation Calc

If WBC Search Operation Calc = SearchByName, then assume that Append Contact Record Type Field 1 = "SearchByName".

3) Create a new Contact

4) Check the log:


The issue has the following business impact:
Currently in production, UCM application utilize ODQ multi-mode match function to provide other Westpac systems the capability of searching/matching customer records in UCM using different set of search/match rules and search definitions configured in ODQ Matching Server (Oracle OEMed version of IIR), hence multi-mode customer matching.


In a multi-languages/multi-modes search we expect customers to create multiple systems in IIR. However, in this case there is only one IIR System (SDF)

It was working before upgrade because we have not checked if the system exists or not until the fix for bug 14124150. With this fix, if the system does not exist we will use the base record type, ignoring the ‘Append Record Type Field,’ and the default system for the search.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms