Changes

Upgrade from 5.08.04 to 6.0 process

238 bytes removed, 17:48, 7 October 2014
no edit summary
''Raw'' as in it is PostGreSQL format but the table structure, etc. are still 5.08.04 and needs to be upgraded to V6.0.
===Restore the raw dump and correct Foreign Key constraints===__NOEDITSECTION__
[[Image:Restore.png|500px]]
{{Warning| Do '''NOT''' restore all files from the full 5.08.04 backup:
# GIS database - you need to rebuild the sandbox after the upgradeanyhow
# Map data - you will '''overwrite''' the ArcGIS 10.1-version of ''imsma.mxd'' in C:\IMSMAng\server\gis\maps with the ArcGIS 9.3.1-version
# Form templates - these are work-in-progress ffml files outside the database. If you do restore, make sure that you do not mix countries
#:* error message ''COPY fieldreportdesc'' means that it was not possible to load the table so the table is '''empty''';
#:* error message ''ERROR: insert or update on table "fieldreport" violates foreign key constraint "fieldreport_fieldreportdesc_guid_fkey'' means mandatory reference between tables did not work because of missing values in e.g. imsmaenum table;
# Apply the ''fix imsmaenum Foreign Key constraints'' [[Imsmaenum FK fix | script]] ('''first''' time);
# The upgrade scripts might create duplicate enumvalues and therefore the current values must be documented [[Imsmaenum Duplicate fix | query]]
#: Duplicate enumvalues cause import issues i.e. empty fields, which are difficult to detect due to there are no error messages);
[[Image:Upgrade_func.png|400px]]<br/><br/>
If you are upgrading from MySQL there is 110 upgrade scripts to be applied. When the upgrade process is finished:
# Apply the ''fix imsmaenum Foreign Key constraints'' [[Imsmaenum FK fix | script]] ('''second''' time);
# Check if the upgrade scripts created duplicate enumvalues [[Imsmaenum Duplicate fix Part 2| query]] and if necessary fix them ('''mandatory''');
# Due to mistyping there is one mistake in enumvalue and translation for ''Wind Speed'' [[Translation fix | more details]];
6,632
edits