Question

4
Replies
87
Views
Close popover
Jayantha Samarakoon (Jayantha)
Virtusa
Senior Systems Architect
Virtusa
LK
Jayantha Member since 2010 9 posts
Virtusa
Posted: October 14, 2020
Last activity: December 2, 2020

pc_work_social primary key violation in pega

We have more than one application, we do both migration upgrade, currently in the process of migration data AWS cloud to Pega cloud. We are getting primary key violation when we migrating data into pc_work_social since primary key of pc_work_social table (pzinskey) contains numbers with M- prefix. (Not contains class and timestamp) Both source and destination has same primary and different values for other columns. 

Eg. M-1 record contains both source and the target for pzinskey but other columns contain different values.

I wanted to know do we have any possible work around to keep both record in target.

Thanks

Pega Platform 8.4.1 System Administration Healthcare and Life Sciences Senior System Architect Upgrade