Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Pxobjclass column too small in table pc_work_notification



Repeated exceptions appear in the PegaRULES logfile indicating the Pega engine cannot read or list items from the PC_WORK_NOTIFICATION table because the pxObjClass column is too small. This effects cases in the following classes:
  • PegaEvent-Notification-Gadget
  • PegaEvent-Notification-Email

Error Messages

2017-06-05 22:00:01,730 [ PegaRULES-Batch-5] [ STANDARD] [ ] [ PegaRULES:07.10] (anner.UnpopulatedColumnScanner) WARN - Unable to process class 'PegaEvent-Notification-Gadget' There was a problem getting a list: code: -302 SQLState: 22001 Message: DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=4.14.137
DatabaseException caused by prior exception: DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=4.14.137
| SQL Code: -302 | SQL State: 22001

From: (B66F3008E286C813E58032FBF234516FE)
SQL: SELECT pzInsKey FROM DATA.pc_work_notification WHERE pxObjClass = ? AND pxApplication is null AND pxCommitDateTime < ?

Caused by SQL Problems.
Problem #1, SQLState 22001, Error code -302: DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=4.14.137

Steps to Reproduce

Create notification items in Pega 7.2.2.

Root Cause

A defect in Pegasystems’ code or rules:

The column PXOBJCLASS was erroneously defined as VARCHAR(24) in this table.


Perform the following local-change:

Change the definition of the column to VARCHAR(96) in the PC_WORK_NOTIFICATION table.

Suggest Edit

Published July 20, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us