Database-BadTableMapping-KeyPropertyTooBig - Column length has been increased and DB Table/Class saved

General
, ,
1

Hi,

Greetings. I am getting the below error, i have increased the column size to 256 and also re-saved Database Table mapping as well as class instance

Database-BadTableMapping-KeyPropertyTooBig PXINSNAME PegaDATA pr_perf_stats 128 132

Is there anything else i should be doing?

I am on Pega 8.8.2 (containarized deployments)

Regards,
Bharat

2

Hi @KOMARINA

My understanding is that you can’t increate the size of the colom.

When updating or overriding a property that has a Max Length defined, you can enter a smaller Max Length value but not a larger value.

Please refer below articles

Thanks,

Ashok

3

@Bhumireddy Thank you but pxInsName has no length defined within Pega. Increased length can be seen via Modify Schema wizard within Pega, just that error is still being trhown on old/original length.

Regards,

Bharat

4

Hi @KOMARINA,

Could you please give a try by using below activity.

CL:Code-Pega-DB-Column ID:pzUpdateColumnLength

Can you try the following after increasing the column in the schema

  1. Open the class rule form

  2. Do a test connection

  3. Save the class rule form

  4. Open Data-Admin-DB-Table instance of the class

  5. Do a test connection

  6. Save the Data-Admin-DB-Table instance

Thanks,

Ashok

5

@Bhumireddy We are using Oracle, i do not see a way to execute this activity standalone however column length has been increased and can be seen via Modify Schema. I did do re-save of class and database table.

Regards,

Bharat

6

Clearing the Conclusion Cache from Admin Studio for type “property” resolved the issue.