AnsweredAssumed Answered

Duplicate assets and the Registration Service in ITAM

Question asked by hikonen on Oct 2, 2017
Latest reply on Oct 9, 2017 by Gale_Bacon

HI all,

I have a question about the ITAM/APM Registration Service and what it actually does.


We got APM/ITAM 12.9.04.
We are getting some duplicate assets listed in the Registration Service log file (ITAMRegSVC.log) [1]. We can identify them using the method in TEC1359234 [2]. We have the default configuration in APM for the CORA Configuration Settings, so we use the Registration Service (TEC1007672 [3]):
(Common) Enable CORA: False
(Common) Enable CORA Id Generation: True
(Registration Service) Enable Cora: True
(Registration Service) Enable CORA Id Generation: False

CORA settings in APM


If we create two assets with the same values (or no value) for all the CORA attributes:

  • Asset Name (ca_owned_resource.resource_name)
  • Serial Number (ca_owned_resource.serial_number)
  • Alt Asset ID (ca_owned_resource.resource_tag)
  • Host Name (ca_owned_resource.host_name)
  • MAC Address (ca_owned_resource.mac_address)
  • DNS Name (ca_owned_resource.dns_name)

both assets appear in APM and the duplicate asset UUID shows up in the Registration Service log file (ITAMRegSVC.log).  If we in APM change one of the assets' CORA fields to a unique value, the duplicate is removed from the Registration Service log file. This is all as expected. 


From TEC1131899 [3]: "When performing large data loads, or when integrated with SAM, using the registration service will add the assets and register them at a later time, in the background. (...) With the registration service method, duplicate assets may enter into the system, through manual data entry or the data importer.  This is fine, as the registration service will log the duplicate asset(s) and they will remain unregistered. You can review the registration service logs to identify the duplicate assets that have not been registered, then make corrections to the assets to provide uniqueness so they will register."


1) There seems to be two separate stages when a new asset is created in APM:
   a) Add the asset to APM / ca_owned_resource and usp_owned_resource tables

   b) Register the asset

Do I understand this correctly and if so, what exactly happens in each of the two stages?


2) What are the consequences if we do not resolve the duplicate assets and leave them as they are? What does it mean that the duplicates are not registered?

As far as I can see the duplicate assets exist in APM and the ca_owned_resource and usp_owned_resource tables and seem to behave normally. So does it matter that there are duplicates?



Best regards,

Heikki Ikonen



[1] =  "ERROR CA.Applications.RegistrationService.CORAProcessor - Duplicate asset found in CORA for: 884A2848A6654D459BC7827EEC90DFF4."


[2] = Registration Service log reports "Duplicate asset found in CORA" - How to troubleshoot this? 


[3] = Function to determine whether the asset is a unique or not: 


[4] = Differences between using the Registration Service vs. real time CORA settings (TEC1131899):