Dashboard > DHIS-2 > ... > DHIS 2.0 Releases > DHIS 2.0 M6
  DHIS-2 Log In | Sign Up   View a printable version of the current page.  
  DHIS 2.0 M6
Added by Torgeir Lorange Østby, last edited by margrsto on Jan 08, 2007  (view change)
Labels: 
(None)

DHIS 2.0 Milestone 6

Release date: December 13 2006.

The release is available on the Downloads page.

Database changes

  • Table organizationunit renamed to organisationunit
  • Table organizationunitgroup renamed to organisationunitgroup
  • Table organizationunitgroupset renamed to organisationunitgroupset
  • Table organizationunithierarchy renamed to organisationunithierarchy
  • Table organizationunitstructure renamed to organisationunitstructure
  • In table organisationunit, column organizationunitcode renamed to organisationunitcode
  • In table minmaxdataelement, column organizationunit renamed to organisationunit
  • In table users, column organizationunit renamed to organisationunit
  • Table degmembers renamed to dataelementgroupmembers
  • In table dataelementgroupmembers, column id renamed to groupid
  • In table dataelementgroupmembers, column elt renamed to dataelementid
  • Table igmembers renamed to indicatorgroupmembers
  • In table indicatorgroupmembers, column id renamed to groupid
  • In table indicatorgroupmembers, column elt renamed to indicatorid
  • Table ougmembers renamed to organisationunitgroupmembers
  • In table organisationunitgroupmembers, column id renamed to groupid
  • In table organisationunitgroupmembers, column elt renamed to organisationunitid
  • Table organizationunitgroups renamed to groupsetmembers
  • In table groupsetmembers, column id renamed to groupsetid
  • In table groupsetmembers, column elt renamed to organisationunitgroupid
  • Datasets have changed quite a bit. Instead of a hierarchy of datasets, only the root datasets are left in the database (those without a parent). All the associations from the old hierarchy to the organisation units are replaced by a new dataregisteringassociation table (columns: source varchar(255) NOT NULL [PK], dataSet int NOT NULL [PK, FK to dataset (id)]), which maps organisation units to the root datasets. Finally, the parent and source columns in the dataset table are removed as they are no longer in use.

You can either do this manually or you can try using the database fixer tool.

Using the dhis-database-fixer tool

Read and follow the steps in this section before ever running DHIS 2.0 M6 on a production database! If you've already run DHIS 2.0 M6, read and follow the steps anyway, but you will have to do quite a bit of manuall work.
This upgrade note applies to upgrades from DHIS 2.0 M5 and DHIS 2.0 M6 SNAPSHOT to DHIS 2.0 M6.

Follow these steps

  1. Build and run the dhis-database-fixer tool located in scm/tools/:
    /scm/tools/dhis-database-fixer $ mvn jetty:run-war
  2. Then point your browser to http://localhost:8080/
  3. On the first page, select and setup your source of configuration for Hibernate. If you have selected the correct settings, the "Continue" button should take you to a new page with a green "Connected!" message at the top.
  4. You now want to execute M5 to M6: Dataset fix and M5 to M6: Table and column renames fix. They can be executed in any order, and they can be re-executed any time. After executing the first, click the "Back" button to come back to the list of fixes for selecting and executing the other one. See information below for interpreting log messages.
  5. When done, press Ctrl-C in the terminal to stop the dhis-database-fixer. You're now ready to run DHIS 2.0 M6.

Log message colors

  • Blue messages are info messages
  • Green messages are success messages
  • Orange messages are warning messages
  • Red messages are error messages

If you get warnings...

Read the warnings!

  • If you are upgrading from DHIS 2.0 M5 or an early version of DHIS 2.0 M6 SNAPSHOT you will get two warnings saying that the organizationunitstructure table doesn't exist, and that the organizationunit column in the users table doesn't exist. This is perfectly fine.
  • If you get warnings saying that both table/column A and table/column B exist, you have to do some work manually. One of these tables/columns should contain the data and one of them should be empty. Drop the empty table/column and re-execute the fix. If both contain data, you need to figure out which one contains the correct data.
  • If in doubt, pop a mail to the dev list with sufficient information.

Site powered by a free Open Source Project / Non-profit License (more) of Confluence - the Enterprise wiki.
Learn more or evaluate Confluence for your organisation.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.6 Build:#812 Aug 06, 2007) - Bug/feature request - Contact Administrators