IBM SG24-6320-00 manual Erroneous data in encrypted fields

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

Once the migration has completed successfully, you must recreate your foreign key relationships manually. If possible, while you are working on the migration, it is a good idea if a member or your team starts create a script that will recreate the references once the migration has completed. They will need to refer to the online help to check that the data model changes do not impact the referential integrity or appropriateness of the custom tables. The online help can be found at:

http://publib.boulder.ibm.com/infocenter/wc56help/index.jsp

6.3.8 Erroneous data in encrypted fields

Before migrating encrypted data, you should check the following fields in

Table 6-6for data that has a leading space and is unencrypted.

In WebSphere Commerce, in a field that may be encrypted, such as the field listed in Table 6-6,the presence of a leading space indicates that the field contains encrypted data.

If any of your unencrypted data has a leading space, due to a user entering this in the store for example, the migration tool will misinterpret this and try to decrypt the value, causing an error. The tables and fields to check are shown in

Table 6-6.For further information about the behavior of the encrypted data migration script, please refer to Appendix C, “Migration scripts” on page 255.

Table 6-6 Tables and fields to check for erroneous leading spaces

Table	Columns to	Notes
	check
ORDPAYINFO	VALUE	Credit Card related information
ORDPAYMTHD	PAYDEVICE	Credit card related information

Chapter 6. Pre-migration steps 109