What exactly is your colleague trying to achieve by manually updating CIs in the topo dataset?
CIs are created in this dataset by the discovery tool when they are first discovered. The discovery tool has a policy to deal with CIs that it once discovered but which it now no longer finds. The default is that if a CI is not found for three consecutive scans then the CI is soft deleted in the CMDB during synchronisation. When a CI is soft deleted all relationships are also soft deleted. This is happening when your colleague updates the CIs manually. The errors you are getting may be because the discovery tool has found a new child CI related to one that your colleague has manually deleted. The sync process will create the new child CI and then try and create the relationship. Because the parent is soft deleted you will get the error. The solution is for the topo dataset only to be updated by the discovery tool. Cheers Peter _____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Kathy Morris Sent: 22 February 2010 19:28 To: [email protected] Subject: Re: Topology Dataset Discovery 1.6 ** I have not had problems with RE either. I am totally supportive of using RE. We are migrating onto another Remedy new system, which will be designed better. If you wanted to mark an asset as soft delete (MarkAsDeleted) - where would you do this? CMDB Asset? another dataset? -----Original Message----- From: Roger Justice <[email protected]> To: [email protected] Sent: Mon, Feb 22, 2010 1:31 pm Subject: Re: Topology Dataset Discovery 1.6 You have most of the concept. No you cannot go into the TOPO dataset and set the entry as marked as deleted since the TOPO API call was not written to allow for this to work. I have worked with the RE since version 2.0 and have not had any problems. I would impress on the developer that you are working with that BMC Support will not support the population by scripts and when they want to upgrade to Atrium Core 7.5 or later and want to use the normalization engine they will have more problems. -----Original Message----- From: Kathy Morris <[email protected]> To: [email protected] Sent: Mon, Feb 22, 2010 1:23 pm Subject: Re: Topology Dataset Discovery 1.6 ** I know TOPO is populated from Discovery and bmc.asset is the gold set. My question is - can the developer open TOPO and set assets to MarkAsDelete directly? My understanding is that TOPO is updated directly from the discovery and I would not go into TOPO to set the assets as MarkAsDeleted, however I was just wondering if I misunderstanding something here. And now we are receving several of these errors: "cannot set to as Markasdeleted to "NO" on the relationship instance because of the relationship endpoints are MarkAsDeleted. Are we getting this error because we are doing something wrong? The developer I work with does not want to use reconcilation because his scripts are doing the job and he said the reconcilation did not work for them. ----Original Message----- From: Roger Justice <[email protected]> To: [email protected] Sent: Mon, Feb 22, 2010 1:13 pm Subject: Re: Topology Dataset Discovery 1.6 The golden dataset is BMC.ASSET. The dataset that Discovery populates is called TOPO or something similar. Since you are not using the RE you are not using CMDB as designed and it may not be possible toi fix this issue. Is there a reason that you are not using the RE. -----Original Message----- From: Kathy Morris <[email protected]> To: [email protected] Sent: Mon, Feb 22, 2010 1:07 pm Subject: Re: Topology Dataset Discovery 1.6 ** Is it OK to manually mark assets as deleted in the topology dataset? Are you saying the source dataset is bmc.asset? If yes, should we delete these assets that are MarkedAsDeleted from bmc.asset? -----Original Message----- From: Roger Justice <[email protected]> To: [email protected] Sent: Mon, Feb 22, 2010 12:58 pm Subject: Re: Topology Dataset Discovery 1.6 If you were using the RE a purge Job would fix this problem since it would remove the assets from the source dataset that are marked as deleted in the BMC.Asset dataset. -----Original Message----- From: Kathy Morris <[email protected]> To: [email protected] Sent: Mon, Feb 22, 2010 12:20 pm Subject: Topology Dataset Discovery 1.6 ** Hi All, A co-worker is manually going into the topology dataset and marking assets as deleted.. During synchronization, we are getting errors that say "cannot set to as Markasdeleted to "NO" on the relationship instance because of the relationship endpoints are MarkAsDeleted. Why are we getting these errors? Are these manual updates causing this? Also we are not using the reconcilation engine. Scripts push the data from Topology to bmc.asset. ( I know this is ridiculous). _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _________________________________________________________________________ ______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org <http://www.arslist.org/> Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are" _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _________________________________________________________________________ ______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org <http://www.arslist.org/> Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are" _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org <http://www.arslist.org/> Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are" _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
