IBM SG24-6320-00 Unsent messages, Order status, Catalog, Change the order status to S Shipped

6320ch_DEV_before_migration.fm Draft Document for Review July 28, 2004 7:33 pm

Important: Ensure that all connections to the database are terminated before continuing. Otherwise the changes performed by the script in this section may not take effect.

6.3.2 Unsent messages

If the development database contains any messages in the MSGSTORE table, these must be removed before migrating the database, as they cannot be handled by WebSphere Commerce V5.6.

As this is a development database, there is no reason to attempt to have these messages sent and they can safely be deleted.

The following SQL will clean the MSGSTORE table:

delete from MSGSTORE

6.3.3 Order status

Any orders in state C (Payment approved) will result in an extra allocation of the products in those orders from the inventory when the migrated instance is restarted.

As this is a development database, this may not be an issue. If it is a potential problem, we recommend that you do one of the following:

Delete the orders:

delete from order where status=’C’ delete from ordeitems where status=’C’

Change the order status to S (Shipped):

update order set status=’S’ where status=’C’ update ordeitems set status=’S’ where status=’C’

Change the order status to X (Cancelled):

update order set status=’X’ where status=’C’ update ordeitems set status=’X’ where status=’C’

6.3.4 Catalog

This sections describes the changes which needs to be applied for the catalog subsystem.

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