Work Unique ID (pyLastReservedID) getting increased abruptly post upgrade to Pega 8.3
Hi All,
Recently our pega7.3 application got upgraded to pega8.3. It is based on pega cloud and postgres DB. Post upgrade our application is behaving abruptly. The uniqueID (instance of Data-UniqueID) is getting increasing abruptly. That means, if case id created with CC-100, the next case is creating as CC-1101. The pyLastReservedID is getting increased abruptly. Not sure, from where it is getting increased ? The issue is specifically happening after upgrade.
Please help if any has faced the same issue ?
Accepted Solution
Cognizant Technology Solutions
GB
We raised a SR to PegaSystems. And they have replied it as a feature of Pega 8.x, where in multi noaded system, the case id generation will split as per the nodes.
Pegasystems Inc.
US
Hi, please review below comments
As part of upgrade process, it's recommended not to install the samples of strategic applications.
Samples of Strategic Applications will have instances of PC_DATA_UNIQUEID, which will reset / modify the PC_DATA_UNIQUEID table column, pyLASTRESERVEDID hence causing an impact on the WO creation.
You will find the same explanation in SA-55277 https://community.pega.com/support/support-articles/pylastreservedid-column-reset-post-application-update
Hope this helps!
Cognizant Technology Solutions
GB
Thanks Tanie for your reply. But upon analysis, we found that the issue was not because of pyLastReservedID. The generateID activity which was modified in 8.3, is calling the below function-
((PegaDatabase) tools.getDatabase()).getUniqueID(tools.getParamValue("IDPrefix"), tools.getParamValue("IDSuffix"));
And this function is generating the ID not picking up values from pc_data_uniqueid table and this is a internal function, so we don't know how the function is working. So we are still in dark on this.
Pegasystems Inc.
US
Hi,
Activity generateID is in multiple classes. Which particular one are you comparing between Pega 7.3 and 8.3? Pl let me know and I can look into further within our in-house systems.
Thank you
Pegasystems Inc.
US
Hi there again,
Please review SA-60811 (https://community.pega.com/support/support-articles/pylastreservedid-counter-pcdatauniqueid-table-reset) and you may perform the suggested local change
Manually reset PYLASTRESERVEDID values in the PC_DATA_UNIQUEID table for a number of impacted object IDs to the correct values for the corresponding objects.
Hoping, this will resolve your issue!
Accepted Solution
Cognizant Technology Solutions
GB
We raised a SR to PegaSystems. And they have replied it as a feature of Pega 8.x, where in multi noaded system, the case id generation will split as per the nodes.