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

Error in Column Popularity Utility



Column Popularity Utility failed with Database Errors

Error Messages

2015-06-06 10:07:58,678 [                main] [          ] [                    ] (      internal.util.ExposeCols) ERROR   - Encountered batch element exception: [jcc][t4][102][10040][4.14.137] Batch failure.  The batch was submitted, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null
  at com.pega.pegarules.deploy.internal.util.ExposeCols.processBatch(
  at com.pega.pegarules.deploy.internal.util.ExposeCols.saveInstances(
  at com.pega.pegarules.deploy.internal.util.ExposeCols.saveInstances(
  at com.pega.pegarules.deploy.internal.util.ExposeCols.runUtility(
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(

Steps to Reproduce


Root Cause

The root cause of this problem is defect/misconfiguration in the operating environment.  Issue is due to minimal LogFilSiz, LogPrimary, and LogSecond for the Data Warehouse.


The explanation for this behavior is as follows:

Increase the LogFilSiz, LogPrimary, and LogSecond for the Data Warehouse on DB2.


Published July 3, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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