Kathy, Unfortunately this is a "depends" answer. Depends on how many CI's are in your environment, depends on how clean and consistent your source data is. Depends on whether your BMC.ASSET data is consistent, it depends on whether your identification rules are clearly defined and consistent with your source and target data. Depends on how dynamic your data is (constantly changing or relatively consistent).
I rarely if ever experience an error free run in recon. However, reviewing the logs I typically am able to determine why the error occurred and what I can do to remediate the issue. Because of the configuration drift and the consistency of the procedures used to bring the physical CI in and out of the environment, maintenance is a constant in our environment. Typically the most common error that I come across when identifying CI's is the rule comes back with duplicates and thus cannot determine which CI to use the recon id from in identification. For new CI's this is not an issue since it does not find a match at all and will auto identify (if you have this enabled). If you provide more detail, we can probably point you in the right direction. Jim Coryat Senior Software Engineer Micron Technology Inc. From: Kathy Morris [mailto:[email protected]] Sent: Wednesday, February 26, 2014 2:59 PM Subject: CMDB 7.6.4 ** Hi, Sometimes when we run the reconciliation jobs, we find some of the CIs that are Dataset A do not make it to the BMC.ASSET. For example, the computer may have been created in BMC.ASSET, however the OS was not created in BMC.ASSET after reconciliation. OR The computer may exist in Dataset A, and not make it to BMC.ASSET after reconciliation. I know there is an error somewhere and I need to troubleshoot the logs. Just wondering if most people are able to run reconciliation with no errors or CIs dropped? Do you usually get 100% error free recon job runs? What is the norm? or is this just part of maintenance? _ARSlist: "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"
