Updated pyLastUpdateDate is not considered when BIX shell script runs
Issue: When a BIX XML is extracted, it is taking the old date value for pyLastUpdateDate to pull the records when though the pr_Extract_Time table is updated to remove the record for that Extract identifier (pyINsName).
The same issue exists when when the pyLastUpdateDate is set to one month back, it is still taking the old value which was there.
BIX Extract -->XML file (filter is defined as pxCreatedatetime or pxUpdateDateTime >Last Extraction Date)
DEV-->Pega Cloud
DB--> Oracle.
The extraction is succesfully always but the problem here is why its not considering the nupdated pyLastUpdateDate?
I have verified LOGS (Pega, Alert and BIXLOG) and there are no errors.
what could be the reason?
what should be the starting point to debug? and what process will look up for this value?
Thanks,
Arjun
***Updated by moderator: Lochan to update Categories***
Pegasystems Inc.
US
Enabling debug on com.pega.pegarules.data.internal.access.ExtractImpl will show you the query being run when the Extract is executed and is typically a good debug starting point.
Is the filter using "Last Extraction Date" or is it "Last Extraction Time"?
What version of Pega is in use?
Are you running the extract through an agent? If so, is the pxExtractDataWithArgs activity being used?
Cognizant
IN
Sure, i will start with that.
Filter is 'Last Extraction Time' in XML
Pega version is '7.1.9' with CS 7.1.4
we are running the shell script with commands in cmd.
Thanks,
Arjun