When data is migrated:
The existing data is transferred (copied) into the new empty schema. At this step, the internal structure of some columns (Component Data Arrays) remains in the EAE 3.3 format. The columns are then reformatted and changed to AB Suite format.
The existing database should be empty to avoid potential conflicts that can cause the migration process to fail.
It is recommended that the source and target databases be on the same machine. If necessary, copy the source database to the machine where migration is undertaken.
The EAE Data Migration Wizard enables migration of data from an Enterprise Application 3.x application to an Agile Business Suite application.
To enable migration of an existing database, perform the following:
Select Start, expand Agile Business Suite 7.0 > and then click EAE DBMigrate Utility SQL 2014 or EAE DBMigrate Utility SQL 2016 or EAE DBMigrate Utility SQL 2017.
The EAE Data Migration Wizard appears.
Note: The name of the DBMigrate Utility depends on the version(s) of SQL Server and respective SSIS version installed in the machine. For example, if SSIS 2014 or SSIS 2016 or SSIS 2017 is available, then the utility name is either EAE DBMigrate Utility SQL 2014 or EAE DBMigrate Utility SQL 2016 or EAE DBMigrate Utility SQL 2017, whereas if SSIS 2014, SSIS 2016 and SSIS 2017 are available, then the utility name appears as EAE DBMigrate Utility SQL 2014, EAE DBMigrate Utility SQL 2016 and EAE DBMigrate Utility SQL 2017 in the Start menu.
Enter the EAE source database details.
First choose the source database type from SQL or Oracle by clicking either the MS SQL Database or Oracle Database tab.
Enter the following details for the EAE Source Database:
Source Machine – This is the SQL Server instance for an MS SQL database, or SID for an Oracle database. If you are using the default instance, you can use local/localhost. You can specify a different named instance if you have one setup that can point to another machine; but, that is dependent on internal network support of SQL Server/Oracle rather than the EAE Data Migration Wizard.
Database – This is the database (catalog) for an MS SQL database. This field does not apply for Oracle databases.
User Name – This database user name has sufficient privileges to read the source database.
The user account should be one that can connect to the database server using database authentication.
Password – This field is the corresponding password for the database user name that you enter.
Note: The User Name and Password entered should be an SQL-SERVER user or it can also be a LINC user who has privileges to read the source database and NOT a Windows user. For example, if you use “sa” as the user name and its related password, you can migrate. However, if you enter a Windows user name and password, the system does not allow you to migrate.
Schema – The Schema is the owner of the system application tables. All tables for one EAE 3.3 application have names in the format:
<Schema>.<Logical DB>_<text>
So, for example, if the tables for your application are named EAE.DD_<text>, enter EAE in the Schema field. If you look in the Enterprise Manager, you will see the owner of the SAMPLE tables is dbo.
Logical DB – The table prefix used in the EAE 3.3 tables. All tables for one EAE 3.3 application have names in the format:
<Schema>.<Logical DB>_<text>
So, for example, if the tables for your application are named EAE.DD_<text>, enter “DD” in the Logical DB field. Examine the SAMPLE tables in Enterprise Manager, and you will notice the tables are prefixed with “SAMPLE”.
Once you have entered these details, click Back to amend details in the previous screen, or click Next.
The Target Database dialog appears. Specify the details of AB Suite database you are migrating to in the target database settings. At this point in the process, your AB Suite application must already be deployed to a runtime server and an empty target database should exist. This prepares the target database to receive the
migrated data. Refer to Using the Administration Tool for more information on creating and preparing databases.
Enter the AB Suite Target Database settings. Enter the following details for your target database, MS SQL:
Data Source – Enter the SQL Server instance for an MS SQL database. If you are using the default instance, then (local) can be entered. You can specify a different named instance if you have one setup. The named instance can point to another machine, but that is dependent on SQL Server internal network support, rather than the EAE Data Migration Wizard.
Database – Enter the database (catalog) for an MS SQL database. This is the deployed but empty Agile Business Suite application.
Schema – The Schema is the owner of the system application tables in the target database.
All tables for one Agile Business Suite application have names in the format:
<Schema>.<text>
So, for example, if the tables for your application are to be named APP.<text>, enter “APP” in the Schema field.
Click Next to view to the Options settings. There is only one option that needs to be set.
Parallel Threads – Enter the number of parallel threads to be run during migration. The EAE Data Migration Wizard can use up to one thread per CPU on the migration machine.
Fewer details are required for the target because the user running the migration wizard is assumed a target database user with authenticated operating system and sufficient privileges to populate the tables.
Once you enter the required details, click Back to amend details on the previous screen, or click Next.
The Data Migration tool migrates the specified data. If all the steps are executed properly, migration proceeds after clicking Next and then Finish. This takes some time to complete for a large database and prompts you with either Successfully completed or Successfully completed with warnings. For any errors, check the DBMlogs in C:\AB Suite 7.0\data\public\log and search for ERROR.
Logs
The migration log is stored in the DBMlog.log file. By default, the log directory is available at C:\AB Suite 7.0\Data\public\log.
The log also reports the number of rows migrated and the number of tables migrated at the end. It does not let you cross-reference this information back to find out which tables were causing trouble. You might be able to get some of this information from SQL Server log and the system event log.
Two other log files, MigrationLog.txt and DBSchema_<db_name>.xml, are created under the current working folder of the Data Migrate Tool. For an installed product these files are found in the bin directory of AB Suite 7.0. By default, they are available at C:\Program Files\Unisys\AB Suite 7.0\bin.
The Microsoft SQL Server Integration Service package creates the MigrationLog.txt, which is used to move the data from tables in the source database to tables in the destination database. It might contain additional data that might be useful in diagnosing DBMigration failures.
The DBSchema_<db_name>.xml file is an xml representation of the schema of the database.