Bookshelf Home | Contents | Index | PDF |
Siebel Data Quality Administration Guide > Administering Data Quality > Matching Data Using Batch Jobs > Example of Batch Data Matching Using the Universal ConnectorYou must run batch mode key generation on all existing records before you run real-time data matching. The Universal Connector requires generated keys in the key tables first before you can run real-time data matching. The key generation is done within the deduplication task, which is the reason for running deduplication on all existing records first. For more information about batch data cleansing and matching, see Batch Data Cleansing and Data Matching. The following procedure describes how to start a data matching batch job. To perform batch mode data matching
Full Data Matching JobsIn a full data matching job, the records for which you want to locate duplicates and the candidate records that can include those duplicates are defined by the same search specification. A full data matching job is specified with the value Yes in the DQSetting parameter, see Table 21. Full data matching jobs are useful when:
A typical example of a command for a full data matching job is as follows: run task for comp DQMgr with DqSetting="'','Yes','account_match.xml'", bcname=Account, bobjname=Account, opType=DeDuplication, objwhereclause="[Name] LIKE 'A*'" Jobs like this that perform data matching for a subset of records are still considered to be full data matching jobs because the data to be checked does not depend on earlier data matching. Incremental Data Matching JobsIf you want to perform data matching for some number of nonexclusive subsets of the records in a business component, such as all the records that have been created or updated since you last ran data matching, use a WHERE clause that includes an appropriate timestamp, and also adjust the DqSetting clause of the command as shown in Table 21. This kind of job is considered an incremental data matching job, because data matching was done earlier and does not need to be redone at this time. In an incremental data matching batch job, the records for which you want to locate duplicates are defined by the search specification, but the candidate records that can include those duplicates can be drawn from the whole applicable database table. Incremental data matching batch jobs are useful if you run them regularly, such as once a week. A typical example of a command for an incremental data matching job is as follows: run task for comp DQMgr with DqSetting="'','No',''", NOTE: If you do not specify the DQSetting parameter, or leave the second value of the DQSetting parameter blank, the job will be an incremental data matching job. |
Siebel Data Quality Administration Guide | Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |