Completing the development database migration

After you successfully migrate your development database, additional tasks are required to complete the database migration.

Before you begin

If your WebSphere Commerce node is using a remote database, catalog the remote database on the WebSphere Commerce node.

Procedure

  1. Update your SRCHCONF to contain the new search preprocess directory by running the following command:
    update SRCHCONF set CONFIG = replace(CONFIG, 'old_PreProcessdir', 'new_PreProcessdir');
    Where:
    old_PreProcessdir
    The preprocess directory of the version 7.0 search server.
    new_PreProcessdir
    The preprocess directory of the version 8.0 search server.
  2. DB2 Run the DB2 reorg command.
    1. Windows Open a DB2 command window.
    2. LinuxAIX Log on to the system by using the DB2 instance owner ID.
    3. Go to the WCDE_installdir\bin directory.
    4. Run the following command:
      Windows
      reorg.db2.bat db_name db_user db_password db_schema_user
      LinuxAIX
      ./reorg.db2.sh db_name db_user db_password db_schema_user
      db_name
      The name of the migrated WebSphere Commerce development database.
      db_user
      The name of the database user.
      db_password
      The password for your database user.
      db_schema_user
      The name of the database schema user.
  3. If you are migrating from WebSphere Commerce Version 7 Feature Pack 1, Feature Pack 2, Feature Pack 3, Feature Pack 4, Feature Pack 5, or Feature Pack 6, and you have configured workspaces and have already run the update workspaces schema script after migrating, run the following SQL statement in each workspace write schema:
    • Cloudscape:
      ALTER TABLE PAGELAYOUT ALTER COLUMN PAGELAYOUTTYPE_ID NULL;
    • DB2:
      ALTER TABLE PAGELAYOUT ALTER COLUMN PAGELAYOUTTYPE_ID DROP NOT NULL;
      
      CALL SYSPROC.ADMIN_CMD ('REORG TABLE PAGELAYOUT');
    • Oracle:
      ALTER TABLE PAGELAYOUT MODIFY PAGELAYOUTTYPE_ID NULL;

What to do next

  1. Run the updatedb command to apply the latest Fix Pack to your migrated database. For more information about updating the database, see updatedb utility.
  2. Migrate your custom assets.