The data integrity checks showed some “orphaned” org units which should not have been on the system.
So I wrote scripts to clean out the org units and checked all 37 tables that either reference organisationunitid or sourceid and cleaned out all those tables. I also checked the “reporttable_organisationunits” table and it was not necessary to renumber as the org units were never in that table (I checked before doing any deletes and by the way thanks Jason Pickering for the script you shared with Ferdie).
After that I cleared analytics, re-generated resource tables, cleared cache and cache statistics and re-ran integrity checks…those org unit uids are still appearing as “orphaned organisation units”.
From which table(s) is the integrity check picking these org units up from?
Thanks
Ant Snyman
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
after doing SQL against a running DHIS 2 instance you might want to go to data admin > cache statistics > clear cache. This since the cache might become stale unknowingly as a result of direct SQL queries.
regards,
Lars
···
On Sat, Aug 15, 2015 at 12:05 PM, Ant Snyman ant@hisp.org wrote:
Dear All,
DHIS2 vesrion 2.20 snapshot, build 19527
The data integrity checks showed some “orphaned” org units which should not have been on the system.
So I wrote scripts to clean out the org units and checked all 37 tables that either reference organisationunitid or sourceid and cleaned out all those tables. I also checked the “reporttable_organisationunits” table and it was not necessary to renumber as the org units were never in that table (I checked before doing any deletes and by the way thanks Jason Pickering for the script you shared with Ferdie).
After that I cleared analytics, re-generated resource tables, cleared cache and cache statistics and re-ran integrity checks…those org unit uids are still appearing as “orphaned organisation units”.
From which table(s) is the integrity check picking these org units up from?
Thanks
Ant Snyman
Cell: 0824910449
Landline: 028 2713242
Health Information Systems Program - SA
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
Yes I did clear cache statistics as well as browser cache. How does the application determine orphaned organisationunits? Organisationunits without a parentid? Or a parentid that does not exist?
Regards
Ant
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
after doing SQL against a running DHIS 2 instance you might want to go to data admin > cache statistics > clear cache. This since the cache might become stale unknowingly as a result of direct SQL queries.
regards,
Lars
–
On Sat, Aug 15, 2015 at 12:05 PM, Ant Snyman ant@hisp.org wrote:
Dear All,
DHIS2 vesrion 2.20 snapshot, build 19527
The data integrity checks showed some “orphaned” org units which should not have been on the system.
So I wrote scripts to clean out the org units and checked all 37 tables that either reference organisationunitid or sourceid and cleaned out all those tables. I also checked the “reporttable_organisationunits” table and it was not necessary to renumber as the org units were never in that table (I checked before doing any deletes and by the way thanks Jason Pickering for the script you shared with Ferdie).
After that I cleared analytics, re-generated resource tables, cleared cache and cache statistics and re-ran integrity checks…those org unit uids are still appearing as “orphaned organisation units”.
From which table(s) is the integrity check picking these org units up from?
Thanks
Ant Snyman
Cell: 0824910449
Landline: 028 2713242
Health Information Systems Program - SA
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
Lars…I have finally solved the puzzle…I suspect that the person importing these org units misaligned the formatting because the uids were actually loaded in the org unit name column and what I thought were the uids were actually the “org unit names”. I should have picked that up straight away because the “orphaned organisationunits” integrity check always reports the name of the offending org unit, and never the uids.
But thanks for responding…
Regards
Ant
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
···
On 16 August 2015 at 08:41, Ant Snyman ant@hisp.org wrote:
Thanks Lars or your response.
Yes I did clear cache statistics as well as browser cache. How does the application determine orphaned organisationunits? Organisationunits without a parentid? Or a parentid that does not exist?
after doing SQL against a running DHIS 2 instance you might want to go to data admin > cache statistics > clear cache. This since the cache might become stale unknowingly as a result of direct SQL queries.
regards,
Lars
Ant Snyman
Cell: 0824910449
Landline: 028 2713242
Health Information Systems Program - SA
–
On Sat, Aug 15, 2015 at 12:05 PM, Ant Snyman ant@hisp.org wrote:
Dear All,
DHIS2 vesrion 2.20 snapshot, build 19527
The data integrity checks showed some “orphaned” org units which should not have been on the system.
So I wrote scripts to clean out the org units and checked all 37 tables that either reference organisationunitid or sourceid and cleaned out all those tables. I also checked the “reporttable_organisationunits” table and it was not necessary to renumber as the org units were never in that table (I checked before doing any deletes and by the way thanks Jason Pickering for the script you shared with Ferdie).
After that I cleared analytics, re-generated resource tables, cleared cache and cache statistics and re-ran integrity checks…those org unit uids are still appearing as “orphaned organisation units”.
From which table(s) is the integrity check picking these org units up from?
Thanks
Ant Snyman
Cell: 0824910449
Landline: 028 2713242
Health Information Systems Program - SA
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
Thank you for your response. I have sorted out the problem and it was neither cache nor browser related.
Regards
Ant Snyman
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
···
On 16 August 2015 at 09:15, Aanyo Melo AHIAGNO aanyo7@hotmail.fr wrote:
Hello
Can you try, to do the something on the another browser ???
Yes I did clear cache statistics as well as browser cache. How does the application determine orphaned organisationunits? Organisationunits without a parentid? Or a parentid that does not exist?
after doing SQL against a running DHIS 2 instance you might want to go to data admin > cache statistics > clear cache. This since the cache might become stale unknowingly as a result of direct SQL queries.
regards,
Lars
On Sat, Aug 15, 2015 at 12:05 PM, Ant Snyman ant@hisp.org wrote:
Dear All,
DHIS2 vesrion 2.20 snapshot, build 19527
The data integrity checks showed some “orphaned” org units which should not have been on the system.
So I wrote scripts to clean out the org units and checked all 37 tables that either reference organisationunitid or sourceid and cleaned out all those tables. I also checked the “reporttable_organisationunits” table and it was not necessary to renumber as the org units were never in that table (I checked before doing any deletes and by the way thanks Jason Pickering for the script you shared with Ferdie).
After that I cleared analytics, re-generated resource tables, cleared cache and cache statistics and re-ran integrity checks…those org unit uids are still appearing as “orphaned organisation units”.
From which table(s) is the integrity check picking these org units up from?
Thanks
Ant Snyman
Cell: 0824910449
Landline: 028 2713242
Health Information Systems Program - SA
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
I am looking for a DHIS 2 Developer available from March and willing to work on the development of some forms and reports from a distance. I would also like to communicate with anyone who is using DHIS 2 for the collection of information for the generation of PEPFAR (United States President’s Emergency Plan for AIDS Relief) HIV indicators.
Regards,
Angela Hinds
Senior Technical Officer
Health Information, Communicable Diseases and Emergency Response
I am looking for a DHIS 2 Developer available from March and willing to work on the development of some forms and reports from a distance. I would also like to communicate with anyone who is using DHIS 2 for the collection of information for the generation of PEPFAR (United States President’s Emergency Plan for AIDS Relief) HIV indicators.
Regards,
Angela Hinds
Senior Technical Officer
Health Information, Communicable Diseases and Emergency Response
On Wed, Feb 24, 2016 at 12:30 PM, Hinds, Ms. Angela (CAR) hindsang@carpha.org wrote:
Dear Colleagues,
I am looking for a DHIS 2 Developer available from March and willing to work on the development of some forms and reports from a distance. I would also like to communicate with anyone who is using DHIS 2 for the collection of information for the generation of PEPFAR (United States President’s Emergency Plan for AIDS Relief) HIV indicators.
Regards,
Angela Hinds
Senior Technical Officer
Health Information, Communicable Diseases and Emergency Response
Mr.Samuel K. Cheburet (Bsc. HRIM,Dip. HRIT)
Division of Monitoring and Evaluation,Health Research development and Informatic’s
CRVS Unit
Afya House, Room LG 37
PO. Box 30016, 00100.
Ministry of Health Headquarters, Nairobi, Kenya.
mobile + 254-721624338
Email: samuelcheburet@gmail.com
Skype: samuelcheburet
*"HealthInformation Management - Making a World of Difference”