Question

5
Replies
478
Views
Aydin Toprak (topra)
PEGA
Senior System Architect
Pegasystems Inc.
NL
topra Member since 2016 19 posts
PEGA
Posted: March 19, 2019
Last activity: March 29, 2019
Posted: 19 Mar 2019 8:44 EDT
Last activity: 29 Mar 2019 13:56 EDT
Closed
Solved

Committing all uncommitted hotfixes

Hi,


I have two questions regarding uncommitted hotfixes on Pega.


On our production system, almost all our hotfixes are waiting on uncommitted hotfixes list. Those are not very few... cumulated over the years....


We would like commit them as we would like to use update managers full functionality to roll back hotfixes in some cases later on.


My first question is; do we have any risk to commit them and is this procedure required and DB back up before doing that ? We know that those fixes are already running but as this in production system we would like to be sure about it especially the issue, which I will detail below, we have.


the issue we have as follows;


We have installed a cumulative patch regarding a defect on our production system. The patch covered that problem but required a corporate wide SilverLigtht update which could not be done at that moment. As a result of this, we have removed the patch by deleting the rules one by one from DB.


At the moment, we have total number of 6-7 hotfixes on production system, those can be seen on uncommitted hotfixes list, but actually no rule related with them on the system.


Considering this exceptional issue, what happens If we commit them all at once ? We think that the list will clear up, and as there are no rules about that hotfixes, system will run as it is right now ... but we would like be sure about that.


Any help, idea and support will be appreciated.


Thank you


Regards


Hi,

I have two questions regarding uncommitted hotfixes on Pega.

On our production system, almost all our hotfixes are waiting on uncommitted hotfixes list. Those are not very few... cumulated over the years....

We would like commit them as we would like to use update managers full functionality to roll back hotfixes in some cases later on.

My first question is; do we have any risk to commit them and is this procedure required and DB back up before doing that ? We know that those fixes are already running but as this in production system we would like to be sure about it especially the issue, which I will detail below, we have.

the issue we have as follows;

We have installed a cumulative patch regarding a defect on our production system. The patch covered that problem but required a corporate wide SilverLigtht update which could not be done at that moment. As a result of this, we have removed the patch by deleting the rules one by one from DB.

At the moment, we have total number of 6-7 hotfixes on production system, those can be seen on uncommitted hotfixes list, but actually no rule related with them on the system.

Considering this exceptional issue, what happens If we commit them all at once ? We think that the list will clear up, and as there are no rules about that hotfixes, system will run as it is right now ... but we would like be sure about that.

Any help, idea and support will be appreciated.

Thank you

Regards

***Edited by Moderator Marissa to update platform capability tags;; add SR Details****

Pega Platform System Administration Support Case Exists
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.