Can’t roll up
No matter what I do, I can’t get my data to roll up. Here is the log from my latest effort, using a dimension report. All the headers are correct, all the periods are correct, there are the right number of rows in the _report table, it’s just that all numbers are 0. When I look at aggregateddatavalue, only one of the two periods is there, only 2 of 11 organization units is there, all 44 categoryoptioncomboids are there.
Ola will probably be able help a bit more with this, but just a few
things to check.
Have all the resource tables been built? Maintenance->Resource tables
Regards,
Jason
···
On Thu, Jun 3, 2010 at 10:28 PM, Friedman, Roger (CDC/OID/NCHHSTP) (CTR) <rdf4@cdc.gov> wrote:
No matter what I do, I can't get my data to roll up. Here is the log from
my latest effort, using a dimension report. All the headers are correct,
all the periods are correct, there are the right number of rows in the
_report table, it's just that all numbers are 0. When I look at
aggregateddatavalue, only one of the two periods is there, only 2 of 11
organization units is there, all 44 categoryoptioncomboids are there.
Using the same database as Roger I managed to reproduce this problem and found that the clearing the hierarchy history as suggested by Lars, solved it.
The problem was aggregation up the hierarchy from the raw data at district level to region or national, as all aggregates for orgunits above the district level were 0 in the report table.
Apparently something has happened during the creation or later fixing of the orgunit hierarchy which has lead to a problem with the aggregation.
Clearing the hierarchy history made the system rebuild the hierarchy structure again and then it worked.
It is always good practice to clear the hierarchy history after finishing the initial customisation work as the history then is more a history of fixes and tweaking and not a real history of how the organisational structure has changed over time. This also speeds up the aggregation process as no history needs to be taken into account.
Of course later when in production and real changes to the hierarchy are necessary to reflect real world changes then one should not clear the history after making such changes…
Lars might fill in more technical details as to how this problem happened.
Thanks, Ola. I have cleared the hierarchy history through the menu.
Thanks, Lars. I got hung up in the failure of the resource tables operation and didn’t try clearing the history.
For my information, in what table is the hierarchy history? And what function does it perform in relation to the rollup? Is this an effort to automatically account for changes in the hierarchy when doing roll-ups? There have been frequent hierarchy changes in Ghana (almost all district splits), a problem which I have put on the shelf until I get basic functionality.
Subject: Re: [Dhis2-devs] [Dhis2-users] Can’t roll up
Hi,
Using the same database as Roger I managed to reproduce this problem and found that the clearing the hierarchy history as suggested by Lars, solved it.
The problem was aggregation up the hierarchy from the raw data at district level to region or national, as all aggregates for orgunits above the district level were 0 in the report table.
Apparently something has happened during the creation or later fixing of the orgunit hierarchy which has lead to a problem with the aggregation.
Clearing the hierarchy history made the system rebuild the hierarchy structure again and then it worked.
It is always good practice to clear the hierarchy history after finishing the initial customisation work as the history then is more a history of fixes and tweaking and not a real history of how the organisational structure has changed over time. This also speeds up the aggregation process as no history needs to be taken into account.
Of course later when in production and real changes to the hierarchy are necessary to reflect real world changes then one should not clear the history after making such changes…
Lars might fill in more technical details as to how this problem happened.
Thanks, Ola. I have cleared the hierarchy history through the menu.
Thanks, Lars. I got hung up in the failure of the resource tables operation and didn’t try clearing the history.
For my information, in what table is the hierarchy history? And what function does it perform in relation to the rollup? Is this an effort to automatically account for changes in the hierarchy when doing roll-ups?
Exactly.
This function is used to represent the organisation unit hierarchy in the aggregation process and, if empty/messy, will cause the hierarchy aggregation to be non-functional. Will make this more robust for the next version.
Lars
···
2010/6/7 Friedman, Roger (CDC/OID/NCHHSTP) (CTR) rdf4@cdc.gov
There have been frequent hierarchy changes in Ghana (almost all district splits), a problem which I have put on the shelf until I get basic functionality.
Subject: Re: [Dhis2-devs] [Dhis2-users] Can’t roll up
Hi,
Using the same database as Roger I managed to reproduce this problem and found that the clearing the hierarchy history as suggested by Lars, solved it.
The problem was aggregation up the hierarchy from the raw data at district level to region or national, as all aggregates for orgunits above the district level were 0 in the report table.
Apparently something has happened during the creation or later fixing of the orgunit hierarchy which has lead to a problem with the aggregation.
Clearing the hierarchy history made the system rebuild the hierarchy structure again and then it worked.
It is always good practice to clear the hierarchy history after finishing the initial customisation work as the history then is more a history of fixes and tweaking and not a real history of how the organisational structure has changed over time. This also speeds up the aggregation process as no history needs to be taken into account.
Of course later when in production and real changes to the hierarchy are necessary to reflect real world changes then one should not clear the history after making such changes…
Lars might fill in more technical details as to how this problem happened.