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

Hofixes are not committing



After committed all hotfixes, the logs show successful committing but the hot fixes still show as uncommitted on the UI with Pega 7.2.

Error Messages

Not Applicable

Steps to Reproduce

Try to commit hotfixes with Pega 7.2.

Root Cause

A defect or configuration issue in the operating environment.

The getUniqueID functionality was changed which results in a longer string for HOTFIXORDER names, for example HOTFIXORDER-5021672004.

This value was too large for the pyUniqueID column in the pr_data_products table and thus when the hot fix was installed these values were truncated and do not match the corresponding data.


Perform the following local-change steps:

1. Increase the size of the column PYUNIQUEID to 16 or 40. Depends on the size of the value which needs to get inserted.

2. This query will get you a list of all of the rows that need to be updated.

SELECT pxinsname, pyuniqueid FROM PR_DATA_PRODUCTS WHERE pxinsname != PYUNIQUEID

For whatever rows where the pyUniqueID has been truncated and thus doesn’t match pxInsname an update of the row needs to be run to set pyUniqueId=pxInsName.

3. After updating and committed pr_data_products table rerun commit all hotfixes.

Suggest Edit

Published April 24, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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