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

PSQLException: ERROR: column PC0.null does not exist



Business Information Exchange (BIX) extract produces exceptions in log.

Error Messages

BIX log:
Caused by: org.postgresql.util.PSQLException: ERROR: column PC0.null does not exist

Pega log:
DatabaseException caused by prior exception: org.postgresql.util.PSQLException: ERROR: numeric field overflow

Steps to Reproduce

1. Go to Records Explorer.
2. Select Extract rule Instances from SysAdmin.
3. Open Extract rule Instance and run.

Root Cause

Some of the properties which are selected in the extract rule to extract are not mapped to any column in the relevant data table.

Hence "column PC0.null does not exist" Error is shown up in the Logs.


Since the user is trying to run extract rule on a class which is an instance of obj-External class and some of the columns are missing in the data table which is mapped to that class, Extraction is unsuccessful and "column PC0.null does not exist" error is shown up in BIX logs.

Published March 27, 2018 - Updated December 2, 2021

Was this useful?

100% 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