Question

4
Replies
234
Views
Close popover
Haroon Qureshi (HaroonNS2)
SAP NS2

SAP NS2
US
HaroonNS2 Member since 2017 3 posts
SAP NS2
Posted: February 15, 2017
Last activity: February 22, 2017
Closed

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***

Reporting Support Case Exists
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.