Upgrade from 5.08.04 to 6.0 process

Data Quality SQL queries

There are several SQL queries that should be run before starting the upgrade process, see xxx link.

Run V5.08.04 tools - Locale fix

This tool was created for the upgrade to 5.08.04 and addresses old issues. Many countries did not run it and import scripts may have created new records with issues. This tool has to be run before re-calculation the area/length and upgrading to V6.0.

The user-entered format of the coordinates is stored in the database in this format: X | Y | language | country | e.g. 474522|4615907|en|GB| in the column userenteredcoord in the table geopoint.

The locale portion (|en|GB|) of userenteredcoord was added in V5.06.00 but the existing geopoints were not given locale information by the database upgrade functionality. If the locale information was missing, it was added later when field reports were e.g. imported. However, then it was the regional settings of the user doing the import that was used. This created invalid combinations when the data entry was done with other regional settings.

The Locale fix tool will verify that there are no invalid combinations of decimal symbol and locale information in the database. If invalid combinations are stored the tool will try to fix them but there may be combinations that will require SQL updating.

Start the tool by clicking on C:\IMSMAng\ext\LocaleUpdater\run.bat.

Note that you might need to run the tool with two different regional settings i.e. first with dot as decimal symbol and then with comma as decimal symbol.

Run V5.08.04 tools - Re-calculation of area/length

The calculations of calculated area (m2) and calculated length (m) have been updated in V5.08.04. Due to that in previous version different formulas were used and anti-clock wise entered polygons resulted in negative square meters the calculated area/length needs to be re-calculated before upgrade to V6.0.

Start the tool by clicking on C:\IMSMAng\ext\CalcAreaMigration\run.bat.

Save the published templates as files

The templates might be created with old version of IMSMA and may contain errors that have been undetected in 5.08.04 but will not be working with V6.0. I recommend to save the very latest version of all templates ever been used for data entry as files. how to

Take full backup

Take a full backup and make sure that the country has a separate file backup of the attachments (especially for countries that has GBs of attachments).

Extract MySQL

Use the MySQLtoPGSQL tool which will generate two files:

• Dump.sql and
• Views.sql.

Rename the MySQL dump.sql to e.g. MySQLdump and copy the raw PostGreSQL dump.sql and view.sql to your backup folder.

Restore the raw dump and upgrade

Do not restore GIS database and map data. You need to rebuild the sandbox and by restoring the map date you will copy the ArcGIS 9.3.1-version of imsma.mxd to C:\IMSMAng\server\gis\maps.

Did the backup from the country contain the attachments?

Restore the PostGresSQL dump on a computer with IMSMA V6.0 and scan the log for error messages.

Start the TrayLauncher for starting the upgrade scripts. When the upgrade scripts are done:

1. stop TrayLauncher;
2. start TraYLauncher;
3. take backup.

Note that a database that is already upgrade to V6.0 with one of the earlier RC/Beta might need manual manipulation e.g. Beta 2 to Beta 3.

Templates - Run the image tool

Note that this tool (1 February 2014) still does not work. The work-around is to delete the images, logotypes in either 5.08.04 or 6.0. In 5.08.04 they are easier to see than in V6.0. picture

The tool should be run twice:

• Published templates that are in database;
• Files that are in C:\IMSMAng\client\FormTemplates\MyTemplates.

Note that other errors in templates are not fixed by this tool or by upgrading.

Templates - Checking the templates by publishing them in V6.0

After you have either run the tool or removed the images manually you should test that all published templates are still working by publish them in V6.0. Check the log when you drag them into the designer. This error message in the log means that there is still an image in wrong format in the template: Need to update FFML image to Image object

Other possible issues are:

• the same field more than once in the template;
• value list of multi-select is changed.