pxIndexPurpose Property Definition and Column Size Do Not Match
Hi i have issue with pxIndexPurpose Column size too small.
i tried the resolution from this link and increased it from our oracle database column .
But when i check the column size on system database from pega designer studio, and still detect the column size as 32 byte .
do i need to run something in order to sync the database size of pxIndexPurpose Column ?
Accepted Solution
asuransi sinarmas
ID
Hi, Thx for your response .
i am not increasing the size of property max length.
i am increasing the size of the column size directly from DB because after optimize property for reporting,
by default pega create table pr_index_(CLASS NAME)
on this table they have column called pxIndexPurpose created with 32 byte size.(can't sett the default because it was create automatically by pega when we optimize property for reporting)
i need to change it to 64 byte because when i try to save on my property that was optimize for reporting i get this error : The key property pxIndexPurpose in database PegaDATA, table pr_Index_ASM_FW_GISFW_Data_Pay is too big for its column; column size: 32, property size: 45, property value:.
the pxIndexPurpose value is around 45 bytes.
I have found the solution after create sr to pega, turn out i need to do this in order for pega to be able sync if i modify the column size from DB Directly in order for pega to sync the column size .:
Hi, Thx for your response .
i am not increasing the size of property max length.
i am increasing the size of the column size directly from DB because after optimize property for reporting,
by default pega create table pr_index_(CLASS NAME)
on this table they have column called pxIndexPurpose created with 32 byte size.(can't sett the default because it was create automatically by pega when we optimize property for reporting)
i need to change it to 64 byte because when i try to save on my property that was optimize for reporting i get this error : The key property pxIndexPurpose in database PegaDATA, table pr_Index_ASM_FW_GISFW_Data_Pay is too big for its column; column size: 32, property size: 45, property value:.
the pxIndexPurpose value is around 45 bytes.
I have found the solution after create sr to pega, turn out i need to do this in order for pega to be able sync if i modify the column size from DB Directly in order for pega to sync the column size .:
Designer Studio-->Sysadmin-->DatabaseTable
1) Open the table in which the column is available and done the changes in DB.
2) Click on the test connectivity.
3) Save it.
Pegasystems Inc.
IN
Hello Febryl29,
Thanks for posting your query in PSC :)
Firstly, the size of the property is not what is supposed to be in the size of the column it is the width of the field used in the UI. If you have increase the column size that should address. Refer https://pdn.pega.com/support-articles/long-value-index-pxindexpurpose-property-cause-pycommiterror.
Could you provide below information:
- Pega version used
- Exact error observed at your end
- Do you see the same error after increasing the column size?
Just to let you know, an enhancement request has been raised for the reported behavior and would be prioritized for future version of the product.
Regards,
Rincy
Pegasystems Inc.
IN
Hi
You do not need to run anything as such. Logging out and logging in back or simply refresh as Prudhvi suggested should work.
If still it does not reflect the correct size, you need to go back to DB and check whether the chages are reflecting there or not.
Aaseya IT Services Pvt Ltd
GB
Hi, I have some questions below. because we tried same for some other column and it worked fine for us.
1. How did you update the column size? through DB script?
2. If it is through DB Script, Did you commit your changes to the DB?
3. did you check the column size in DB again?
Accepted Solution
asuransi sinarmas
ID
Hi, Thx for your response .
i am not increasing the size of property max length.
i am increasing the size of the column size directly from DB because after optimize property for reporting,
by default pega create table pr_index_(CLASS NAME)
on this table they have column called pxIndexPurpose created with 32 byte size.(can't sett the default because it was create automatically by pega when we optimize property for reporting)
i need to change it to 64 byte because when i try to save on my property that was optimize for reporting i get this error : The key property pxIndexPurpose in database PegaDATA, table pr_Index_ASM_FW_GISFW_Data_Pay is too big for its column; column size: 32, property size: 45, property value:.
the pxIndexPurpose value is around 45 bytes.
I have found the solution after create sr to pega, turn out i need to do this in order for pega to be able sync if i modify the column size from DB Directly in order for pega to sync the column size .:
Hi, Thx for your response .
i am not increasing the size of property max length.
i am increasing the size of the column size directly from DB because after optimize property for reporting,
by default pega create table pr_index_(CLASS NAME)
on this table they have column called pxIndexPurpose created with 32 byte size.(can't sett the default because it was create automatically by pega when we optimize property for reporting)
i need to change it to 64 byte because when i try to save on my property that was optimize for reporting i get this error : The key property pxIndexPurpose in database PegaDATA, table pr_Index_ASM_FW_GISFW_Data_Pay is too big for its column; column size: 32, property size: 45, property value:.
the pxIndexPurpose value is around 45 bytes.
I have found the solution after create sr to pega, turn out i need to do this in order for pega to be able sync if i modify the column size from DB Directly in order for pega to sync the column size .:
Designer Studio-->Sysadmin-->DatabaseTable
1) Open the table in which the column is available and done the changes in DB.
2) Click on the test connectivity.
3) Save it.