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

Classes mapped to PegaDATA schema are not finding the tables



After a migration from PRPC 6.3 SP1  to Pega 7.1.7 split schema, classes mapped to the PegaDATA schema are not finding the tables in the data schema.

Error Messages

Not Applicable.

Steps to Reproduce

Upgrade PRPC 6.3 SP1 to Pega 7.1.7 split schema and start the system on WebSphere application server.  

Open a class that maps to a database table in the PegaDATA schema and test connectivity.

Root Cause

The root cause of this problem is defect/misconfiguration in the operating environment.

The bindings for the defaultSchema properties were not defined at the correct scope to be seen by the system.  

Also the PegaRULES datasource was being started as the rules schema user instead of the data schema user.


This issue is resolved by making the following change to the operating environment: 
  1. Move the PegaRULESDefaultSchema and PegaDATADefaultSchema bindings at the correct scope.  
  2. Update the PegaRULES data source to use the data, or base user.

Published March 10, 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