Filter
Top Products
Appendix C. Migration scripts 257
Draft Document for Review July 28, 2004 7:33 pm 6320ax02.fm
This file controls the sequence of execution of various SQL files, in addition to
other activities. This provides fine grain control over how migration should
proceed. Here are some examples of the usefulness of this approach.
Some of the column lengths have decreased in the WebSphere Commerce V5.6
schema when compared to the column lengths in WebSphere Commerce Suite
V5.1. However, if you have data that occupies more space than allowed by
column length in WebSphere Commerce V5.6 then the data migration from
WebSphere Commerce Suite V5.1 schema to WebSphere Commerce V5.6
schema should fail. It is highly recommended that you re-evaluate your need to
have larger column length and thus staying with standard and supported
WebSphere Commerce V5.6 schema. However, if you must have the same
column length as defined in WebSphere Commerce Suite V5.1 schema then you
must change the behavior of one of the SQL files mentioned in this configuration
file. Both the standard output and the migration log file specifies the command it
is currently executing, this corresponds to, say, the dataMigrationCommand or
command XML tag as mentioned in this configuration file. When the data migration
discussed above fails you would notice that it was executing the
wcs.schema.recreate.tables.sql file in the following directory:
WC56_install_dir/schema/migration/51
You could edit this file to re-apply the same setting as in WebSphere Commerce
Suite V5.1.
The other obvious benefit of this execution behavior is that once you know that a
given step is taking a long time to execute, you could examine the corresponding
SQL statements and tune your database, e.g. if you are running out of bufferpool
or log file space then you could pin-point the exact large table of your database
causing this behavior and tune your database accordingly.
migrateEncryptedInfo.bat behavior
This script reads all the rows of a given table and then processes and commits a
subset of rows at a time. Note that the instance must be migrated prior to running
this script as it needs the migrated instance.xml file, in addition to certain other
files.
Internally, this script calls the MKChangeApp command twice with different
parameters and config files:
1. The first invocation uses the config file CCInfoDBUpdate.dbtype.txt, which
defines the following two action items:
a. System Key to currentKey migration: Prior to WebSphere Commerce
Suite V5.1.1.2 the merchant key was not used to encrypt credit card data,