Multiple D&B Update Manager (Siebel) Processes

By default the dnbtask.cfg file uses the tables updated to set up five simultaneous tasks. The DNBUpMgrSieb portion of the file looks as follows:

[Siebel]
Task1 = UPDATE_SIEBEL_ACCOUNT
Task2 = UPDATE_INDUST, COMMIT, UPDATE_SIEBEL_INDUST, COMMIT,

UPDATE_SIEBEL_SYNONYM 
Task3 = UPDATE_SIEBEL_ADDR_PHY, COMMIT, UPDATE_SIEBEL_ADDR_MAIL
Task4 = UPDATE_SIEBEL_CONTACT 
Task5 = UPDATE_SIEBEL_LOC1, COMMIT, UPDATE_SIEBEL_LOC2, COMMIT, UPDATE_SIEBEL_LOC3

You can edit the file to change the number of parallel processes created. However, the order of the updates within individual tasks is important; for example UPDATE_INDUST must be done before UPDATE_SIEBEL_INDUST. Use caution when updating the DNBUpMgrSieb portion of the dnbtask.cfg file.

Caution: If you have modified the RTI configuration file to insert new accounts into the Siebel Accounts table, then do not run the multiple task process. Instead you must run the single task D&B Update Mgr (Siebel) server component. Make sure you have modified the dnbmaps.sql file used by the single task server component. The order of the updates is critical to data integrity if new accounts are being added.