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

Increase in rows in table pr_index_info (AES Remote)



The number of rows in the pr_index_info table seem to be always increasing. It seems the stored procedure SPPR_POPULATE_INDEX_DATA is at fault. This table is used by AES to get table index information.

Error Messages


Steps to Reproduce

Day to day activities that produce alerts.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. There are defects in stored procedure SPPR_POPULATE_INDEX_DATA for DB2/UDB. 

The stored procedure is putting data in the wrong columns – in particular, it is putting table name in the requestorID column, and crossing table name and requestor ID.


This issue is resolved through the following local change:

  1. Drop the stored procedure (SPPR_POPULATE_INDEX_DATA)

  2. Run the script: sppr_populate_index_data.sql (available from GCS) to recreate the stored procedure

  3. Truncate the values in the table pr_index_info ('alter table pr_index_info activate not logged initially with empty table' or 'truncate table pr_index_info immediate' depending on the version)


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

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