The current SiblingColumnStorageStrategy uses any MibObj defined as string which shares the same resource type, instead of define a SNMP OID and request an additional operation though the network.
This change requires a new parameter called sibling-column-name which deprecates the old sibling-column-oid. The problems come when someone wants to upgrade OpenNMS from 1.8 to 1.10 and wants to use the same datacollection-config.xml.
Currently a RuntimeException will be thrown, and the JRBs won't be updated.
A better approach is to only skip the resources with the misconfigured SiblingColumnStorageStrategy but let the others properly get updated, and of course, improve the error message related to this misconfiguration and provide instructions about how to deal with it.