Troubleshooting: Running the database tier migration script with the precheck option
Pre-checking the database migration might reveal problems with database column lengths.
Problem
When you run the
database tier migration
script with the precheck option, you receive an error
message indicating that the length of a column in your database has
changed in WebSphere Commerce Version 7.0.
Solution
The lengths of the following columns have changed in WebSphere Commerce Version 7.0. To ensure that you do not lose any data contained in these columns during the migration process, make sure that your data in these columns does not exceed the new length for the column, prior to data migration. For example, ensure that MBRGRP.DESCRIPTION is not greater than 512 characters. If the existing data in the columns exceeds the new length, it will be flagged by the database preparation script.
Modify the lengths according to the following
table:
| Table.Column | Previous version of WebSphere Commerce | WebSphere Commerce, Version 7.0 |
|---|---|---|
| CATGRPDESC.NOTE | LONG VARCHAR | VARCHAR(4000) |
Modify
the lengths according to the following table:
| Table.Column | Previous version of WebSphere Commerce | WebSphere Commerce, Version 7.0 |
|---|---|---|
| ACRELGRP.CONDITIONS | VARCHAR2(4000) | VARCHAR2 (2500) |