Why is the Chksum less than 100% for certain Infocube versions after loading a database?
Should it not be 100% for all versions? Why could it be smaller for some versions?
Thanks in advance,
small differences in the Checksum % are likely due to rounding.
The Checksum function performs a grand total of the version, then the percentages are calculated based on these totals (which are displayed in the colum to the left). The grand totals are rounded to the seventh digit (7 spaces from the left), hence the small differences in the percentages.
Small rounding differences present no database or reporting problems.
A possible solution could be to re-define the Infocube data type to double.
This requires an Extraction and reloading of the infocube data
Large differences in the Checksum % are likely due to:
- "orphaned" entity members in the relationship structure (To verify, use the Scan feature in the Relationships screen - read more about Troubleshoot: effect of missing relationships or How to repair and prevent missing relationships in hierarchies)
- manual deletion of some items of any dimension of the infocube.
A solution for this would be to fix the releationships and proceed with a version alignement
thanks i understand much better now.
I will browse the Resources for more information
I had the same issue on a cube with many versions. If I didn't normalize the entity relationships after changing entities, this could come up. I try to remember to run the normalize tool after making entity changes now.
Retrieving data ...