Document ID: TEC613670 Tech DocumentTitle: After upgrade to 2.3.3, reports no longer have data
Upgrading from 2.3.2 to 2.3.3, customers may see that data is no longer appearing in their reports. Customers may have tried to do a full resync or re-add the data source and it doesn't resolve the issue. We've seen errors in DM log files about RIBException for Failed to bind type reference. This is because the type is not in the RIB cache.
The /tmp/ribcache may have become corrupt and have a partial state of the RIB documents for the various data sources. Reason for corruption/partial documents is still being investigated. System will not re-get the RIB document because it thinks it has the latest version, even on service restart.
Rename the /tmp/ribcache directory and restart the caperfcenter_devicemanager service so the RIB cache is rebuilt. Service will take a few minutes to fully come up as it queries all the data source for RIB documents.