Verifying duplicates

Verification for duplicates searches for duplicated configuration items based on naming rule field values in the database.

With the repair option enabled, the duplicated objects are merged. After the merge, the durable object remains in the database, and the transient object is deleted.
The merge is performed by several threads in parallel. The default number of threads is 5. You can change the number of threads in the collation.properties file by setting the com.ibm.cdb.topomgr.dataverification.generator.ThreadCount flag to an appropriate number, as in the following example:
  • com.ibm.cdb.topomgr.dataverification.generator.ThreadCount=10
You must restart the TADDM server after you change the number of threads.
Some errors might occur during the merge of the objects. The cause of the errors is included in a log file.
  • ERROR_INVALID_DURABLE_GUID
  • ERROR_INVALID_TRANSIENT_GUID
The cause of the errors are missing aliases in the aliases table or an invalid object. You must wait for the cleanup agents to delete the invalid objects.

To verify duplicates, run one of the following options:

  • verify-data.sh -v dup [-a repair]
  • verify-data.bat -v dup [-a repair]