This error "ARERR [120092] The dataset ID and Reconciliation Identity combination is not unique" means that the same reconciliation identity cannot be assigned to another CI in the same dataset. This is expected behavior. To resolve the issue, you must find out why the reconciliation job was trying to assign the same reconciliation ID to another CI in the same dataset.
The class mentioned in the above error message is BMC.CORE:BMC_ComputerSystem. There are out of the box and custom identification rules for each class.
The following example shows the BMC_ComputerSystem class identification rules.
The priorities shown in the example show the sequence in which the rules check for CI duplication in the target dataset (BMC.ASSET). The priority proceeds to the next available rule until it reaches the final one.
Let’s assume that the following CI records are for BMC.CORE:BMC_ComputerSystem.
| Name | Dataset | Reconciliation ID | Serial Number |
|---|---|---|---|
Dell 2500 series laptop | BMC.ADDM |
| 686868 |
Dell 2500 series laptop | BMC.ASSET | OI-E7315F17CAC04E8AB89C2D5E8E924595 | 686868 |
HCL 200 Series Laptop | BMC.ADDM | 0 | 686868 |
If we compare the above record table with the Identification rule for BMC_ComputerSystem class, the serial number is common for Dell and HCL laptops. Let us further assume that the fields for the Virtual and PartiionID attributes are NULL for Dell and HCL Laptop CI records. In this case, only the attribute Serial Number carries a value and this attribute shares the same number between these two CI records.
When the reconciliation job runs, the CI passes the first and second priority rule. After that, the job identifies the CI on the third rule based on the value of Serial Number considering that the isVirtual and PartiionID had NULL values. The job tries to assign the reconciliation ID OI-E7315F17CAC04E8AB89C2D5E8E924595 to the CI representing the HCL 200 Series Laptop in BMC.ADDM. This results in the error being logged.
