The asset management sandbox has a number of bugs that have progressively been fixed but issues still exist with AM 7.6.4 SP1: - the AL's pushing to create the sandbox CI's don't use matching Ids but use a list of computer system attributes. This means that attributes in other classes and bespoke attributes in the computer system can't be updated. - BMC changed the push fields to use matching Ids. CI's that are weak children cannot then be updated as the system thinks you are trying to set certain hidden fields that it won't allow. - the recon process is triggered when the sandbox CI is saved. If you create a relationship to a new CI then, depending on the performance of your system, it is possible that the recon job identifies the new CI but not relationship as it is created after the CI. The final activity of the recon job deletes the CI which then deletes the relationship before it is merged with the production dataset. - you can't create a new parent CI from an existing CI as the workflow hardcodes the new CI as a child (even though the partent/child option is presented to you) - you can't create a new CI with the same name as an existing CI as the recon engine will match the new one to the old one (if you wanted to modify the old one you would have searched for it)
The reason for leaving it on is that the attributes in the CI's then get flagged as having been last updated via the sandbox. This then allows you to control which attributes are updated by which source datasets. Without the sandbox enabled you may need to add the target dataset to the precedence set which can cause unexpected results. The issue reported by Tricia should be traceable by AL logging and relatively easily fixed. I would advise leaving it on unless the issues found make it impossible to use. Cheers Peter -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Lyle Taylor Sent: 15 September 2011 16:35 To: [email protected] Subject: Re: Turning off Sandbox for the CMDB Did you add any custom workflow such as data validation to the CMDB? The Sandbox Create stuff is coming from something in the update process in the sandbox failing and not completing. Any workflow such as validations that stop normal processing will foul that up. The first step in the sandbox process is to create a frame of the existing "gold" CI, which it names Sandbox Create. It then pulls in the rest of the information and adds the changes that were made by the user. It then reconciles that back into the gold dataset. The big problem is that that set of operations don't happen as a transaction, so if anything fails along the way, you're left with incomplete data, and the reconciliation still runs and pushes that incomplete data back into your gold dataset. I thought they had supposedly fixed that in 7.5. I know that my recommendation for 7.1 (CMDB 2) is to turn it off as it provided no value in most cases and generally caused issues. Not sure how that applies to 7.5, though... Lyle -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Tricia Sent: Wednesday, September 14, 2011 7:16 PM To: [email protected] Subject: Turning off Sandbox for the CMDB We are facing a major problem with our CMDB (Asset Management 7.5, ARS 7.5). The CIs are being renamed to Sandbox Create at random times. It is happening with great frequency and BMC Support has no idea how to resolve it. We are not using the CMDB with any discovery tools or any data imports. So I am planning on turning off the Sandbox feature. Are there any issue I should be aware of? Has anyone else done this? Thanks Tricia ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
