dhis2-devs team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

Whew. We have cleaned up the DHIS 1.4 database a lot to remove some of
the issues we were having with incorrect indicator formulas, and
problems with the organization hierarchy. I have removed all values
over 2^31 per your email as well as making some deletions from the
DataElementCalculated table. Finally, it worked (See stack trace
below).

Thanks for all your help.

Regards,
Jason



* INFO  12:24:23,359 Imported DataElements
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:24:31,937 Imported CalculatedDataElements
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:24:32,234 Imported IndicatorTypes
(DefaultDhis14FileImportService.java [Thread-18])
* WARN  12:24:34,484 Key is null (LoggingHashMap.java [Thread-18])
* WARN  12:24:34,500 Key is null (LoggingHashMap.java [Thread-18])
* WARN  12:24:34,781 Key is null (LoggingHashMap.java [Thread-18])
* WARN  12:24:35,562 Key is null (LoggingHashMap.java [Thread-18])
* WARN  12:24:35,578 Key is null (LoggingHashMap.java [Thread-18])
* WARN  12:24:36,125 Key is null (LoggingHashMap.java [Thread-18])
* WARN  12:24:36,703 Key is null (LoggingHashMap.java [Thread-18])
* INFO  12:24:36,937 Imported Indicators
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:24:37,421 Imported DataElementGroups
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:24:41,156 Imported DataElementGroup members
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:24:41,546 Imported IndicatorGroups
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:24:42,578 Imported IndicatorGroup members
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:24:43,640 Imported DataSets
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:24:48,593 Imported DataSet members
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:24:59,015 Imported OrganisationUnits
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:24:59,359 Imported OrganisationUnitGroups
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:25:04,031 Imported OrganisationUnitGroup members
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:25:04,250 Imported OrganisationUnitGroupSets
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:25:04,625 Imported OrganisationUnitGroupSet members
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:25:14,156 Imported OrganisationUnitRelationships
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:25:16,015 Imported OrganisationUnitHierarchy
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:25:25,203 Imported DataSet OrganisationUnit Associations
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  12:25:43,484 Imported Periods
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  13:24:14,562 Imported RoutineDataValues
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  13:24:30,953 Imported OnChangePeriods
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  13:25:06,921 Imported SemiPermanentDataValues
(DefaultDhis14FileImportService.java [Thread-18])
* INFO  13:25:07,000 Import process completed: 1:01:08.109
(ImportInternalProcess.java [Thread-18])


2009/4/1 Lars Helge Øverland <larshelge@xxxxxxxxx>:
>
>>
>> We will need to change this in DHIS 1.4 somehow. Would it be possible
>> for DHIS to implement a check to ensure that the value is not out of
>> the allowable range? If it is, then perhaps it could simply ignore
>> these values, and inform the user.
>
> That would have been very nice but this happens when the JDBC driver
> accesses the database and doesn't give the DHIS 2 application a chance to do
> something about it.
>
>>
>>
>> > - For inital imports (!), in the DHIS 2 import screen - "Show advanced
>> > options" - set "Skip check for matching datavalues" to "yes (empty
>> > database)"
>> >
>>
>> Could you explain this option?  I would assume that it will check for
>> existing data values and not overwrite them. If I choose no, I will
>> assume it will attempt to insert everything?
>
> Exactly. "No" is the default and will do a check for matching data values
> for every row, which is redundant on empty databases.
>
>>
>> >
>> > o I am not sure why you didn't get it to work. This sounds a little
>> > silly
>> > but are you sure you waited long enough? My import on a high-end maching
>> > took 32 min. Is the GUI message saying "Import process complete", or is
>> > it
>> > still saying "Importing routine data values" ?  This is the end of my
>> > log.
>> > Yours stops at "Imported Periods"
>>
>> Yes, I waited. Well, in fact ,I did not have to wait. It just executed
>> like lightning and gave  me a "null" response in the browser window. I
>> did not get anything like "Import process complete".
>
> Strange, normally something would have emerged in the logs.
>
>>
>> >
>> > http://folk.uio.no/larshelg/files/dhis2zambiaMarch2009.backup
>>
>> Big help Lars. This will at least enable me to start having a look at
>> the development of the reports (which they need ASAP) and then we can
>> continue to clean up the other issues.
>>
>> Tack,
>> Jason
>
>
> Det e lugnt..
>
>