KNOWN ISSUE: Resource Associations may be appended rather than replaced when using Connector Solution
|Article:TECH39684|||||Created: 2008-03-27|||||Updated: 2008-04-18|||||Article URL http://www.symantec.com/docs/TECH39684|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
When importing Resource Associations using Connector Solution, the associations in the data source may be appended to the existing associations rather than replacing the existing resource associations with the set from the data source. For example, a computer, Computer1, is associated to a monitor, Monitor1, through the Associated Assets association type. You then create a data source pointing to a record set with the following rows:
Next you create an import rule based on the above data source for the computer resource type and map the Associated Assets association type to the AssociatedAssetName column from the data source.
Executing the above import rule will leave Computer1 associated to both Monitor1 and Monitor2, which is incorrect. The correct result is to have Computer1 associated to Monitor2.
Connector Solution 6.5
CMDB Solution 6.5
This is caused by a flaw in the way Resource Associations are loaded by the spResourceAssociationsLoadData_Complete procedure.
Note: You must re-apply this workaround if you repair Connector Solution 6.5
Use the following steps to prevent this issue from occurring:
- Back up the Altiris database.
- Download the spResourceAssociationsLoadData_Complete.txt file from the right-hand pane of this article.
- Execute the code from the downloaded spResourceAssociationsLoadData_Complete.txt file against the Altiris database.
- Re-run the Connector import rules for the affected resources.
|Description||Logged in sydd2 (Altiris - Sydney) database|
Article URL http://www.symantec.com/docs/TECH39684