pylastreservedid changed while crestoring the data
Hello,
While restoring an existing DB to a new environment the pylastreservedId value changed, I am not well versed with what this actually does, but is it possible that it may change as the DB restore was completed successfully? Although there were additional frameworks installed .
Attachement--(the value changed from 1001 to something else...)
Accepted Solution
Pegasystems Inc.
IN
Seems like it got commited on the day the restore happened looking at the commit date for the same. Thanks for putting your time into it.
Pegasystems Inc.
US
The screenshot shows the value for LI-. What is the value for LI- in the new environment? I am not quite sure what you did. You did a database backup from one environment and restored it in another? Did you copy both the rules and data schemas to the new environment and replace the contents of the existing rules and data schemas or did you do some kind of merge?
Pegasystems Inc.
IN
The new environment and the old env. both have the same data and rules , (as the DB of the new env. was dropped, and was restored to that of the old one successfully). Once that was done additional frameworks were installed on top of that. So the only difference b/w new and old environment should be those frameworks.
LI is the pxinstancename and pxobject class is Data-UniqueID from the table pegadata.pc_Data_uniqueid which stores the workobject ids, added the screenshot for the difference in that value for the 2 env.
Associated SR -> SR-B84322
Accepted Solution
Pegasystems Inc.
IN
Seems like it got commited on the day the restore happened looking at the commit date for the same. Thanks for putting your time into it.