Support Article
Long value in Index-.pxIndexPurpose property cause pyCommitError
SA-1608
Summary
While creating a work object, user experienced "pyCommitError" in the recently upgraded Pega 7.1.6 setup.
Error Messages
"Please correct the errors indicated and try again.
Errors:
pyCommitError:** The key property pxIndexPurpose in database PegaDATA, table pr_index is too big for its column; column size: 32, property size: 36, property value: Index_HRCRiskRating_CustomerTypeRisk, instance class: Index-<Org>-Data-GSCM-RiskRating, trying to run SQL: insert into PEGA7_FCCM_DEV.pr_index (PXCREATEDATETIME , PXCREATEOPERATOR , PXCREATEOPNAME , PXCREATESYSTEMID , PXINDEXCOUNT , PXINDEXPURPOSE , PXINSINDEXEDCLASS , PXINSINDEXEDKEY , PXINSNAME , PXOBJCLASS , PXPRIVILEGECLASS , PXPRIVILEGENAME , PXUPDATEDATETIME , PXUPDATEOPERATOR , PXUPDATEOPNAME , PXUPDATESYSTEMID , PYLABEL , pzInsKey , pzPVStream) values (? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?)"
Steps to Reproduce
1. Create a Work Object.
2. Set the pxIndexPurpose property for Index- class objects to a value with > 32 characters.
3. Save the object/record to the database and pyCommitError will manifest on the screen and this does not allow user navigate to the next screen.
Root Cause
Column size of PXINDEXPURPOSE in the table PR_INDEX was 32 bytes. When user tries to insert value exceeds 32 bytes in this column, pyCommitError issue manifests.
Resolution
As a local-change, user has increased the column size "PXINDEXPURPOSE" in the table PR_INDEX from 32 to 64 bytes.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.