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

Database tables are mapped to PegaDATA database in single schema



After upgrading from Pega 7.1.5 to Pega 7.1.7 in a single-schema environment, a PegaDATA database is listed even though only one schema is in use.

Error Messages

Not Applicable

Steps to Reproduce

Upgrade from Pega 7.1.5 to Pega 7.1.7 in a single-schema environment observe that a PegaDATA database is listed.

Root Cause

This is an expected behavior.


In Pega 7.1.7, you observe the database “PegaDATA” even if you are using a single schema. If you search for Database Table rules for classes "PegaSample" and "Data-Admin-DB", you will see that one is mentioned as being in "PegaDATA" and the other as being in "PegaRULES". If you click on “Test connectivity” on each, the results should show that they are both pointing to the same schema.

Published June 12, 2015 - 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