Migrating the WebSphere Commerce database by using command line

Using command line, you can complete the database check and migration.

Before you begin

  1. Run the database premigration checker.
  2. Ensure that you eliminate all items that are flagged by the database premigration checker.

About this task

It is recommended to use the WebSphere Commerce Migration wizard instead of the WCIM migration scripts to reduce the probability of errors.


  1. Open a command line.
  2. LinuxAIX Switch to the WebSphere Application Server user ID, also known as the wasuser, by running the following command:
    su - wasuser
    Note: This user must have authority to access the files in the WC_installdir directory.
  3. Go to the WC_installdir/bin directory.
  4. Run the database migration command:
    • LinuxAIX./wcim_ant.sh -tier db -action migrate -from 70 -instanceName instance_name -isStaging true | false [-defaultTablespace yes | no] [-logLevel Error | Warning | Info | Verbose | Debug]
    • Windowswcim_ant.bat -tier db -action migrate -from 70 -instanceName instance_name -isStaging true | false [-defaultTablespace yes | no] [-logLevel Error | Warning | Info | Verbose | Debug]
    • For IBM i OS operating system./wcim_ant.sh -tier db -action migrate -from 70 -instanceName instance_name -isStaging true | false [-defaultTablespace yes | no] [-logLevel Error | Warning | Info | Verbose | Debug]
    Specifies the tier of your WebSphere Commerce topology that you are migrating. The only available option is db.
    Specifies the action to perform when the command runs. The supported actions are as follows:
    Runs the database premigration checker to check the status of your database before you migrate it. Run the database premigration checker before you migrate the database.
    Migrates the database to WebSphere Commerce Version 8.0.
    Specifies the version of the WebSphere Commerce database from which you are migrating. The only available option is 70.
    Is the name of your WebSphere Commerce Version 7.0 instance.
    Specifies whether you are migrating a staging database. Available options are true or false.
    DB2Optional: Specifies whether to use a default table space for your database.
    Sets a default table space.
    A non-default table space can be used.
    Optional: Specifies the amount of information about the database tier migration that is logged. The valid log levels are as follows:
    Only error messages are logged.
    All warning and error messages are logged.
    All error, warning, and event messages are logged.
    All errors, events, and other information are logged, including all SQL statement information. It requires 1-2 MB of storage for most migrations. Verbose is set by default.
    Similar to the Verbose option, but includes some additional debug information. This value is helpful if you encounter errors and need to debug them. It requires 1-2 MB of storage for most migrations.
    Note: The migration script prompts you to enter the database password when you run it.
    The following example illustrates how to run database migration script and the prompts that follow:
    ./wcim_ant.sh -tier db -action migrate -from 70 -instanceName demo
       Database type? [ db2 ] (cloudscape,db2,os400,oracle,)
       Remote database? [ false ] (true,false,)
       Database name?
       Database user?
       Database user password?
       Database server port?
       Is this a test run? [ Yes ] (Yes,No,)
       Is the database backup completed? [ Yes ] (Yes,No,)
       Is the database restore completed? [ Yes ] (Yes,No,)
    When the database migration completes successfully, you see the following message:
    INFO:   WCIM has completed the job(s) successfully.
  5. If the database migration fails, review and correct any errors that are found in the following log file: WC_installdir\logs\WCIM\wcim.server.yyyy.mm.dd_hh.mm.ss.log.
    Note: A database restore is not necessary before you rerun the database migration.
  6. After the migration completes successfully, review any warnings in the WC_installdir\logs\WCIM\wcim.server.yyyy.mm.dd_hh.mm.ss.log, and then determine whether any actions are needed.

What to do next

  1. Updating the SITE table on the migrated database
  2. Completing the database migration