Could not Process Error while processing BIX Extracts via agents
BIX Extract in CSV format is processed by advanced agent running on multiple nodes.
While checking the execution history of bix extract for that class, the records are frequently failing with "Could not process" status.
Could someone please let me know what can be the issue.
Pegasystems Inc.
IN
Hi,
Could you please enabled below loggers in All leval and run the extract. Then check Bix log file and share log file.
com.pega.pegarules.data.internal.access.ExtractImpl
com.pega.pegarules.data.internal.access.ExtractParameters
com.pega.pegarules.data.internal.access.DatabaseUtilsCommonImpl
Ciberspring Inc
IN
2020-07-05 05:13:27,377 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - # Total Instances retrieved: 0 2020-07-05 05:13:27,384 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - Elapsed Time (seconds): 90.118 2020-07-05 05:13:27,384 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - Total CPU Time (seconds): 0.0 2020-07-05 05:13:27,384 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - #Instances Extracted: 0 2020-07-05 05:13:27,384 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - #Instances per second: 0.0 2020-07-05 05:13:27,384 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - #Instances per hour: 0.0
2020-07-05 05:13:27,377 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - # Total Instances retrieved: 0 2020-07-05 05:13:27,384 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - Elapsed Time (seconds): 90.118 2020-07-05 05:13:27,384 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - Total CPU Time (seconds): 0.0 2020-07-05 05:13:27,384 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - #Instances Extracted: 0 2020-07-05 05:13:27,384 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - #Instances per second: 0.0 2020-07-05 05:13:27,384 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - #Instances per hour: 0.0 2020-07-05 05:13:27,384 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - #Instances not extracted due to errors: 0 2020-07-05 05:13:27,385 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - {i=AB-PO-CIP-DATA-TESTR-TEST!TEST} 2020-07-05 05:13:27,387 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - Processing extract rule with insKey :RULE-ADMIN-EXTRACT AB-PO-CIP-DATA-TESTR-TEST TEST #20180717T092321.515 GMT 2020-07-05 05:14:57,495 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) ERROR - Error while getting the sequenceNumberAn I/O error occurred while sending to the backend. 2020-07-05 05:14:57,496 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) ERROR - Error while doing a commit to pr_log Table 2020-07-05 05:14:57,496 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) ERROR - Error while getting the count from manifest table 2020-07-05 05:14:57,508 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) ERROR - Unable to process AB-PO-CIP-DATA-TESTR-TEST: null java.lang.NullPointerException: null 2020-07-05 05:14:57,508 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) ALERT - 2020-07-05 05:14:57,508 GMT*8*EXCP0001*0*0*util-i-0e849fcd4802241cf*NA*NA*BVGJE2SPFWZDM6L9Y98DIF12TATAY2OI6A*System*AB-PO-CIP-Work*PIC:01.01*166d8b8d1d3a3686c270aab544bb52f5*N*1*BVGJE2SPFWZDM6L9Y98DIF12TATAY2OI6A*4948*PegaRULES-Batch-9*STANDARD*com.pega.pegarules.data.internal.access.ExtractImpl*NA*RC-FW-CIPFW-Data-BixExtract.RunExtractW1*Rule-Obj-Activity:RunExtractW1*RULE-ADMIN-EXTRACT PXEXTRACTDATAWITHARGS #20180713T143905.514 GMT Step: 2 Circum: 0*NA****NA*NA*Rule-Admin-Extract*ExtractPage*Rule-Admin-Extract*ExtractPage*Java;RULE-OBJ-ACTIVITY RULE-ADMIN-EXTRACT PXEXTRACTDATAWITHARGS #20180713T143905.514 GMT Step: 2 Circum: 0;doActivity Rule-Obj-Activity:pxExtractDataWithArgs;Call pxExtractDataWithArgs;RULE-OBJ-ACTIVITY RC-FW-CIPFW-DATA-BIXEXTRACT RUNEXTRACTLIST #20200622T054527.880 GMT Step: 1_2 Circum: 0;6 additional frames in stack;*pxObjClass=;pyArgs=[removed];pyExtractName=[removed];pyExtractClassName=[removed];*[MSG][Unable to process AB-PO-CIP-DATA-TESTR-TEST: null][STACK][java.lang.NullPointerException<CR>]* 2020-07-05 05:14:57,519 [ PegaRULES-Batch-9] [ ] [ PIC:01.01] ( internal.access.ExtractImpl) INFO - PAL Statistics for BIX Extract run : Non-rule-resolved instances accessed from the database: 6 CPU time accessing non-rule-resolved instances from the database: 0 Elapsed Time accessing non-rule-resolved instances from the database: 0.037 CPU time retrieving rule-resolved Rules from the database: 0 Rule-resolved rules requested from database or cache: 6 Bytes read from database Storage Streams (uncompressed): 143680 Number of database requests that exceeded the time threshold: 0 CPU time spent performing BLOB decryption: 0 Elapsed time spent performing BLOB decryption: 0 BLOB decryption: 0
Incessant Technologies Pvt.Ltd
AU
Hello,
Based on the logs that are provided following are the errors which I can see
Null Pointer Exception. Generally this exception comes when there is any issue with the Work Object opening while extracting the data by BIX Rule.
Error while getting the sequenceNumberAn I/O error occurred while sending to the backend : This error will occur if the DB Query time out happens while retrieving the data for extraction.
Error while doing a commit to pr_log Table ,Error while getting the count from manifest table : Due to the above errors these might be occuring.
This message Could not process" status in the Execution History will appear when there is any issue in records extraction any data issues and it will provide the percentage of successfully executed records and the failed Ins Keys can be found in the PegaBIX.log file.