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 uses wrong filter criteria in BIX V7.1

SA-24554

Summary



When an extract rule is run with an additional filter criteria, filter is not being applied in some cases, which causes the extract to be generated with wrong data.
Issue occurs irrespective of the property in use.


Error Messages



Not applicable


Steps to Reproduce



Not Applicable
 

Root Cause



Issue occurs sporadically and this inconsistent behavior could e accounted to the use of sysnonyms. When ssnonyms were eliminted issue did not reproduce. A bug was raised with Oracle support, details of which are mentioned below.

(Bug 19708887 : DATABASEMETADATA.GETCOLUMNS API RETURN NOTHING WHEN INCLUDESYNONYMS=TRUE)
 

Resolution



As the issue is with oracle database, whenever there is an involvment of sysnonyms, below solution was suggested as a woraround to overcome the effect.
 

Add an additional check in the Shell Script that is being used for execution, to verify the presence of “filter” or “DBColumns Map”.
If the above parameters are absent, re-run the extract to get the correct data.

Suggest Edit

Published June 20, 2016 - Updated December 2, 2021

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