Installation guide

Important!
We recommend checking the migration log file after each leg of an upgrade before moving
on to the next leg.
To check the status of SQL Server upgrades
1. Open the log file C:\mvf-mig6\data\logs\migrate_database_to_IMPAX6.5.3.log.
2. If the following warning appears in the log file, you can safely ignore it:
Warning: The table 'CHANGE_CONTEXT_DETAIL' has been created but its maximum
row size (8095) exceeds the maximum number of bytes per row (8060). INSERT
or UPDATE of a row in this table will fail if the resulting row length exceeds
8060 bytes.
3. Ensure that Migration Complete Successful appears at the end of the log file.
If this message does not appear, review the rest of the log file to see where the upgrade failed.
Solve the problem, then rerun the upgrade script.
Taking a post-upgrade system snapshot
(Topic number: 6845)
12.
After upgrading to IMPAX 6.5.3, use the migration_inventory tool to capture the state of the system
to compare it with the previous IMPAX system. Perform this task on any computer on which the
Migration Tools have been installed that can access the 6.5.3 Database Server.
To take a post-upgrade system snapshot
1. In a command prompt or terminal window, change to the directory containing the
migration_inventory tool.
2. On a Windows server, type
migration_inventory -s -d database_name -U database_user_name -P database_password
-D Database_Server_host_name
The output is stored in the migration_info table. It lists the number of IMPAX studies, total
objects, and objects in cache. It also lists all IMPAX source stations and DICOM printers.
3. To create a report file with this information, type
mig_reporter -t system_inventory_tool (Windows)
This command writes the output of the migration_inventory command to a report file in the
/usr/mvf-mig6/reports or C:\mvf\mig6 directory.
AS300 Upgrade and DAA Consolidation Guide—IMPAX 5.2 or 5.3 to IMPAX 6.5.3 36
Agfa Company Confidential—Subject to Non-Disclosure Obligation