Migrating the WebSphere Commerce Developer database by using the command line

You can check and migrate your database by using the command line to complete the premigration check and the migration on your WebSphere Commerce development database. However, it is recommended to use the Migration wizard.

About this task

Before you migrate the development database, run the premigration check to show any issues with the database that might cause errors during the migration. Correct any issues to ensure that your database migration completes successfully.

Procedure

  1. Run the premigration database check.
    1. Open a command prompt.
    2. Go to the WCDE_installdir\bin directory.
    3. Check the database by running the following command:
      • wcim_ant.bat -tier db -action check -from 70 [-defaultTablespace yes | no] [-logLevel Error | Warning | Info | Verbose | Debug]
      Where:
      tier
      Specifies the tier of your WebSphere Commerce topology that you are migrating. The only available option is db.
      action
      Specifies the action to perform when the command runs. The supported actions are as follows:
      check
      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.
      migrate
      Migrates the database to WebSphere Commerce Version 8.0.
      from
      Specifies the version of the WebSphere Commerce database from which you are migrating. The only available option is 70.
      DB2defaultTablespace
      DB2Optional: Specifies whether to use a default table space for your database.
      yes
      Sets a default table space.
      no
      A non-default table space can be used. You are prompted to pass a table space name later in the migration.
      logLevel
      Optional: Specifies the amount of information about the database tier migration that is logged. The valid log levels are as follows:
      Error
      Only error messages are logged.
      Warning
      All warning and error messages are logged.
      Info
      All error, warning, and event messages are logged.
      Verbose
      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.
      Debug
      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.
      The following snippet is an example of the database check interactions: 
      W:\WCDE_ENT80\bin>wcim_ant.bat -tier db -action check -from 70 -logLevel Verbose
Database type? [ db2 ] (cloudscape,db2,os400,oracle,)
cloudscape

Database name?
W:/WCDE_ENT80/db/mall2

Is the database backup completed? [ Yes ] (Yes,No,)
Yes

Is the database restore completed? [ Yes ] (Yes,No,)
Yes
      When the check completes successfully, you see the following message: 
      INFO:   WCIM has completed the job(s) successfully.
    4. If the database check fails, review the following log file: WCDE_installdir\logs\WCIM\wcim.server.yyyy.mm.dd_hh.mm.ss.log. Address the failure message, and rerun the database check.
  2. Migrate the database.
    1. Open a new command prompt, or use the same prompt that you used to run the database check.
    2. Migrate the database by running the following command:
      wcim_ant.bat -tier db -action migrate -from 70 [-defaultTablespace yes | no] [-logLevel Error | Warning | Info | Verbose | Debug]
      Where:
      tier
      Specifies the tier of your WebSphere Commerce topology that you are migrating. The only available option is db.
      action
      Specifies the action to perform when the command runs. The supported actions are as follows:
      check
      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.
      migrate
      Migrates the database to WebSphere Commerce Version 8.0.
      from
      Specifies the version of the WebSphere Commerce database from which you are migrating. The only available option is 70.
      DB2defaultTablespace
      DB2Optional: Specifies whether to use a default table space for your database.
      yes
      Sets a default table space.
      no
      A non-default table space can be used. You are prompted to pass a table space name later in the migration.
      logLevel
      Optional: Specifies the amount of information about the database tier migration that is logged. The valid log levels are as follows:
      Error
      Only error messages are logged.
      Warning
      All warning and error messages are logged.
      Info
      All error, warning, and event messages are logged.
      Verbose
      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.
      Debug
      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.
      The following snippet is an example of how to run the database migration check: 
      W:\WCDE_ENT80\bin>wcim_ant.bat -tier db -action migrate -from 70 -logLevel Verbose
Database type? [ db2 ] (cloudscape,db2,os400,oracle,)
cloudscape

Database name?
W:/WCDE_ENT80/db/mall2

Is the database backup completed? [ Yes ] (Yes,No,)
Yes

Is the database restore completed? [ Yes ] (Yes,No,)
Yes
      When the database migration completes successfully, you see the following message: 
      INFO:   WCIM has completed the job(s) successfully.
    3. If the database migration fails, review and correct any errors that might be found in the following log file: WCDE_installdir\logs\WCIM\wcim.server.yyyy.mm.dd_hh.mm.ss.log.
      Note: If your database migration fails while it enables content versioning, you need to restore the database before you rerun the migration. To determine whether the migration failed while it enabled content versioning, review the WCDE_installdir\logs\WCIM\wcim.server.yyyy.mm.dd_hh.mm.ss.log file. Check the log to see whether the failure occurs while it runs the createVersion task from the configureContentVersionComponent.xml file.
    4. After the migration completes successfully, review any warnings in the WCDE_installdir\logs\WCIM\wcim.server.yyyy.mm.dd_hh.mm.ss.log, and then determine whether any actions are needed.

What to do next