Related content:

Discussion

ORA-12899: value too large for column length while performing rules Upgrade (Step after rules migration).

Question

When is a branch too big?

Question

pxIndexPurpose Property Definition and Column Size Do Not Match

Discussion

ORA-12899: Value too large for column length while performing Rule Migration (Step before rules upgrade).

Discussion

Property-Set for pxObjClass is failing after upgrade to Pega7

Question

How to resolve a pyCommitError: Cannot write property to a decimal column

Question

ORA-12899: value too large for column

Question

pxIndexPurpose in List view query for join Declare Index

Discussion

Unable to check for obsolete database triggers error on upgraded environment after application server restart

Question

Partition key should be mapped to a Database table column in Data Set
Contact a Moderator

Discussion

1
Replies
187
Views
sudharsan Member since 2013 14 posts
PEGA
Posted: June 4, 2015
Last activity: April 6, 2018
Closed

pyCommiterror. Key property pxIndexPurpose in database too big for its column after upgrade

Hi, I'm getting a commit error after upgrade

pyCommitError:** The key property pxIndexPurpose in database PegaDATA, table PR_INDEX_MULTIACCOUNTS is too big for its column: column size:32, property size:39

...

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Low-Code App Development Upgrades
Close popover
Moderation Team has archived post
Posted: 5 years ago

pxIndexPurpose usually contains declare Index rule name. If the rule names are longer, this error occurs

Increase the pxIndexPurpose column size from 32 to 64 characters in the respective declare index table to resolve the issue.
Share this page LinkedIn
Copied!