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

Exception on running Business Intelligence Exchange agents



Exception occurs on running Business Intelligence Exchange (BIX) agents. The extraction is incomplete. The issue occurs intermittently. 

Error Messages

Exception at 20190816T040312.563 GMT: Unable to process EXTRACT-RULE-NAME at at pega.pegarules.session.internal.mgmt.Executable.executeCommandLineExtract( pegarules.generated.activity.ra_action_pxextractdatawithargs_70c7b1a10890f90316470d704198da0c.step2_circum0( pegarules.generated.activity.ra_action_pxextractdatawithargs_70c7b1a10890f90316470d704198da0c.perform( 

Steps to Reproduce

Run the BIX extraction.

Root Cause

The filter criteria for the BIX extract contains wildcard usage by using Contains (Property name, text). When the extract starts, the engine must query the database for a list of records which fulfil the filter criteria.  Since Contains was used, the database query uses the Where clause of propertyColumn LIKE '%TEXT%'. The Where clause is unable to take advantage of the index. The query times out due to poor performance. As the database grows the issue grows worse though the extract sizes remain roughly the same.


Perform the following local-change:
Use Starts With instead of Contains for the BIX extraction filter criteria that allows the database to construct a Like clause which can take advantage of the indexes built on the column.   

(Propertyname) STARTS WITH (text)
propertyColumn LIKE 'text%'


Published 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