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

pr_sys_ruleset_index table is growing exponentially



After upgrade to Pega 7.1.9, pr_sys_ruleset_index table is growing exponentially without any cleanup of records.

Error Messages

There are no error messages

Steps to Reproduce

- Create a new Ruleset version from ruleset say RS
- Do a "save as" on a rule into the new ruleset version.

Root Cause

A defect in Pegasystems’ code or rules

the function pxAllowsRecordInRuleSet when its build the ruleset version list tries to retrieve all version of given ruleset ( rsvlist.addAll(pega_rules_default.GetRuleSetVersions(rsFromName, true))) and this in turn calls getRulesetPrerequiste and dependentrulesetlistpoolimpl to insert the dependentrulesetlist for every version of given ruleset.


Apply Hfix-27767.

With this Hfix applied, only the unlocked versions for ruleset is retrieved.But since “save-as” on a rule fetches and populates the ruleset and ruleset versions that this rule can be saved into, we recommend following best practices to avoid inserting too many records into the table.
  1.       Lock  RSV that are not updated frequently.
  2.       Instead of Re-save into new RS version, consider Branch ruleset

Published June 25, 2016 - Updated October 8, 2020

Was this useful?

50% 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