Question

1
Replies
36
Views
 Boopathi Balu (Boopathi@Balu)
BNP Paribas

BNP Paribas
FR
Boopathi@Balu Member since 2018 13 posts
BNP Paribas
Posted: April 11, 2019
Last activity: April 13, 2019
Posted: 11 Apr 2019 5:48 EDT
Last activity: 13 Apr 2019 8:23 EDT
Closed

Committing Hot-Fix took more time than expected

Hello All,

Currently, we are using Pega 7.2.2. In production, we 114 hot-fixes were not committed & we decide to commit those hot fix. we did the same activity in Pre-Prod & it took 40 mins to complete all the hot fixes. But, It took 4 hours to complete. There were no exception / errors in logs.

If any one knows reason behind this delay, kindly share. Thanks. I have updated the list of hot-fix committed.

** Even after 4 hours, it doesn't reflected in the "Hot fix manager" screen. It's reflected only after the new hot fix installation.

Regards

Boopathi Balu

System Administration Installation and Deployment
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.
Posted: 2 years ago
Posted: 13 Apr 2019 8:23 EDT
Kevin Zheng (KevinZheng_GCS)
PEGA
Director, Software Solutions Engineering
Pegasystems Inc.
US

I would first check your PegaRules/PegaAlert logs and database AWR report (if Oracle) during that period. Is your Pre-Prod and Prod database sizes are similar or very different? Without data, it would be all speculation. Create a SR for Pega GCS to investigate if so desired.