Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Upgrade to Pega 7.2 using runs for more than 21 hours



Upgrade to Pega 7.2 using runs for more than 21 hours.

Error Messages

[java] [ main] [ ] [ ] ( internal.util.MoveLog) INFO - Processed 1000 of 2325 (43.01%): 1000 committed, 0 skipped, 19 seconds remaining

<NO OUTPUT FOR 12 HOURS and no error>

[java] [ main] [ ] [ ] ( internal.util.MoveLog) INFO - Processed 1100 of 2325 (47.31%): 1100 committed, 0 skipped, 17 seconds remaining

Steps to Reproduce

  1. Upgrade PRPC 6.3 SP1 to Pega 7.2
  2. Run on an Oracle database from a UNIX environment.

Root Cause

A defect or configuration issue in the operating environment.

Oracle JDBC driver gathers entropy during upgrade or install while using UNIX. Oracle JDBC drivers use /dev/random by default. When running in an environment where there is not a lot of noise, the entropy pool eventually gets empty and the connection is reset. In some versions of the driver there are long hangs and then the connection restores. In other versions, SQLRecoverableException is observed and the connection is closed.


Use Oracle's suggested local-change to set the system property, 

Modify the setupDatabase.xml file to set the system property and resume the upgrade.


Published July 23, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us