Conversion
After the preparation part is completed the actual conversion to Unicode can be started.
The Migration steps:
-
Stop shared memory and log on again.
Shared memory must be disabled to avoid loading old program domains from this service.
A way to stop shared memory is to create a backup of the <BSE>/lib/srdd_tab6.2 file, and create an empty <BSE>/lib/srdd_tab6.2 file.
For more information regarding shared memory, see the Infor Enterprise Server Administration Guide.
-
Select Actions > Convert (BSE) environment to Unicode
A question is displayed, asking to confirm to convert the environment to Unicode.Caution:This step starts the Unicode migration process. You cannot rollback to the current environment within the Easy Unicode Migration (ttcon8110m000) session. The environment is not accessible.
-
Click Yes to continue.
The environment (BSE) is converted to Unicode. The process included:
- Updating the environment settings.
The environment is set to Unicode with the corresponding multibyte factor (value: 4). The settings are stored in the table 'Multibyte Parameters' (ttadv406).
- Updating
BSE/lib/tss_mbstore6.2
This file contains the mode whether legacy TSS or UTF-T is produced.
When migrating to Unicode with high ASCII support, the setting is:
Format: UTF-T:0:<installation locale>
When migrating to Unicode without high ASCII support, the setting is:
Format: UTF-T:0:ISO88591
- Updating BSE/lib/defaults/all
The high ASCII settings are controlled by the resources
high_ascii_tolerance
andhigh_ascii_tolerance_strict_mode
. When migrating to Unicode with high ASCII support, the setting is:high_ascii_tolerance:1 high_ascii_tolerance_strict_mode:1
When migrating to Unicode without high ASCII support, the setting is:
high_ascii_tolerance:0
- Updating
BSE/lib/defaults/db_resource
The row versioning concept is enabled.
Format: bdb_use_row_version:1
- Dumping program domains (pd-files).
Based on the updated environment settings the program domains of all present package combinations are dumped to runtime. All multibyte string datatype domains are rescaled according the updated multibyte factor (4).
- Updating the environment settings.
-
Run the database configuration procedure on the database server.
Note: Before changing the collation ensure that:
- You are logged off from LN and the logic service.
- Shared memory and the job daemon are stopped.
For Microsoft SQL Server the collation of the database must be set to:
Latin1_General_100_CS_AS_KS_WS
For Oracle Server no configuration changes are required.
For general information regarding collation see these guides:
- Infor LN Installation Guide
- Infor Enterprise Server Technical Reference Guide for Microsoft SQL Server Database Driver
How to set or change the database collation, see the Microsoft knowledge base.
-
Run and check the conversion of the Tools data manually.
Start the generated script on the command line as administrator. If the conversion of the Tools data has successfully completed the application companies are ready to be converted.
-
Tools data conversion
First, run the conversion of the Tools company 0 data. Run the generated script that is described in the preparation phase from the command line.
- Navigate to <BSE_TMP>\uni\tools
On UNIX run this command:
./cTools.sh
On Windows run this command:
cTools.bat
The output of the conversion is logged in this folder: <BSE_TMP>\uni\data
See for explanation of the files in the "Directory Structure":
c000_<source locale>.out
: Contains the conversion result of all processed tablesc000_<source locale>.err
: Contains possible errors of not correctly processed tables.In the Easy Unicode Migration (ttcon8110m000) session, the <source locale> is the locale that is linked to company 0.
After the tools conversion has completed, log on again and start the Easy Unicode Migration (ttcon8110m000) session. Verify if the Data Conversion field of company 0 is set to Converted. The status indicator can also be set manually.
- Navigate to <BSE_TMP>\uni\tools
-
Select Actions > Data Conversion Application
A question is displayed, asking to select the companies to be converted of ALL package combinations or the SELECTED package combination. The selected package combination is the actual displayed package combination in the Easy Unicode Migration (ttcon8110m000) session.
- Click Yes to continue.
-
Click OK when the process has
finished successfully.
In the Easy Unicode Migration (ttcon8110m000) session the Data Conversion field of the successfully processed companies is set to Converted with a time stamp. In case the conversion for a company failed the field for the concerning company is set to Failed with a time stamp.
You can also run the data conversion for marked companies only in the Easy Unicode Migration" (ttcon8110m000) session.
-
Tools data conversion
- Close Infor LN and stop shared memory, when all companies are converted successfully.
-
Move back the saved
$BSE/lib/srdd_tab6.2
and restart shared memory. -
Restart all previously stopped processes, such as:
- Job daemon
- Printer daemon (UNIX)
- Restart Infor LN.
-
Start the
Support Information Tool (ttsit0100m000)
session.
Verify if the Unicode field on the General tab is selected.Note: Running the Check Tables (ttaad4232m000) session to validate the table consistency after the migration can result in a 512 error on the table ttaad401 Fast Unicode migration temp table. You can ignore this error.