Changes

Upgrade from 5.08.04 to 6.0 process

28 bytes added, 22:32, 9 April 2015

no edit summary

<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 them when you are sending them the 6.0 backup.</li>

</ol>

[[Image:Upgrade_func.png|400px]]<br/><br/>

If you are upgrading from MySQL there are 118 upgrade scripts to be applied (18 February 2015 build). The added upgrade scripts in 24 October 2014 build takes several hours to run and the ''update-reconciliation-locations-column'' has cause problems:

~~::a~~ <ol type="A"><li>upgrade script finished without error message but when reading the log there were database changes not done (Laos which already were on 6.0)</li>~~::b upgrade~~ <li> pgrade script starting to fill the log with error messages so I aborted the upgrade and re-started (Sri Lanka from MySQL)</li></ol>:: So '''check''' the log ''C:\IMSMAng\trayLauncher\trayLauncher.log'' even if the upgrade scripts have not thrown an error.

====Check to be done BEFORE next step (mandatory)====__NOEDITSECTION__

Alnaucler

NoPublic, bureaucrat, administrator

6,632

edits