Addressing Migration Issues

While importing a data from Enterprise Application Environment Release 3.3 to Agile Business Suite, you might encounter some issues and behavioral differences. You can apply the following guidelines to resolve the migration issues.

Migrating Profiles

In EAE for Windows, you can define a profile with duplicates not allowed settings, but at run time duplicated rows can be inserted. AB Suite does not allow duplicated rows in such profiles. This means that if duplicated rows are passed to AB Suite during migration, they are rejected.

To avoid migration problems, you should inspect all “duplicates not allowed” profiles in EAE data and ensure there are no duplicate rows. If there are duplicate rows, either correct the data or change the profile to allow duplicates.

You can use the UNIQUEXI utility to report duplicated rows in “duplicates not allowed” profiles in EAE for Windows. The utility is available in the Utilities section of the Agile Business Suite Product Support Website.

Installing UNIQUEXI

Copy the uniquexi.jar file to the %LINCIIDIR%\bin directory. The utility is used in two steps:

The utility runs and generates a SQL script. The script reports the number of duplicates in every "duplicates not allowed" profile. Enter the following at the
command prompt:
```
set JAVA_HOME=<the directory of java 1.4.1>
cd %LINCIIDIR%\bin
%JAVA_HOME%\bin\java -jar uniquexi.jar <schema> <LINC system directory>
```
where, <schema> is the DB user who owns the tables of this LINC system. For example,
```
set JAVA_HOME="C:\Program Files\Java\j2re1.4.2"
%JAVA_HOME%\bin\java -jar uniquexi.jar dbo C:\MySystem
```
In the <LINC system directory> two scripts are generated for MS SQL server and Oracle accordingly:
```
MsUniqueXInspect.sql
OraUniqueXInspect.sql
```
A database utility, ISQL/SQLPLUS, runs the script and gets the number of duplicates.
Enter the following at the command prompt:
```
cd <LINC system directory>
isql -U <user name> -P <user password> -d <database> -i MsUniqueXInspect.sql -e
```
Or
```
isql -E -d <database> -i MsUniqueXInspect.sql -e
```
The first option assumes that SQL server authentication is possible. A user with
<user name> and <user password> is allowed to read the database.
The second option assumes that a user running the command is a database user and is allowed to read the database.
The result is:
```
duplicates_in_PROFA
--------------------
1
(1 row affected)
duplicates_in_PROFB
--------------------
0
(1 row affected)
```
For Oracle, enter following at the command prompt:
```
cd <LINC system directory>
set ORACLE_SID=<database>
sqlplus <user name>/<user password> @OraUniqueXInspect.sql
```
The user with <user name> and <user password> is allowed to read the database. The result is:
```
DUPLICATES_IN_PROFA
--------------------
1
DUPLICATES_IN_PROFB
--------------------
0
```

Migrating User-Maintained Tables

A user-maintained table provides database performance features that might not be available with System Modeler. The custom nature of user-maintained tables makes it impossible to enable migration of these tables automatically.

It is your responsibility to ensure that user-maintained tables are consistent and reorganized with corresponding class definitions.