Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Issues while running migrate script for split schema upgrade

SA-20776

Summary



During an upgrade to Pega 7.1.9 from PRPC 6.3, the migrate.sh script fails while moving rules from the existing schema to a newly created rules schema. 


Error Messages



null
at com.pega.pegarules.util.deploy.PegaBulkMover.dumpDatabaseTable(PegaBulkMover.java:720)
at com.pega.pegarules.util.deploy.PegaBulkMover.process(PegaBulkMover.java:579)
at com.pega.pegarules.util.deploy.PegaBulkMover.main(PegaBulkMover.java:222)

PegaBulkMover:: SQLException querying Database on column index 123
at com.pega.pegarules.util.deploy.PegaBulkMover.dumpDatabaseTable(PegaBulkMover.java:823)
at com.pega.pegarules.util.deploy.PegaBulkMover.process(PegaBulkMover.java:579)
at com.pega.pegarules.util.deploy.PegaBulkMover.main(PegaBulkMover.java:222)


 


Steps to Reproduce



Run migrate.sh to perform bulk move actions.
 


Root Cause



A defect or configuration issue in the operating environment.

There were several records in the pr4_base table with a null value for the pzPVStream column (BLOB column).

This is data corruption as there should never be records in this table with no BLOB content.


Resolution



The above mentioned records must be deleted manually before the migration can proceed.
 
 

Published March 12, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us