this happens because you have some sort of duplicate record in your “period” database table, for a period near Nov 25, 2015. Have a look for that in the period table and remove any duplicates.
This is however a problem we have seen a few times now so we will put in a “safety check” in the system to warn about and then ignore this issue.
this happens because you have some sort of duplicate record in your “period” database table, for a period near Nov 25, 2015. Have a look for that in the period table and remove any duplicates.
This is however a problem we have seen a few times now so we will put in a “safety check” in the system to warn about and then ignore this issue.
okay I am not 100% sure what causes this. I have now included a uniqueness check on ISO dates in the generation of the period resource table. It should ignore duplicates and provide a log warning when duplicates are encountered.
Could you please try to upgrade to the latest 2.22 and see if that fixes your problem. Build ready in 15 minutes. Revision 21900.
this happens because you have some sort of duplicate record in your “period” database table, for a period near Nov 25, 2015. Have a look for that in the period table and remove any duplicates.
This is however a problem we have seen a few times now so we will put in a “safety check” in the system to warn about and then ignore this issue.
okay I am not 100% sure what causes this. I have now included a uniqueness check on ISO dates in the generation of the period resource table. It should ignore duplicates and provide a log warning when duplicates are encountered.
Could you please try to upgrade to the latest 2.22 and see if that fixes your problem. Build ready in 15 minutes. Revision 21900.
this happens because you have some sort of duplicate record in your “period” database table, for a period near Nov 25, 2015. Have a look for that in the period table and remove any duplicates.
This is however a problem we have seen a few times now so we will put in a “safety check” in the system to warn about and then ignore this issue.
okay I am not 100% sure what causes this. I have now included a uniqueness check on ISO dates in the generation of the period resource table. It should ignore duplicates and provide a log warning when duplicates are encountered.
Could you please try to upgrade to the latest 2.22 and see if that fixes your problem. Build ready in 15 minutes. Revision 21900.
this happens because you have some sort of duplicate record in your “period” database table, for a period near Nov 25, 2015. Have a look for that in the period table and remove any duplicates.
This is however a problem we have seen a few times now so we will put in a “safety check” in the system to warn about and then ignore this issue.
There is also an integrity check “Dupliate periods” which should also help you to identify this problem. Look in “Data Administration → Data integrity”. You will still need to resolve the problem directly in the database however.
Regards,
Jason
···
On Thu, Mar 10, 2016 at 10:57 AM, Lars Helge Øverland lars@dhis2.org wrote:
That sounds good, thanks for applying the fix.
Note that this fix is to some extent hiding the real problem, so have a look in the logs for warnings about duplicate periods going forward.
okay I am not 100% sure what causes this. I have now included a uniqueness check on ISO dates in the generation of the period resource table. It should ignore duplicates and provide a log warning when duplicates are encountered.
Could you please try to upgrade to the latest 2.22 and see if that fixes your problem. Build ready in 15 minutes. Revision 21900.
this happens because you have some sort of duplicate record in your “period” database table, for a period near Nov 25, 2015. Have a look for that in the period table and remove any duplicates.
This is however a problem we have seen a few times now so we will put in a “safety check” in the system to warn about and then ignore this issue.
There is also an integrity check “Dupliate periods” which should also help you to identify this problem. Look in “Data Administration → Data integrity”. You will still need to resolve the problem directly in the database however.
Regards,
Jason
On Thu, Mar 10, 2016 at 10:57 AM, Lars Helge Øverland lars@dhis2.org wrote:
That sounds good, thanks for applying the fix.
Note that this fix is to some extent hiding the real problem, so have a look in the logs for warnings about duplicate periods going forward.
okay I am not 100% sure what causes this. I have now included a uniqueness check on ISO dates in the generation of the period resource table. It should ignore duplicates and provide a log warning when duplicates are encountered.
Could you please try to upgrade to the latest 2.22 and see if that fixes your problem. Build ready in 15 minutes. Revision 21900.
this happens because you have some sort of duplicate record in your “period” database table, for a period near Nov 25, 2015. Have a look for that in the period table and remove any duplicates.
This is however a problem we have seen a few times now so we will put in a “safety check” in the system to warn about and then ignore this issue.