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

Cannot find stored procedure 'SPPR_POPULATE_INDEX_DATA' on DB2



An error occurs in the PegaRULES log files when the system is started. The system is running on Pega 7.1 with a split schema DB2 database and is monitored by an Automated Event Services (AES) server.

Error Messages

**Date and time**,612 [ PegaRULES-Batch-3] [ STANDARD] [ ] [ PegaRULES:07.10] (ote_Interface_IndexData.Action) ERROR - Error in RDB-Delete There was a problem getting a list: code: -440 SQLState: 42884 Message: DB2 SQL Error: SQLCODE=-440, SQLSTATE=42884, SQLERRMC=SPPR_POPULATE_INDEX_DATA;PROCEDURE, DRIVER=3.62.56
From: (B413CF0978F680C5C4D00842A54CCAF14)
SQL Inserts: <58e8dfce4ff82ed8391b839f1c18d379> <PR_PORTAL_STATE>

Steps to Reproduce

Start a Pega 7 instance with split schema with a DB2 database.

Root Cause

A defect in Pegasystems’ code or rules:
The AES Server does not consider the monitored node is a split schema database.


Perform the following local-change:
Add data schema to the currentFunctionPath in datasource.


Note: This issue is resolved in AES 7.1 running on Pega 7.1.7.

Published November 8, 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