Run the database premigration checker

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

To run the database premigration checker, complete the following steps:

1. Open a command window:

   • I5/OS|Open a QShell window (STRQSH command) on the WebSphere Commerce machine.

   • AIX|Linux|Solaris|Open a shell prompt window on the WebSphere Commerce machine, and switch to the WAS user ID (for example, wasuser) by entering the following command

     su - wasuser
     
     
     

   • Windows: (DB2) Open a DB2 command window on the WebSphere Commerce 6.0 machine.

   • (Oracle) Open a command prompt window.

2. Run the database premigration checker:

   (DB2)

   • AIX|Linux|Solaris:

     ./migratedb.sh -dbtype db2 -dbname dbname -dbuser dbuser [-dbpass dbuserpw] 
     -from previous_version -instanceName instance -precheck
     
     
     

   • Windows:

     migratedb.bat -dbtype db2 -dbname dbname -dbuser dbuser [-dbpass dbuserpw] 
     -from previous_version -instanceName instance -precheck
     
     
     

   (Oracle)

   ./migratedb.sh -dbtype oracle -dbname dbname -dbuser dbuser [-dbpass oraclepw] 
   -from previous_version -instanceName instance -hostname hostname
   -port port_number -precheck
   
   
   

   • Windows:

     migratedb.bat -dbtype oracle -dbname dbname -dbuser dbuser [-dbpass oraclepw]
     -from previous_version -instanceName instance -hostname hostname
     -port port_number -precheck
     
     
     

   • I5/OS|For a local database run

     migratedb.sh -dbtype os400 -dbname relationalDB -dbuser dbuser
     [-dbpass instancepwd]-from previous_version
     -instanceName instance -precheck
     
     
     

   • I5/OS|For a remote database run

     migratedb.sh -dbtype os400 -dbname serverName -dbuser dbuser
     [-dbpass instancepwd] -from previous_version
     -instanceName instance -hostname hostname -precheck -remoteDB true
     
     
     

   Where:

   serverName

   Represents the entry field defined in the relational database on the machine where the database resides. This directory can be queried on the WebSphere Commerce machine by running the WRKRDDIRE command.

   previous_version

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

   
   Notes:

   1. If you do not supply the database password on the command line, the migration script will prompt you to enter it in when you run it.

   2. For remote database migrations use the following values:

      • serverName - represents the entry field defined in the relational database on the machine where the database resides. This directory can be queried on the WebSphere Commerce machine by running the wrkrdbdire command.

      • -remoteDB true - required only for remote database migrations

      • AIX|Linux|Solaris|Windows:

        (DB2) The example assumes that your database schema name is the same as the database user ID. If it is not the same, use the -schema flag to specify the schema name.

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

   • I5/OS|

     WC60_userdir/logs/WCIM/instance/migratedbxx_yyyy.mm.dd_hh.mm.ss.log
     
     
     

   • AIX|Linux|Solaris:

     WC_installdir/logs/WCIM/instance/migratedbxx_yyyy.mm.dd_hh.mm.ss.log
     
     
     

   • Windows:

     WC_installdir\logs\WCIM\instance\migratedbxx_yyyy.mm.dd_hh.mm.ss.log
     
     
     

     Where xx is the previous version of WebSphere Commerce, either 55, 56, or 561.

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

   • (DB2)

     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.
     
     
     

   • (Oracle)

     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.
     
     
     

   • I5/OS:

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

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

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

7. Run the premigration checker again.

 

Related tasks

Migrate the WebSphere Commerce database using the migration script
Migrate the WebSphere Commerce database