Completing the WebSphere Commerce Version 8 offline database migration

After you successfully migrate the database, complete the final database migration tasks.


Procedure

  1. Update your SITE table by running the following two commands. 

      delete from site where COMPNAME not IN ('BASE', 'management-center');
update SITE set VERSION = 9, MOD=0, FIXPACK=0 where COMPNAME IN ('BASE', 'management-center');

  2. Update your SRCHCONF to contain the new WebSphere Commerce Version 9 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 WebSphere Commerce Version 8 search server.

      new_PreProcessdir
      The preprocess directory of the WebSphere Commerce Version 9 search server.

  3. Update your SRCHCONFEXT tables to contain the new search web server host name. 

      update SRCHCONFEXT set CONFIG = replace(CONFIG, 'old_hostname', 'new_hostname');

    Where:

      old_hostname
      The fully qualified host name of the WebSphere Commerce Version 8 search web server.

      new_hostname
      The fully qualified host name of the WebSphere Commerce Version 9 search web server.

  4. If you customized any searchable attributes in WebSphere Commerce Version 8 and plan to use them in WebSphere Commerce Version 9, we must update KEYS table for the SRCHATTR table.

    1. Connect to the database.

    2. Run the following SQL command: 

        update keys set counter = case when (select max(srchattr_id) from srchattr) > 
counter then (select max(srchattr_id) from srchattr) else counter end where tablename = 'srchattr';

    3. Restart the WebSphere Commerce Version 9 server.

  5. When you set up the WebSphere Commerce Version 9 environment, you specified an SPIUSER password. Now that the database is migrated from a previous version, your SPIUSER password might be inconsistent. By using the Organization Administration Console, update your SPIUSER password to the same value that you set when creatingd the environment.

    1. Log on to the Organization Administration Console.

    2. Click Access Management > Find Users.

    3. In the Logon ID field, enter spiuser, then click Find.

    4. Select the SPIUSER from the search results, then click Change.

    5. Update the SPIUSER password to the same value that we used when you set up the environment.

    6. Click OK.

  6. Run the updatedb command from your utility docker.


What to do next