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

After HFix-30178, Use last update as start option not respected



Business Intelligence Exchange (BIX) extract, with the output format as a database schema, does not work initially when the source and destination tables are in different databases.
After installing HFix-30178 and HFix-45698 with its dependent hotfixes, the data is pushed to the destination database. Despite selecting the 'Use last updated time as start' checkbox in the 'Filter Criteria' tab in the Extract rule, the extract does not run on the recently updated work objects. The extract runs on all the work objects and pushes them to the destination database (each run extracting all work object).
The second run continues to ignore the filter criteria and pushes all resolved work objects, thus creating duplicate data.

Error Messages

[PegaRULES-Batch-19] [ ] [your_WS:01.01.03] (internal.access.ExtractImpl) ERROR ad70304 - SQL Exception could not get last update time. Invalid object name 'PEGA_DATA.PR_EXTRACT_TIME'.

Steps to Reproduce

  1. Install HFix-30178, and HFix-45698 with its dependent  hotfixes.
  2. Set the 'Use last updated time as start' option.
  3. Run the extract.
  4. Rerun the extract.

Root Cause

A defect in Pegasystems’ code or rules.
Pega searched for the PR_EXTRACT_TIME table in the external database when the source and the destination were in the external database.


Apply HFix-47326.


Published April 4, 2019 - 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