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"
