Hi All, If you add a Company value to a CI with one weak child then the CMDB filters push the Company group id to the read security field of the relationship. The weak child is not touched.
If, however, the CI has two or more weak children then, when the relationships are updated, the CMDB filters on the relationships update the weak children with something. Has anyone investigated why the children are being updated? The Company is not sent to the weak children and there is no reason to re-send the propagated attributes. Anyway, why only update the child CIs if there is more than one? The problem we face is that a computer CI can have ~200 weak children (sourced from BMC Config Discovery) and, with four datasets (import, staging, production and baseline), ~800 weak children are updated (the child update uses the recon id) and this is causing timeouts. BMC's workaround is to change the weak relationships to normal relationships. This workflow is present in CMDB 2.1 and 7.5. Cheers Peter _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
