6320ax02.fm

Draft Document for Review July 28, 2004 7:33 pm

3.Apply patch for migrateencryptedinfo.bat into Utilities.jar, refer to

Chapter 11, “Migrating WebSphere Commerce components” on page 201 for more details on why this patch is applied

4.Call WebSphere Commerce V5.6 encrypted data migration script migrateencryptedinfo.bat to migrate the encrypted data

5.Execute choosemc.sql to assign the master catalog

Database post migration SQL script

The SQL file executes the final changes needed on the database to finish the database migration.

The post.migration.sql file will perform the following tasks:

1.Correct the index errors introduced by migratedb.bat

2.Remove records with non-encrypted values starting with space. Refer to Chapter 11, “Migrating WebSphere Commerce components” on page 201 for more details on this.

The content of the post.migration.sql file:

Example: C-5 Content of post.migration.sql file

-- CORRECT INDEX ERRORS DURING DB MIGRATION

create index I0000511 on campaign ( storeent_id asc);

drop index I0000539;

create index I0000539 on contract ( member_id asc);

create index I0000588 on initiative ( storeent_id asc);

drop index I0000824;

create index I0000824 on userpvcdev ( users_id asc);

--DELETE ORDPAYINFO VALUES THAT STARTS WITH ' ' SO IT IS NOT ASSUMED TO BE A ENCRYPTED VALUE delete from ordpayinfo where value like ' %';

266Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide

Page 284
Image 284
IBM SG24-6320-00 manual Database post migration SQL script, Example C-5 Content of post.migration.sql file