Pega 8.5 error : Table can't have more than 1600 columns

General
, , ,
1

We are using surveys in pega 8.5, which are cases in this version.

We also have several cases whose classes point to our main Work class : EXAMPLE_Work.

Each simple question our property on our surveys is a column on EXAMPLE_Work.

Hence, starting from a specific number of columns in EXAMPLE_Work, we have an error stating that there can’t be more than 1600 columns in a table.

So we tried to free some space by deleting columns. From 1600, we only have 160 remaining.

Yet, the error still persists and we can’t edit or save any of our cases in EXAMPLE_Work, even after the 1440 deletions, as shown in the following screenshots.

We are using Postgres as a database.

Error_MaximumNbOfColumns.png
Error_MaximumNbOfColumns.png1246×716 105 KB

Mapping-Class_to_DatabaseTable.png
Mapping-Class_to_DatabaseTable.png857×237 16.2 KB

Nb_of_columns_currently.png
Nb_of_columns_currently.png735×373 49.7 KB

2

@HibaA120

Hello,

Have you checked the table itself in your DB? is it also showing 160 columns?

Since the table is much smaller and with very few lines, you could maybe consider rebuilding it from scratch.

Regards

Anthony

3

After investigating the issue with a DBA, it is due to a Postgres specification that the Alter table for deleting columns applies the changes to Pega tables but only hides columns in PG.

So basically there were still 1600 columns.

4

Hi, we’re facing the exact same issue on our end — same 1600-column error on Postgres, even after deleting a number of columns. How did you finally resolve it on your side? Did you use ALTER TABLE queries, or something else like a table rebuild?.