Re: ARERR 120039 - operation violates the cardinality constraint...
Gerard: ARERR 120039 refers to wrong defined cardinality for a relationship instance in CMDB where its relationship definition for cardinality is different. Example: If you have defined some relationship class named A as 1-1 cardinality, and you've created two CI's and related them using A relationship class, you can't add a second child (using A relationship) to the parent because you're violating cardinality constaint. This error also appears as known defects when integrating CMDB with BMC Portal and BMC Configuration Automation. Please check KA301320, SW00255311 and SW0035971 in KB for more details. HTH, Alejandro De: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] En nombre de Gerard Lafontant Enviado el: Miércoles, 05 de Octubre de 2011 17:49 Para: arslist@ARSLIST.ORG Asunto: ARERR 120039 - operation violates the cardinality constraint... ** Anyone has seen this error before? and what's a possible fix on this issue? thank you all in advance. The operation violates the cardinality constraint of the relationship. : 1-Many cardinality will be violated. Cannot create relationship instance because right endpoint is already in another relationship. Relationship Instance Id: AG0017A4107626DcrtSwLqqo-wmBkY _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
Re: ARERR 120039 - operation violates the cardinality constraint...
thanks Alejandro that was my suspicion... I will look into the listed KB for a solution On Fri, Oct 7, 2011 at 10:00 AM, Alejandro Canon aca...@extensionsa.comwrote: ** Gerard: ** ** ARERR 120039 refers to wrong defined cardinality for a relationship instance in CMDB where its relationship definition for cardinality is different. Example: If you have defined some relationship class named “A” as “1-1” cardinality, and you’ve created two CI’s and related them using “A” relationship class, you can’t add a second child (using “A” relationship) to the parent because you’re violating cardinality constaint. This error also appears as known defects when integrating CMDB with BMC Portal and BMC Configuration Automation. Please check KA301320, SW00255311 and SW0035971 in KB for more details.*** * ** ** HTH, ** ** Alejandro ** ** ** ** *De:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *En nombre de *Gerard Lafontant *Enviado el:* Miércoles, 05 de Octubre de 2011 17:49 *Para:* arslist@ARSLIST.ORG *Asunto:* ARERR 120039 - operation violates the cardinality constraint...* *** ** ** ** Anyone has seen this error before? and what's a possible fix on this issue? thank you all in advance. ** ** ** ** The operation violates the cardinality constraint of the relationship. : 1-Many cardinality will be violated. Cannot create relationship instance because right endpoint is already in another relationship. Relationship Instance Id: AG0017A4107626DcrtSwLqqo-wmBkY _attend WWRUG11 www.wwrug.com ARSlist: Where the Answers Are_ _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
ARERR 120039 - operation violates the cardinality constraint...
Anyone has seen this error before? and what's a possible fix on this issue? thank you all in advance. The operation violates the cardinality constraint of the relationship. : 1-Many cardinality will be violated. Cannot create relationship instance because right endpoint is already in another relationship. Relationship Instance Id: AG0017A4107626DcrtSwLqqo-wmBkY ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: Where the Answers Are
