Completing the IBM Websphere Commerce Version 8 offline database migration

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

Procedure

Update your SITE table by running the following two commands with appropriate MOD and FIXPACK values.

delete from site where COMPNAME not IN ('BASE');

update SITE set VERSION = 9, MOD=0, FIXPACK=0 where COMPNAME IN ('BASE');

Update your SRCHCONF to contain the new HCL 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 IBM Websphere Commerce Version 8 Search server.
new_PreProcessdir: The preprocess directory of the HCL Commerce Version 9 Search server.

For example,

update SRCHCONF set CONFIG = replace(CONFIG,'WC_eardir/instances/demo/search/pre-processConfig/MC_10001/DB2','/v3/db2/CatalogEntry') WHERE indextype='CatalogEntry';
update SRCHCONF set CONFIG = replace(CONFIG,'WC_eardir/instances/demo/search/pre-processConfig/MC_10001/DB2/CatalogGroup','/v3/db2/CatalogGroup') WHERE indextype='CatalogGroup';

Update your SRCHCONF tables to contain the new search web server host name by running the following command:
```
update SRCHCONF set CONFIG = replace(CONFIG, 'old_hostname', 'new_hostname');
```
Where:

old_hostname

The fully qualified host name of the IBM Websphere Commerce Version 8 Search server.

new_hostname

The fully qualified host name of the HCL Commerce Version 9 Search server.
If you customized any searchable attributes in IBM Websphere Commerce Version 8 and plan to use them in HCL Commerce Version 9, you must update the KEYS table for the SRCHATTR table.
1. Connect to your 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 HCL Commerce Version 9 server.
When you set up your HCL Commerce Version 9 environment, you specified an spiuser user password. Now that your database is migrated from a previous version, your spiuser user password might be inconsistent.
1. Set the spiuser password in your Docker images.
2. Update the account policy for the spiuser user.
  Run the following SQL.
```
UPDATE USERREG SET PLCYACCT_ID = NULL WHERE logonid = 'spiuser';
```
Run the updatedb command from your utility docker.

What to do next

Perform all necessary testing of your migrated custom assets with the migrated database.