BIX Extract uses wrong filter criteria in BIX V7.1
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.
Steps to Reproduce
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)
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.