Duplicate identification reports
Control Desk does not remove duplicate assets and configuration items (CIs) automatically. Therefore, reports can be used as a guide when cleaning duplicates from your system.
When are the reports run?
When you are upgrading from an earlier version of Control Desk, duplicates can exist in the database. These reports, together with the cleansing tool, CCIGuidLoader, can be used to clean your environment. In this scenario, when you upgrade Control Desk, you need to run the cleansing tool to reconcile data that is already in your database. You then run the reports, which identify duplicate entries that you can remove from your database manually. At this juncture, you can run the reports again to ensure that all duplicates are removed.
Alternatively, when you change the entries in the CleansingRules.xml or CDMMapping.xml files, it can be necessary to run the cleansing tool and the reports again. For example, if you change the rules to accommodate new data sources that you are importing into Control Desk, you need to run the cleansing tool. The tool assigns integration identifiers to the assets and CIs.
How are the reports run?
The reports are run with Tivoli's process automation engine report mechanisms. Use the Report Administration application to generate a request page before the report is run.
What reports are provided?
| Report | Description |
|---|---|
| ci_duplicate_group | Identifies duplicate Authorized
CIs based on the integration identifier. Columns, ordered by integration identifier:
|
| actci_duplicate_group | Identifies duplicate Actual
CIs based on the integration identifier. Columns, ordered by integration identifier:
|
| asset_duplicate_group | Identifies duplicate Authorized
IT Assets based on the integration identifier. Columns, ordered by integration identifier:
|
| deployedasset_duplicate_group | Identifies duplicate Authorized IT Assets based
on the TLOAMNRSGUID. Columns, ordered by TLOAMNRSGUID:
|