Troubleshooting: "Maximum number of columns" warning when creating a Circumstance Definition rule
When saving a Circumstance Definition, or when saving a rule with a single Circumstance Property, you may receive a warning stating you have exceeded the maximum number of columns.
The wording of this warning depends upon the vendor software that hosts your Pega database:
Database type | Warning |
|---|---|
Oracle | Problem executing SQL to update database schema: code: 1792 SQLState: 42000 Message: ORA-01792: maximum number of columns in a table or view is 1000 |
MSSQL 2000 | CREATE TABLE failed because column ‘%.*ls’ in table ‘%.*ls’ exceeds the maximum of ## columns. Example: System.Data.SqlClient.SqlException: CREATE TABLE failed because column '_Test1' in table 'TestAccountsProperties' exceeds the maximum of 1024 columns. |
DB2 | SQL code -680: Too many columns are specified for a table, view, or table function. |
Solution
Workaround
This warning indicates that you have hit the limit on the number of columns allowed in the circumstance index table.
This is a limitation of the databases themselves (not Pega Platform™), and there is no workaround. You may continue to save Circumstance Definition rules and rules circumstanced by a property, but the Find by Circumstance report on rules will no longer be updated with new circumstance information.