PRPC v5.4 to PRPC v7.1.8: Rules migration is failing while loading the records to new rules schema
As a part of the rules migration, generated the DDL by configuring the migrateSystem.properties file and executed the DDL on new rules schema. We see that all the rules tables dump successfully placed in the bulk mover directory. But while loading the database records from the bulk mover to new rules schema, migration script is failing.
Database: DB2 LUW v9.7
App Server: WebSphere 126.96.36.199
Snippet of migrateSystem.properties file:
#The directory where output from the bulk mover will be stored. This directory will be cleared when pega.bulkmover.unload.db is run.
#This property must be set if either pega.bulkmover.unload.db or pega.bulkmover.load.db is set to true.
#The location where a temporary directory will be created for use by the migrate system utilities.
######## The operations to be run by the utility, they will only be run if the property is set to true.
#Set to true if migrating before an upgrade. If true admin table(s) required
#for an upgrade will be migrated with the rules tables.
#Generate an xml document containing the definitions of tables in the source system. It will be found in the schema directory of the
#Create ddl from the generated xml document. This ddl can be used to create copies of rule tables found on the source system.
#Apply the generated clone ddl to the target system.
#Unload the rows from the rules tables on the source system into the pega.bulkmover.directory.
#Load the rows onto the target system from the pega.bulkmover.directory.
### The following operations should only be run when migrating upgraded rules
#Generate the rules schema objects (views, triggers, procedures, functions). The objects will be created in the pega.target.rules.schema
#but will contain references to the pega.target.data.schema where appropriate.
#Apply the rules schema objects (views, triggers, procedures, functions) to pega.target.rules.schema.