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

HotFix not committing

SA-31742

Summary



The user put committed hotfixes in their QA environment. The log reports that the hotfixes are committing. However, one hotfix does not commit.

Error Messages



2016-12-05 13:21:28,985 [ WebContainer : 6] [TABTHREAD0] [ PegaRULES:07.10] (l.util.InstalledHotFixMgmtImpl) INFO |10.17
7.209.144  - Committing archive HFIX-29097
2016-12-05 13:21:28,988 [ WebContainer : 6] [TABTHREAD0] [ PegaRULES:07.10] (l.util.InstalledHotFixMgmtImpl) INFO |10.17
7.209.144  - Committing archive HFIX-29800
2016-12-05 13:21:28,990 [ WebContainer : 6] [TABTHREAD0] [ PegaRULES:07.10] (l.util.InstalledHotFixMgmtImpl) INFO |10.17
7.209.144  - Committing archive HFIX-29041


Steps to Reproduce



Commit the uncommitted hotfixes


Root Cause



A defect or configuration issue in the operating environment:


1. From the pr_data_products table, following entries have been observed for the UNCOMITTED hotfixes:

    
    

2. The value in the PYUNIQUEID also gets inserted into the PXINSNAME column.
3. In user environment the size of PYUNIQUEID is 20.
4. However the values in PXINSNAME for UNCOMMITTED rows is more than 20 characters.
5. This is the root cause of the problem, the column PYUNIQUEID size is not enough to store the input value.


Resolution



Perform the following local-change:

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

2. Update the rows marked in red for example:

    update pr_data_products.PYUNIQUEID = 'HOTFIXORDER-5021672004' where pr_data_products.PXINSNAME = 'HOTFIXORDER- 5021672004';

3. Perform setp 2 for all the rows with status as UNCOMMITTED.

4. Run the DB COMMIT command. Make sure the values got updated and verify entries in PYUNIQUEID matches to the values in the corresponding PXINSNAME column.

5. Thereafter restart the JVM and commit the hotfixes from update manager page.

 

Published January 3, 2017 - 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