Resolution:
Usage of dbloader in clustered env results in duplcate records in MCT, PRINCIPALKEY, PRODUCTKEY, GOLDENCOPY and RELATIONSHIP table

Environment:

TIBCO Product name and version: TIBCO Collaborative Information Manager 7.X.X and 8.X.X
Operating System(s): All Operating Systems

Symptoms:
When dbloader is executed in a clustered environment  with 4 instances on CIM, then dbloader is executed 4 times resulting in 4X records in Repository/Master Catalog.

Cause:
When dbloader is executed a message would be sent to the AsyncCallTopic. And as all the instances in the cluster would be listening on to this TOPIC, each of the instance would try to process that message which results multiple executions of dbload into master catalogs.


Resolution:
In a 4 instance clustered environment for example, it is required to set the poolsize for asynccall topic receiver and sender to be 0 on 3 instances of cluster and set to 1 in only on 1 instance of the cluster.

Attachments:


References:

None