Migrate > Migrating WebSphere Commerce > Migrating the WebSphere Commerce Server using the command line

Run the database pre-migration checker

Prior to running the database migration, run the pre-migration checker to expose any issues with the database that might cause errors during the migration. This allows you to correct any issues, ensuring that the database migration completes successfully.

Procedure

1. Open a command window:

   • Open a shell prompt window on the WebSphere Commerce version 7.0 machine, and switch to the WebSphere Application Server user ID (for example, wasuser) by entering the following command:

     su - wasuser
     

   • Start a Qshell session.

   • Open a DB2 command window

   • Open a command prompt window.

2. Run the database pre-migration checker. Navigate to the WC_INSTALL/bin directory and run the following command:
   

   ./wcim_ant.sh -tier db -action check -from previous_version -instanceName instance
   

   
   

   wcim_ant.bat -tier db -action check -from previous_version -instanceName instance
   

   Where:

   previous_version

   Is the current WebSphere Commerce version you are migrating from for example, 561 or 60.

   Notes:

   1. The migration script will prompt you to enter the database user name, password, database name, and whether the database is on the remote machine and the remote machine name. When you input the remote machine name, you need enter the fully qualified host name or the IP address.

   2. The schema name must be same as the user name. If the user name is different than the schema name, you need transfer the schema to a schema which has same name with user. Alternately, you can create a database user which is the same as the current schema and use this user to migrate the database.

   Example

   ./wcim_ant.sh -tier db -action check -from 60 -instanceName my_instance
   >Database type? [ db2 ] (cloudscape,db2,os400,oracle,)
   os400
   >Remote database? [ false ] (true,false,)
   false
   >Database name?
   my_database_name
   >Database user?
   my_instance
   >Database user password?
   my_db_password
   >Database server port?
   50000
   >Is this a test run? [ Yes ] (Yes,No,)
   Yes
   >Is the database backup completed? [ Yes ] (Yes,No,)
   Yes
   >Is the database restore completed? [ Yes ] (Yes,No,)
   Yes
   

3. Check the following log files for messages or errors:

   • 

     WC_INSTALL/logs/WCIM/wcim.server.yyyy.mm.dd_hh.mm.ss.log
     

   • 

     WC_INSTALL\logs\WCIM\wcim.server.yyyy.mm.dd_hh.mm.ss.log
     

4. The database pre-migration checker checks that you have adequate free disk space to migrate the largest table in the database. If you see a message similar to the following you may have to increase your disk space.

   • 

     In order to migrate one of the biggest tables table_name in the database,
     the database migration script needs at least nn MB in the database log space.
     It also needs at least nn MB free disk space in the tablespace.
     Otherwise, the database migration may fail.
     

   • 

     In order to migrate one of the biggest tables table_name in the database,
     the database migration script needs at least nn MB in the database undo segment.
     It also needs at least nn MB free disk space in the tablespace.
     Otherwise, the database migration may fail.
     

5. Complete the actions suggested that are output to the screen or that are contained in the wcim.server.yyyy.mm.dd_hh.mm.ss.log file.

6. Back up the updated WebSphere Commerce database. Refer to the database documentation for more information.

7. Run the pre-migration checker again.

Next topic:

Migrate the WebSphere Commerce database using the WCIM migration script

+

Search Tips   |   Advanced Search