3. Run Data Upgrade
3.1. Run automatic environment upgrade
To upgrade data, see online documentation for HOPEX V6.0: PLATFORM - Administration > Administrator Guide > Environments > Updating an environment
It is useful to record start time and end time of environment upgrade processing in the specific migration document for future references.
Note that duration can vary according to migration path, infrastructure and volume of data. Anyway, this is a heavy processing that lasts several hours. Verify that the machine will not be shut down (or go to sleep, or hibernate).
3.2. Check logs and environment compilation
Automatic environment upgrade run various conversion tools that could meet errors.
Review report tabs and logs. In particular, check that no compilation error is reported.
(MegaCrdxx.txt located by default in <HOPEX environment folder>)
megaerrxx.txt log (located by default in C:\ProgramData\MEGA\Hopex Application Server\<instance>\Logs
|
File
|
Default location
|
|
Environment report (MegaCrdYYYYMM.txt)
|
C:\ProgramData\MEGA\Hopex Application Server\<instance>\Repos\<environment folder>
|
|
megaerr log (megaerrYYYYMMDD.txt)
|
C:\ProgramData\MEGA\Hopex Application Server\<instance>\Logs
|
After this step:
• HOPEX environment must compile without error.
3.3. Backup migrated data
Perform SQL backups (.BAK files) for this intermediate steps. In case of a further error requesting to restore data, this will be a stable point of restore.
Example for an environment named Migration and instance port 5001:
• Migration1_SystemDb
• Migration1_MasterData
• Migration1_HAS_5001