Hi Guys, Even we had same experience post DDM run. Fortunately thsi has been loddeg as defect and there is a workaround and steps to fix these issues caused via DDM run as well as UDM. There is a blog which explains about the new architecture of Asset forms AST:Attributes and related information. Please check the following: KA418342 - Caused due to DDM SW00460222 - Caused due to UDM
Blog https://communities.bmc.com/community/bmcdn/bmc_it_service_support/bmc_asset_management/blog/2014/04/08/the-pulse-allowing-users-to-override-discovered-asset-data Regards, Aditya Shrivastava On Sat, May 2, 2015 at 3:46 AM, Jamie <[email protected]> wrote: > We ran into this while using DDM, but before we went live with our > upgrade. The issue is that the DDM scripts are using instance ID to > migrate the data and never finds a match so it creates a duplicate record. > If you were to modify the DDM script to use Recon ID instead, I believe > that will help you going forward. There is still a slight risk that DDM > migrates the record from the other data set, because there is no logic that > says to only migrate the BMC.Asset record to AST:Atriubtes, however in most > cases your BMC.Asset entry is likely to be the one with the latest update > so that will likely be the one to be sent across last. > > As far as fixing the duplicates, I tried to go through my old emails to > see what exactly we did and I couldn't find anything. Trying to remember > from my memory, I believe I wrote a script to find which entry in the > AST:Attributes table matched the record in the BMC.Asset and then deleted > the others. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
