Question
Allianz
DE
Last activity: 4 Mar 2016 9:06 EST
Roll back single hotfixes
Hello,
we are using Pega 7.1.7. With the functionality "Rollback All" it's possible to roll back all installed Hot Fixes. When having installed more than one Hot Fixes that are not committed yet, is it possible to roll back only a single Hot Fix? In our case, we have installed 2 Hot Fixes but only want to roll back a single one and not all. Is that somehow possible?
Thx a lot.
Regards
Virtusa Global IT Services Company
AU
Pegasystems Inc.
US
The process for installing hot fixes should be to install, test, and then either rollback or commit. You should not be keeping hot fixes in an uncommitted state for longer than testing is needed and you should not be installing new hot fixes on top of uncommitted ones for just this reason. Since you only have 2 your best option would be to rollback all and then just install, test, and commit the one that you want.
Pegasystems Inc.
US
Good point Celeste.
Additionally, if you have installed a DL item with multiple hotfixes, you should not be attempting to rollback some of them. This is due to the possibly complicated inter-dependencies present in many DL items with multiple hotfixes. Allowing this would result in an unsupported condition with unpredictable results!
Generally, prior to installing a new DL item, you should seriously consider committing any uncommitted hotfixes, provided your team has tested them sufficiently in your application. There are circumstances that that isn't needed, but then you will have to rollback or commit all the uncommitted hotfixes as a group. In other circumstances you may wish to delay installing a DL until testing can be completed.
Pegasystems Inc.
IN
Hi
The activity which is responsible to rollback the uncommited hfix is pzCallRollBackAllHotFixes and it is a final rule. So I dont think it is possible to rollback only one HFIX.
Other than restoring database , one more option could be to rollback all and then install the required HFIX again or commit the required hfix and then perform rollback.
I also think that this can be taken up as an enhancement request so that our product management team can review it and take further call about implementing this in the product .
Rules Cube Inc.
CA
i have a question here.. prior to rollback some work objects are in flight and if we go for db backup to restore hotfixes. How to retain those new work objects ?
THanks
Venkatesh G
Pegasystems
US
If you're using the rollback feature of the update manager, I don't believe it will rollback the work, just the hot fixes.
If you're talking about a more general db restore, then yes, if you are not splitting your schema between work and rules, then the db restore would lose recent work. /Eric
Rules Cube Inc.
CA
Thank you for your reply Eric.. So do we have any way to save work and do db restore..?
Thanks
Venkatesh G
Pegasystems
US
Easiest would be to have split schema so that if you do a db restore to last week on the rules db, you wouldn't lose the last week's worth of work too.
However, I recall there is a backup-work wizard that packages the work on a zip, optionally deleting the work as well (it may be called the purge work wizard) , so if you don't have split schema you could test the following:
1) Back up db. Install hot fix.
2) Discover that hot fix isn't working properly after you "committed" it on update manager.
3) Use backup-work wizard to save work on a zip. Restore db. Restore work from the zip.
/Eric
Hi Martin,
DB rollback is one of the solution for this, since we would be taking DB Backup for each and every installation.
Thanks