NoPublic, bureaucrat, administrator
6,632
edits
Changes
no edit summary
The dump file created with the tool is a '''raw''' dump file in PosGreSQL format which is possible to restore with V6.0.
''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.
<li> The upgrade scripts do not handle the subobjects that should be transformed into normal multi-selects well (2014-11-25/NAA).Run these '''[[Check Detection Sample Sector VegetationRemoval | queries]]''' in order to see if there are any records that have to be inserted manually '''(mandatory)'''. If there are rows you need to '''export''' them and '''manually''' add them in the correct tables with SQL after the upgrade.</li></ol>
===Restore the raw dump (mandatory)===__NOEDITSECTION__
[[Image:Restore.png|500px]]
<li> The upgrade scripts will '''wrongly''' change enumvalues to Inactive and therefore the current values must be documented ('''[[Imsmaenum Duplicate fix | query]]''')
: e.g. if the country has decided that enumvalue ''OutOfRange'' in enumcategory ''Priority'' should be ''inactive'', the upgrade script will set it to ''active''.</li>
<li> How many rows are there in the attachment table? If more than 0, then you have to verify that the attachments are included in the backup folder or '''instruct''' the country on how to handle them when you are sending them the 6.0 backup.</li>
</ol>
#: Duplicate enumvalues cause import issues i.e. empty fields, which are difficult to detect due to there are no error messages;
# Check if the upgrade scripts '''wrongly''' changed enumvalues to Inactive ('''mandatory''')('''[[Inactive enumvalue fix | query ]]''')(still happening with 18 Feb 2015);
# If needed '''add ''' Detection/Samle/Sector/Vegetation removal records to the correct tables;
# Stop TrayLauncher;
# Start TrayLauncher;
