Question
Nordea
SE
Last activity: 19 Jul 2019 4:27 EDT
Pega Upgrade Time
Hi,
We recently upgraded Pega from 7.3.1 to 8.2.1 in two of our lower environments SIT & BAT. The upgrade was done via in-place manner. We observed that SIT took 130 minutes to upgrade whereas BAT took 330 minutes to do the same. Both the environments have same Rule Base & approx same Data. I was just curios what are the other factors we should check which may impact upgrade time because the downtime would play crucial role during production upgrade and we have to plan it accordingly.
Pegasystems Inc.
IN
Hi,
Did you compare both environment's log.You can check the timestamp between two steps to find out which step took more time.
Thanks,
Abhinav
Nordea
SE
Yes, I compared I could see there are more rows for BAT but I don't think those entries should be taking double time. Most of the error reported in SIT log can be seen in BAT log as well. the only extra error I could see in BAT multiple times is shown below but not sure if that could be the root cause because that exception did not cause any timeout :--
[java] DatabaseException caused by prior exception: java.sql.SQLException: HikariDataSource HikariDataSource (HikariPool-1) has been closed - 148087
Attached are the upgrade logs for both the environment
Pegasystems Inc.
IN
Hi Anand,
Thanks for the information.Please let me know what is HikariDataSource.I believe that is related to an external database.Why this connection is being closed.Your application DBA can help you more.Please try to rectify it.It will resolve your issue.
Thanks,
Abhinav