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

BIX Extract fails with CSV for History class

SA-71555

Summary



Business Intelligence Exchange (BIX) extract fails with CSV for the History class.


Error Messages



SQL: SELECT "PZINSKEY" AS "pzInsKey" ,  "null" AS "pyTicketsAdded", pxCommitDateTime AS "pxCommitDateTime" FROM PEGACIADCRPD.History_ESI_OPS_CIA_Work_Task WHERE "PZINSKEY" like ?  AND (("PXTIMECREATED" >= ? )) ORDER BY "PZINSKEY"

SQL Inserts: <HISTORY-ESI-OPS-CIA-WORK-TASK%>    <20181102T145100.000>    

Caused by SQL Problems.
Problem #1, SQLState 42000, Error code 904: java.sql.SQLSyntaxErrorException: ORA-00904: "null": invalid identifier



Steps to Reproduce

 
  1. Create a BIX extract file with History class.
  2. Extract them as a CSV file.


Root Cause



A defect or configuration issue in the operating environment.


Resolution



Here's the explanation for the reported behavior:

History classes do not have a BLOB column (pzpvstream). The column from the table cannot be extracted if it does not exist in that table. For a BLOBless table, only those columns which exist in the database table can be extracted.



 

Published January 17, 2019 - Updated December 2, 2021

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