Data Migration was a one-time optional activity to migrate the underlying portfolio database in e- config and was only needed during the e-config Upgrade that was rolled out on January 21, 2013.
This document references both Windows XP and Windows 7 specific guidelines as those two operating systems were supported at that time. The guidelines outlined in this document are no
longer applicable and should not be used. This document is now for reference only.
e-config Data Migration Guidelines
Version 1.1
Author: e-config Team
Owner: e-config Team
Document History
Revision History
Date of this revision: 02-Apr-2014
Revision Number
Revision Date
Summary of Changes Changes
marked
1.0 18-Jan-2013 Document Publication (N)
1.1 02-Apr-2014 Updated cover page (N)
Contents
1. INTRODUCTION ... 4
1.1 Purpose ... 4
1.2 References ... 4
2. HARDWARE / SOFTWARE REQUIREMENTS ... 5
2.1 Minimum Hardware Requirements for e-config ... 5
2.2 Software Requirements ... 5
3. LIMITATIONS / KNOWN ISSUES ... 6
3.1 Known Issues ... 6
3.1.1 Connection to Destination Not Established! error displayed ... 6
3.1.2 Connection to Source Not Established! error displayed ... 6
3.1.3 Data Migration tool shows memory read error when closing on XP ... 6
3.1.4 No portfolios in migrated database when running Data Migration tool after e-config upgrade installation ... 6
3.1.5 Database file econfig.accdb not created when migrating an empty econfig.mdb ... 7
3.2 Limitations... 7
3.2.1 Data migration tool unusable with 64-bit version of Microsoft Office ... 7
3.2.2 Data migration tool crashes when migrating a database located on c:\... 7
4. DATA MIGRATION SETUP ... 8
4.1 Installing econfigDMSetupTool ... 8
5. MIGRATING E-CONFIG DATABASE USING INTERACTIVE DM TOOL... 12
5.1 Migrating econfig.mdb to econfig.accdb ... 12
5.2 Reviewing data migrated ... 17
6. USING THE MIGRATED ECONFIG.ACCDB DATABASE ... 19
6.1 Database located in \econfig\userdata directory prior to installing e-config Upgrade ... 19
6.2 Database located outside of e-config installation path prior to installing e-config Upgrade . 19 7. MIGRATING E-CONFIG DATABASE USING COMMAND LINE DM TOOL ... 20
7.1 Migrating econfig.mdb to econfig.accdb ... 20
8. COMPACTING E-CONFIG DATABASE WITH DATA MIGRATION TOOL ... 24
8.1 Compacting with Interactive DM tool ... 24
8.2 Compacting using CommandlineDM ... 25
9. GETTING SUPPORT ... 27
1. Introduction
The IBM Configurator for e-business (e-config) is a PC-based hardware and software configurator for POWER Systems (rack/tower and blades), and GTS/ISS, System z™ and S/390 Servers, Storage, Retail Store Solutions, iSeries™ and AS/400® Servers and Software and pSeries® and RS/6000® Systems and Software (except SP).
The suite of tools enables a user to configure multiple product lines, view all of the selections from a main view, verify product availability, view the system diagram, price the system and submit the order to manufacturing for processing.
The e-config application is being updated to work with a new version of the core engine code, including updated installation tools. The core engine of the tool has been changed to provide critical updates (removing the dependencies on MS JVM, MS Visual Studio 6 and MS Jet; migrate to current version of MS Access; and provide support for Windows 7 for both 32-bit and 64-bit).
One of the major changes in this upgrade is about upgrading the core database that is included with e-config.
Currently, the core database is called econfig.mdb and is built around old database technology with a maximum size of 1GB. With the installation of this e-config Upgrade, the new core database is econfig.accdb and it uses the most current database technology and data formats, allowing up to 2GB of total data to be stored in it.
1.1 Purpose
The data migration is an optional step and is not required or mandatory step for using the e-config Upgrade.
The data migration process allows users to migrate existing data that is contained in their current database to the new e-config Upgrade's core database.
If you do not need the existing portfolios from the current e-config database, then it is not necessary to continue with the data migration steps in this document. In such a case, during the installation, you should choose to not perform data migration. This can be accomplished by selecting ‘No’ to continue the installation when e-padm displays a message that an unmigrated database was found. The installation will continue and create an empty core database for e-config.
1.2 References
The e-config prerequisites and installation guidelines referred to in this installation guide will be provided in a separate document found at the link below.
Newer versions of the document(s) listed below will take precedence.
Ref. # Document Name Version # Date Available
1 e-config Upgrade Installation Guidelines 1.0 18-Jan-2013
2. Hardware / Software Requirements
There must be enough additional space on the hard drive to create a backup copy of the existing database and create the new database. For example, if your econfig.mdb database is at the upper limits (max size 1 GB), ensure there is a minimum of 2 GB free space available to create the new database. ie: 1 GB for econfig.mdb and 1 GB for econfig.accdb.
The tool will compact the new database but depending on the file contents it may not be able to compress it any smaller than the original database size.
2.1 Minimum Hardware Requirements for e-config
XP minimum requirements:
1.2 GHz CPU (Intel Pentium, Intel Celeron)
500 MB RAM
400 MB disk space for e-config
Network interface: 10 MB for LAN connection Vista and Windows 7 minimum requirements:
1GHz CPU
1 GB RAM (32-bit) or 2 GB RAM (64-bit)
16 GB disk space for OS, 400 MB for e-config
Network interface: 10 MB for LAN connection2.2 Software Requirements
Supported Operating System:
Windows XP Professional with SP3
Vista Business (32-bit) with SP2
Windows 7 Professional (32-bit) with SP1
Windows 7 Professional (64-bit) with SP1
3. Limitations / Known Issues
If having problems with the data migration, read though this section to determine if your problems are addressed and follow the suggested resolution. If the problem is not addressed, contact the Help Desk.
Contact information can be found at http://www.ibm.com/services/econfig/announce/support.htm
Workarounds for known issues have been included. Items identified as a limitation may not currently have a work around.
3.1 Known Issues
3.1.1 Connection to Destination Not Established! error displayed
Problem: Connection to Destination Not Established! error message received when trying to migrate database.
Cause: Incompatible version of Microsoft Access Database Engine 2010 installed or Microsoft Access Database Engine 2010 32 bit not installed.
Resolution: Uninstall the incompatible version Microsoft Access Engine and install Microsoft Access Database Engine 2010 32-bit from the Microsoft website.
3.1.2 Connection to Source Not Established! error displayed
Problem: Connection to Source Not Established! error message received when trying to migrate database or compact a database using the CommandlineDM.
Cause: Incompatible version of Microsoft Access Database Engine 2010 installed or Microsoft Access Database Engine 2010 32 bit not installed.
Resolution: Uninstall the incompatible version Microsoft Access Engine and install Microsoft Access Database Engine 2010 32-bit from the Microsoft website.
3.1.3 Data Migration tool shows memory read error when closing on XP
Problem: On XP, when closing the Data Migration tool, an application error (unable to read memory) is received.
Cause: Incorrect version of Microsoft Visual C++ 2010 x86 Redistributable installed.
Resolution: Uninstall the incompatible version of Microsoft Visual C++ x86 Redistributable and install Microsoft Visual C++ 2010 x86 Redistributable version 10.0.30319 from the Microsoft website.
3.1.4 No portfolios in migrated database when running Data Migration
tool after e-config upgrade installation
Problem: After choosing to install e-config without performing the optional data migration step, the user has a new core database with no portfolios. If user now decides that he wants to migrate the portfolios from the
old database and executes the data migration procedure, he finds that even after running through all the steps, the portfolios do not appear in the new core database.
Cause: Once the e-config upgrade code is installed, a clean econfig.accdb is placed in the userdata directory. The Data Migration tool is designed so that it will not overwrite any existing econfig.accdb in
\econfig\userdata because there may be portfolios saved in the new database.
Resolution: If any portfolios were saved in the upgraded version of e-config, export the portfolios out of the core database using the File -> Export option and close e-config. Open Windows Explorer and navigate to the \econfig\userdata directory. Rename econfig.accdb to econfig.accdb.old. Continue with data migration described in Sections 5 and 6 of this document which will create a core database econfig.accdb with migrated portfolios from old database. Then import back the portfolios that had been exported from the previous version of the core database by choosing the File -> Import option within e-config.
3.1.5 Database file econfig.accdb not created when migrating an empty
econfig.mdb
Problem: No econfig.accdb file created when migrating an empty econfig.mdb even though the data migration tool shows a message the migration was successful.
Cause: The data migration tool doesn’t find anything to migrate so no econfig.accdb is created.
Resolution: Perform data migration only on an econfig.mdb file that contains portfolios.
3.2 Limitations
3.2.1 Data migration tool unusable with 64-bit version of Microsoft
Office
Problem: Data migration tool will not install when 64-bit Microsoft Office is installed or e-config becomes unusable after 64-bit version of Microsoft Office is installed.
Cause: There are several known conflicts with the 64-bit version of Microsoft Office and applications that are part of the core underlying technology used in e-config. Please see
http://go.microsoft.com/fwlink/?LinkID=245825 for information on known compatibility issues.
Resolution: Uninstall the 64-bit Microsoft Office and install a 32-bit version of Microsoft Office.
3.2.2 Data migration tool crashes when migrating a database located on
c:\
Problem: Migrating econfig.mdb located in the root directory C:\ cause the data migration tool to crash.
Cause: Microsoft restricts creating a file on C:\ unless the user logs in via admin credentials. The data migration tool creates the migrated database in the same folder as the database being migrated but due to this Microsoft restriction, the tool is unable to create the database in c:\.
Resolution: Move econfig.mdb to another location and rerun the migration tool.
4. Data Migration Setup
The following instructions describe the steps necessary to install the data migration tool.
4.1 Installing econfigDMSetupTool
Download econfigDMSetupTool.exe from http://www.ibm.com/services/econfig/econfigDMToolSetup.exe prior to running. The file should be downloaded to the local machine prior to executing the file.
1. Double click the downloaded file econfigDMSetupTool.exe
2. Click Next on the e-config Data Migration tool Welcome
3. Read the License Agreement, click I accept the terms of the license agreement then click Next
4. Enter Customer Information and click Next
5. Select Complete for Setup Type then click Next
6. Click Install to begin the installation
7. Click Finish when the setup has completed
5. Migrating e-config database using Interactive DM
tool
The steps below describe the method to migrate the existing database (econfig.mdb) to the new database format (econfig.accdb) using the interactive data migration tool which is the recommended method.
The steps listed assume that e-config is installed to the default location c:\econfig and the Data Migration tool is installed to the default location c:\econfigDM.
5.1 Migrating econfig.mdb to econfig.accdb
1. Follow the steps in Section 4 to first install the data migration tool.
2. In Windows Explorer, navigate to c:\econfigDM and double click InteractiveDM.exe
3. In the Data Migrator tool that is launched, click the folder icon to the right of the text box
4. In the browser window that is opened, navigate to c:\econfig\UserData
5. Select econfig.mdb then click Open
6. Click Migrate to start the migration process
7. The econfig.mdb will be backed up prior to starting the migration
8. A size and time estimate to migrate the database. Click Continue to begin the migration.
9. If a corrupt entry is found the following message will be displayed. To expedite the migration, select Yes to All. The log file can be reviewed after the completed migration to see all corrupted entries
that were not migrated.
10. Click OK on the completion message
11. The new econfig.accdb will then be compacted. Click OK when complete
12. Close the Data Migrator by clicking on the red X in the upper right corner
5.2 Reviewing data migrated
1. In Windows Explorer, navigate to c:\econfig\UserData
2. Select the file DataMigration [econfig.mdb].txt and open with Notepad or other text reader
3. Review the contents of the file to see which files were migrated. A detailed list of each portfolio found in the databse and if it was sucessfully migrated or not is included.
6. Using the migrated econfig.accdb database
The migrated database can now be used with the e-config Upgrade installation. The instructions assume e- config and the Data Migration tool are installed to the default location. (c:\econfig and c:\econfigDM)
6.1 Database located in \econfig\userdata directory prior to installing e-
config Upgrade
If the migrated database was in the installed e-config directory c:\econfig\userdata you can start the e-config Upgrade installation with no additional intervention.
6.2 Database located outside of e-config installation path prior to
installing e-config Upgrade
Copy the migrated database econfig.accdb to the installed e-config directory c:\econfig\userdata
Begin the installation process as defined in the e-config Upgrade Installation Guidelines document
7. Migrating e-config database using command line DM
tool
The steps below describe the method to migrate econfig.mdb to econfig.accdb using the command line data migration tool which is only recommended for experienced command line users.
The steps listed assume that e-config is installed to the default location c:\econfig and the Data Migration tool is installed to the default location c:\econfigDM
To see help for the command line tool, type commandlinedm –h at a command prompt.
7.1 Migrating econfig.mdb to econfig.accdb
1. Follow the steps in Section 4 to first install the data migration tool.
2. Open a command prompt, navigate to c:\econfigDM
3. Type the command commandlinedm –mc “c:\econfig\userdata\econfig.mdb” and press enter to start the migration process
4. The econfig.mdb will be backed up prior to migrating
5. The migration will start automatically and continue until finished. NOTE: Even if there is a corrupted file, it will continue to migrate the data when using the command line tool.
6. A message will be displayed when the migration and compacting process is complete
7. The log file can be found in the same location described in Section 5.2
8. Compacting e-config database with Data Migration
tool
The database can be compacted to reduce the overall size. This is not the method to use to compact the database if an error is received that the database is near the maximum size.
If an error has been received in e-config that the database has reached maximum size, contact the Help Desk for instructions on how to reduce the size.
8.1 Compacting with Interactive DM tool
1. Follow steps 1-5 in Section 5.1 2. Select Compact
3. Click OK when the compact process completes
4. Close the Data Migration tool
5. The compacted database is saved with the original database name econfig.mdb and the backup is econfig.mdb[Original]
8.2 Compacting using CommandlineDM
1. Follow steps 1-2 in Section 7.1
2. Type the command commandlinedm –c “c:\econfig\userdata\econfig.accdb” and press enter to start the compact process
3. The compacted database is saved with the database name econfig.accdb.Compacted and the backup is econfig.accdb[Original]
9. Getting Support
To get support for any issues you may run into during the installation process; contact the e-config Help Desk. Contact information can be found on the e-config home page under the Support link.
