Discussion
Migration failed due to blob size mismatch
While importing the rule records as part of the migration process, the build fails. This is due to a mismatch in the column sizes in existing and new schema in pzpvstream column. What is the solution ?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
## Use Case ##
In 5.X OR 6.X there was an unexposed OOTB property in the blob of pc_work_xyz
7.1.8 has this property exposed in pc_work table.
Upgrade scripts will not take care of my pc_work_xyz table; what should I do now ?
As such I am not aware of any such use case; has pega systems handled a similar use case ?
If so then please let us know about it.
PRPC Upgrade process does NOT manipulate any custom work table as part of upgrade. Your work tables will continue to work as-is post upgrade.
All the changes done to OOTB work tables are optional unless explicitly specified in the upgrade guide of customer service or other industry solutions.
This can be due to customization in pzpvstream column.
This issue can be resolved by reapplying all the customizations done in the PRPC database before loading the actual data. To achieve this, the migration should be carried out as a multi-step process.
1. Create and apply DDLs
2. Reapply customizations done on these tables in the new schema
3. Verify exact match of tables between the two schemas
4. Unload and load the tables (using PRPC bulkmover or db2 tools)
This can be achieved by setting appropriate properties of migrate.sh to true/false and running migration sequentially