Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Table PR_SYS_WORKINDEXER_QUEUE is very large (>6GB)



PR_SYS_WORKINDEXER_QUEUE table size is greater than 6 GB. Records are not being removed from this table by the SystemWorkIndexer Agent.

Error Messages


Steps to Reproduce


Root Cause

The root cause of this problem is a defect in customer application code/rules. The settings for the default search node matched none of the available production nodes, causing items to remain in queue since there was no Agent capable of processing.


This issue is resolved by making the following change to the PRPC operating environment: Updated the settings on the Indexing (Search) Landing Page - setting one of the production nodes as the declared Indexing node.  Once the HostName and HostID matched one of the nodes (and once the SystemWorkIndexer agent was enabled on that node), items were drained from the queue as expected.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us