Hi there, I had seen these integrity check messages from 1.4 actually, but did not fix them. I see now that I need to do this. I just wanted to ensure that a complete "clean" import from 1.4 to 2.0 was actually possible, and it seems that it is.
> 2) There are a few "EntryNumber" entries in the "RoutineData" table that > exceed what the JDBC driver is able to read. Open the "RoutineData" table, > sort big->small on "EntryNumber" and remove the 3 highest numbers. What is the maximum then? I would assume that we would need to do something to prevent this from happening in the first place. We have a new version of the DHIS 1.4 Zambia database, that includes some more historical data (as of last Friday), but I am not sure if that is the version that you are using. This is part of the problem here, but that deserves another thread. Thanks again, and I will revert to the list again if I encounter more issues. Best regards, jason 2009/3/18 Lars Helge Øverland <[email protected]>: > >> >> >> I would assume this would be caused by the fact I am using a >> completely new database. >> >> So essentially, I would like to perform a completely clean >> installation from 1.4 to 2.0. We will need to do this on a regular >> basis, as 2.0 (at least for the time being in Zambia) will only be >> used for reporting and analysis. No data will be entered or modified. >> Each quarter, a new import from the master 1.4 database will need to >> take place. >> >> Thanks in advance for your help. >> >> I will attempt the second procedure now,and see what happens . >> >> Best regards, >> Jason > > > I had a look in the DHIS 1.4 Zambia database and found a few > inconsistencies. > > 1) The table "DataElementCalculated" represents the formula for calculated > data elements, and there are a few entries that refer to data elements that > don't exist. These can be revealed by opening the table, sort the > DataElementCalculatedID column from A-Z and remove the entries with only > identifiers/numbers. Existing data elements will be mapped and appear as > names. Then do the same for the DataElementID column and remove entries > with numbers/identifiers. Ideally this should be included in the data > integrity checks in 1.4. > > > 2) There are a few "EntryNumber" entries in the "RoutineData" table that > exceed what the JDBC driver is able to read. Open the "RoutineData" table, > sort big->small on "EntryNumber" and remove the 3 highest numbers. > > > Then try importing again. Should take around 15 minutes. > > Lars > > > > _______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
