Question
Coforge DPA UK Ltd.
IN
Last activity: 27 Nov 2017 9:11 EST
Pega Marketing Program Run sequence number
Hi,
As the marketing campaign instances (work objects of PegaMKT-Work) are moved from Dev to Live environment, the campaign is not able to start if the PR(program run)ID is already present (e.g. PR-1324). When I try to reschedule again it is trying to create PR-1325, if 1325 is also present campaign is not starting, if I retry to reschedule again, it is creating PR-1326. Like this way until the number which is not generated occurs, the campaign is not starting.
How can I change the sequence number of PegaMKT-Work objects?
Thanks,
Durgarao J.
***Edited by Moderator Marissa to update categories***
Accepted Solution
Coforge DPA UK Ltd.
IN
The issue is identified. Below are the details of it:
When the campaign instances are moved from lower environments to live, the reserved IDs for PR(program run) were also moved(instances of Data-UniqueID can show the current reserved ID for PR-). When the campaign is trying to run, it is trying to create a next sequence number, if it is already there, campaign was not starting.
Example: current sequence number is PR-1433, the next run tries to create PR-1434, but if 1434 is already present due to earlier runs in live, campaign is stuck and not starting.
Solution applied:
we have modified the LastreservedID in APP_PEGA_DATA.pc_data_uniqueid table to a different number(here we changed to 1700 for safer side. so next runs will start as 1701,1702,1703 and so on) after checking the all the existing PR sequence numbers from coveredins keys of particular campaign instances .
Pegasystems Inc.
IN
Hi Durga,
What is PegaMarketing framework version used at your end?
Usually it is not recommended to migrate programs from one environment to other .
Regards
Sibani Saidarsini
Accepted Solution
Coforge DPA UK Ltd.
IN
The issue is identified. Below are the details of it:
When the campaign instances are moved from lower environments to live, the reserved IDs for PR(program run) were also moved(instances of Data-UniqueID can show the current reserved ID for PR-). When the campaign is trying to run, it is trying to create a next sequence number, if it is already there, campaign was not starting.
Example: current sequence number is PR-1433, the next run tries to create PR-1434, but if 1434 is already present due to earlier runs in live, campaign is stuck and not starting.
Solution applied:
we have modified the LastreservedID in APP_PEGA_DATA.pc_data_uniqueid table to a different number(here we changed to 1700 for safer side. so next runs will start as 1701,1702,1703 and so on) after checking the all the existing PR sequence numbers from coveredins keys of particular campaign instances .