Converting 6.5.1 Databases to 6.6.1 Format
1 After CRM 6.6b7 is installed, remove all the Progress compile code (*.r files) in the following folders from the newly installed QAD CRM 6.6b7 CD environment:
• dataexch
• lib
• integration\mfgpro
• progs
• report
• system
• triggers
2 Modify the crm661_install_dir\qadsfamaupgrade.pf file to connect to the QAD CRM 6.5.1 databases in multi-user mode. If your QAD CRM 6.5.1 databases have been configured in the self-service (shared memory) mode on your database server, you must temporarily restart using the client server mode, so that the CRM 6.6.1 Deployment Utility can access the databases from the Windows Deployment server.
3 Make sure no other user or Progress process, including any AppServer process, is using the QAD CRM 6.5.1 databases that you are upgrading.
4 Click QAD CRM Deployment Utility.
Note: If you are running QAD CRM 6.5.1 databases on the server using Progress 10.1C while your CRM 6.6.1 is set up against Progress 10.2Bxx, you might get an error message after you click the QAD CRM Deployment Utility icon.
To resolve this error, connect to the QAD CRM 6.6.1 session using the Progress version that is compatible with the Progress version used by your 6.5.1 database server:
a Modify all QAD CRM .ini files in crm_install_dir of your QAD CRM 6.6.1 installation. Change the DLC system variable and other Progress configuration parameters to point to a Progress version that is compatible with the Progress version used by your 6.5.1 database server.
b Modify the CRM 6.6.1 shortcut icons created as a result of CRM6.6.1 installation, and ensure that they also reference the compatible Progress file prowin32.exe.
5 On the QAD CRM Deployment Tools screen, click Progress Editor.
6 In the Procedure editor window, run the program punfreezetbl.p.
a Enter the following command:
run <crm661_install_dir>\conversion\punfreezetbl.p.
b Select Compile|Run from the menu or Press F2.
c The program sets _frozen = no for all tables in CRM databases. After the program is executed, a confirmation message appears; click OK and close the editor window.
7 On the QAD CRM Deployment utility screen, click QAD CRM upgrade Utility, fill in the following Utility settings, and click OK.
Parameter file.
Specify the name of the parameter file (qadsfamaupgrade.pf) to connect to your CRM 6.5.1 databases running in multi-user mode.
INI file.
This is pre-populated for you by default.
Input file.
Specify the path to file upgrade_v651_v66b7.txt. You can locate this file in the <crm661_install_dir>\conversion\v651_v66b7 folder.
Log file.
Specify the name of the log file.
8 After you fill in the Utility settings, you are prompted to check whether you have backed up the databases. Make sure you have backed up the databases and click Yes to continue.
9 You see the following message after the data loading has been completed. You can click Yes to see if there are any errors recorded in the log file.
Note: Some .df loading errors might be reported in the log file, since CRM uses Progress tools for loading the .df file. If the .df loading fails for some reason, see bisgen.e, bisgmenu.e, and dataexch.e files under crm661_install_dir.
Make sure that you fix all errors before you proceed any further. If you encounter errors during the
.df loading, restore the databases from the backup and continue again from
step 3.
10 When the .df loading is correct and there are no .e files in crm661_install_dir, the Upgrade Utility screen appears.
a Make sure that the Load from file option is selected; by default, it is selected.
b Make sure the Input file field displays the conversion file that you specified earlier; that is, crm661_install_dir\conversion\v651_v66b7\upgrade_v651_v66b7.txt.
c Click Load Data.
Note: After you click Load Data, you are prompted once again to confirm that your databases have been backed up. Click Yes to continue.
d After the data loading is complete, the system prompts you to view the log file. If you need any help to resolve errors in the log file, contact QAD CRM support.
e Close the Upgrade Utility window and any other Deployment utility windows, including the main Deployment Tools window.
11 Restart the Deployment Tools window again and click Progress Editor.
a On the Progress Editor screen, select Tools |Data Administration.
b On the Data Administration screen, click the Database menu, select bisgen as the working database, and click OK.
c On the Data Administration screen, select Admin|Load Data and Definitions |Table Contents(.d file), choose the table filter_val, and click OK.
d Before loading crm661_install_dir\conversion\v651_v66b7\qps120812-filter_val.d, modify the .d file to replace domain ID sports with a valid domain ID. To enable the filters for other domains, modify domain ID and import the data again.
e In loading data for the table filter_val, select the input file crm661_install_dir\conversion\v651_v66b7\qps120812-filter_val.d and click OK.
Note: When a message about no code page defined in the input file appears, click OK and accept the default code values.
f When database content loading is complete, make sure the Records Loaded column shows 3 and the Total Errors Column shows 0, and click OK to close the information window.
g Exit the Data Admin window by selecting Database|Exit.
h Exit Progress Editor by selecting File|Exit.
i Restart Progress Editor and run the pfreezetbl.p program. To run the program, enter the following command, then select Compile|Run from the menu or Press F2.
run <crm661_install_dir>\conversion\pfreezetbl.p
This sets _frozen = yes for all tables in CRM databases. After the program is run, a confirmation message appears; click OK and close the editor window. Click No when you are prompted to save changes in the Progress Editor buffer.
j Close the Deployment Utility. If you do not see any errors in the log file, your CRM 6.5.1 databases have now been upgraded to 6.6.1.
