Joel, In the CMDB, a relationship is only meaningful if there are two endpoints. You have to be relating something to something or you don't have a relationship.
So, you should not have cases where the InstanceID of either of the endpoints is NULL. NOTE: The reconciliation ID of the endpoints may be NULL because you may not have assigned one yet, but the instance IDs should not be NULL. So, removing any item where it is a "relationship to nowhere" should be safe. On the NULL for SystemName, I would not be so quick to assume that this is not a valid item. This is an attribute and not having that set is just missing that one attribute. It does not mean it is an orphan record. There are many reasons why an individual attribute may be blank. I hope this helps, Doug Mueller From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Joel Sender Sent: Monday, November 12, 2012 5:00 PM To: [email protected] Subject: Orphaned CMDB records ** Deleting orphaned CMDB records (gigo) and want to confirm that if RelLeadClassId(400131300) and RelLeadInstanceId(400131200) are both equal to NULL in BMC.CORE Component forms (BMC_NETWORKPORT, BMC_OPERATINGSYSTEM, etc.) then the record is OK to remove. Also, within the same CORE forms, SystemName equal to NULL also indicates of an orphaned component, correct? Just want to make sure before actually (backing-up and) deleting. TIA, Joel Joel Sender [email protected] 310.829.5552 _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
