BIX Extract via Agent (runExtract activity) causing Error
Pega 7.1.6 BIX:07-10-13
When calling queueRunExtract (which internally calls runExtract) activity through daily agent, It appears that log files generated during extraction are enormous in size and locking database table to respond. This stops opening any Extract Rule (new / existing) and Log-Extract instances. All requester threads in Pega are also dangling and not stopping.
Since we are in 7.1.6 and BIX 07-10-13 – Is there any fix for this version?
Log:
2017-02-10 16:39:16,147 [ PegaRULES-Batch-4] [ STANDARD] [ ] [aExtraction:01.01.01] (ernal.async.BatchRequestorTask) ERROR - Batch activity "Rule-Admin-Extract.runExtract" threw:
at com.pega.pegarules.data.internal.access.ExtractImpl.runExtract(ExtractImpl.java:1606)
at com.pegarules.generated.activity.ra_action_runextract_7eb17a5ada24845605c3d982093ca8a6.step1_circum0(ra_action_runextract_7eb17a5ada24845605c3d982093ca8a6.java:169)
at com.pegarules.generated.activity.ra_action_runextract_7eb17a5ada24845605c3d982093ca8a6.perform(ra_action_runextract_7eb17a5ada24845605c3d982093ca8a6.java:69)
***Updated by moderator: Lochan to add SR Exists group tag; update topic category***
Pegasystems Inc.
US
It's worth pointing out that running BIX via an agent is supported starting in 7.1.8 with the use of pxExtractDataWithArgs activity. That being said, this SA talk about a similar issue, though it doesn't appear to correspond to the error snippet you provided: https://community.pega.com/support/support-articles/bix-extract-rule-caused-massive-log-file
If you can produce this same behavior while running BIX manually (not via an agent), I'd suggest providing us with the complete log to review.
SAP NS2
US
It gets more complicated now - I turned off the agent and just configuring the extract rules but same behavior. The requester is still hanging on opening extract rule (new or existing).
Pegasystems Inc.
US
Were you still running the extract rule via an activity? If so, does it work if you just try running the extract via the extract rule itself?
If you running the extract via the extract rule itself still causes the issue, a complete log would be helpful to see. I would suggest opening an SR but you could provide it here if you wish.