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

Use last update as start filter gets invalid column index error



The Extract rule on History table with Use last update as start filter is not executed in BIX 7.1.6. This issue occurred after applying HFix-27530.

Error Messages

18:36:32,180 [] ( internal.access.ExtractImpl) INFO - History class is not present for class History-YOUR_WORK_CLASS. Proceeding without using history info
18:36:32,183 [ ] ( internal.access.ExtractImpl) INFO - Value of pyLastUpdateDate in pr_Extract_Time at the beginning of BIX run: 2016-06-13 12:32:20.0
18:36:32,383 [ ] ( internal.access.ExtractImpl) DEBUG - Where Condition is: ((pyMessageKey not like ?) OR (pyMessageKey like ?))
18:36:32,383 [ ] ( internal.access.ExtractImpl) DEBUG - sql statement is: SELECT count(pzInsKey) FROM PEGA_DATA.PC_HISTORY_WORK WHERE
pzInsKey like ? AND ((pyMessageKey not like ?) OR (pyMessageKey like ?))
18:36:32,384 [ ] ( internal.access.ExtractImpl) ERROR - SQL Exception: Invalid column index

Steps to Reproduce

  1. Apply HFix-27530 in Pega 7.1.6.
  2. Run the Extract rule.

Root Cause

A defect in Pegasystems’ code or rules:
The query generated by the extract did not include pxCreateDateTime filter condition.


Apply HFix-28183.
Suggest Edit

Published July 2, 2016 - 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