Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Boopathi Balu (Boopathi@Balu)
BNP Paribas

BNP Paribas
FR
Boopathi@Balu Member since 2018 13 posts
BNP Paribas
Posted: Apr 11, 2019
Last activity: Apr 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

To see attachments, please log in.
Installation and Deployment

Posted: 5 years ago
Posted: 13 Apr 2019 8:23 EDT
Kevin Zheng (KevinZheng_GCS)
PEGA
Director, Technical Support
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.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice