NoPublic, bureaucrat, administrator
6,632
edits
Changes
no edit summary
{{Warning | All IMSMA databases are different and '''all''' of the steps below are '''mandatory''' and should be done in the mentioned order.}}
===Data Quality SQL queries(mandatory)===__NOEDITSECTION__
__FORCETOC__
{{TOC right}}
There are several SQL queries that should be run before starting the upgrade process, see [[Data quality checks before upgrading to V6.0]].
===Run V5.08.04 tools - Locale fix(mandatory)===__NOEDITSECTION__
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 recalculation the area/length and upgrading to V6.0.
{{Note | MGRS will be listed in the output even if they are written with correct format since the Locale tool cannot correct them. If your country has been using MGRS you need to make sure that they are written in the [[MGRS coordinates| correct format]] before running the Recalc area/length tool.}}
===Run V5.08.04 tools - Recalculation of area/length(mandatory)===__NOEDITSECTION__
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 recalculated before upgrade to V6.0.
It is recommended to save the very latest version of all remain published templates been used for data entry as files. Save them for future use in case the country report problems with them after the upgrade.
===Take full backup(mandatory)===__NOEDITSECTION__Take a full backup and make sure that the country has a separate file complete backup of the attachments (especially for countries that has GBs of attachments). Otherwise all attachments might be '''lost''' when they uninstall 5.08.04 and install 6.0!!!.
===Extract MySQL(mandatory)===__NOEDITSECTION__
{{Note | I recommended to add ''pause'' to the run.bat so it will not automatically close because it is helpful to be able to see any error messages. The run.bat require that JAVA_HOME variable is set. If not:
* set the variable to "C:\IMSMAng\jre1.6.0_01" '''''OR'''''
# Views.sql.
The MySQLtoPGSQL tool does not have any installation program. Just copy the folder to somewhere on the C-drive. <br/> <br/>
[[Image:MySQLtoPGSQL1.png|400px]]
[[Image:MySQLtoPGSQL2.png|600px]]
[[Image:MySQLtoPGSQL3.png|400px]]
[[Image:Raw folder.png|650px]]
''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(mandatory)===__NOEDITSECTION__
[[Image:Restore.png|500px]]
{{Warning| Do '''NOT''' restore all files from the full 5.08.04 backup:
# Translations - you will '''overwrite''' the 6.0 translations with 5.08.04 translations.}}
<ol start="1">
<li> Did the previous database that you worked with on the V6.0 computer have any attachments? If yes, delete them before restoring this database;
<li> Restore the raw PostgreSQL dump on a computer with IMSMA V6.0;
::*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 that '''mandatory''' reference (FKs) between tables did not get created because of missing values in e.g. imsmaenum table. {{IMSMANG}} depends on that FKs are created.;
</ol>
====Check to be done BEFORE next step (mandatory)====__NOEDITSECTION__
There are a few checks and possibly manual export to be done '''BEFORE''' next step.
<ol>
<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> The upgrade script will change ''Location point'' to ''Reference point'', run this '''[[Location point | query]]''' '''before''' and '''after''' the upgrade.If there are any ''Location points'' you need to inform the country that the type has changed to ''Reference points''.</li>
<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><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 themwhen you are sending them the 6.0 backup.</li></ol>
===Upgrade the database(mandatory)===__NOEDITSECTION__
Start the TrayLauncher for starting the upgrade functionality.<br/> <br/>
[[Image:Upgrade_func.png|400px]]<br/><br/>
{{Note | A database that is already upgrade to V6.0 with one of the early Betas might need manual manipulation e.g. Beta 2 to Beta 3.}}
===Rebuild sandbox(mandatory)===__NOEDITSECTION__
If you have completed the previous steps, and no errors remain, you may proceed with rebuilding the sandbox. Both the IMSMA database and GIS database have been modified to support e.g. the Assistance object. As a result, the GIS database (sandbox) must be completely rebuilt in IMSMA V6.0 format.
{{Note | If you are connected to a network/wireless network that is not stable, disable it while rebuilding the sandbox.}}
This error message indicates that geographical data is missing in the database e.g. the record in table ''geopoint'' is deleted.
===Templates - Run the image tool(mandatory)===__NOEDITSECTION__
{{Note | Only the ''2014052701-IMAGE_UPDATE'' version of this tool works.}}
{| class="wikitable"
{{Note| Other errors in templates are '''NOT''' fixed by this tool or by upgrading. If you do not address the image issue the templates will not be possible to use for data entry or to edit in V6.0. It will be possible to publish them once.}}
===Open Data Inventory Manager and the Workbench(mandatory)===__NOEDITSECTION__
# Open the console log
# Open DIM
# Check for any error messages in the log?
===Templates - Checking the templates by publishing them in V6.0(mandatory)===__NOEDITSECTION__
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:
* other problems are found [[Upgrade Category Error]].
===Templates - Checking the templates by opening them for data entry and saving(mandatory)===__NOEDITSECTION__
After you have published the templates then
# open them
means that there could be a field in the template that has been deleted either by the administrator since template was published the last time or by the upgrade scripts e.g. Unknown device in Accident.<br/><br/>
===Reimport map(could be done by the country)===__NOEDITSECTION__The base imsma.mxd file has been updated to support e.g. the Assistance object and relabelling of objects. The background map must, be reimported and it is recommended to upgrade the background map's mxd-file to version 10.1.
{{Warning | Before reimporting the map, make sure that the C:\IMSMAng\server\gis\maps\imsma.mxd is the 10.1 version. It should be approx. 5MB, if it is 15MB then you have replaced it with the 9.3.1 version by restoring Map data. Verify also that the background map is a ''clean'' map or otherwise you will get duplicate layers in the merged mxd.}}
Verify that the fonts are OK too.
===Take backup(mandatory)===__NOEDITSECTION__
[[Image:Backup.png|500px]]
# the 6.0
===Check with the countries(mandatory)===__NOEDITSECTION__
* Import scripts
: All scripts needs to be reviewed and adapted to PostgreSQL/V6.0, see [[Script changes 6.0]];
: Prj files that are not standard ESRI needs to be copied to C:\IMSMAng\server\gis\coordinate systems.
* Server and client settings/configuration incl. replication
: If they had configured any settings you need to apply them again.
: Create a favourite link to the on-line wiki in the Internet browser.
===Implement V6.0 in the country(mandatory)===__NOEDITSECTION__
* Send them the V6.0 backup
* Installation package
* Apply/change/implement what is needed from the above checklistcheck list
{{NavBox Upgrade}}
[[Category:NoPublic]]
