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

PRPC Schema Report shows tables missing



After upgrade from 6.3 to 7.19 (split schema), PRPC Schema Report shows a lot of tables, columns and indexes missing but the objects exist in the database.

What are the grants required for schema users across data and rules schema?

Error Messages

PRPC Schema Report shows a lot of tables missing

Steps to Reproduce

After upgrade, run PRPC Schema report. 

Root Cause

A defect or configuration issue in the operating environment.  The application server datasource configuration was not setup per the Installation Guide. The PegaRULES datasource was connecting using the RULES schema name instead of the DATA schema name.  Also the second run on the migrate script to create the rules schema objects was run with the target data schema property not set and as a result the grants needed between the rules and data schemas were not setup correctly.


Make the following change to the operating environment: 

1.  Rerun the migrate script with the correct settings to setup the grants needed between the data and rules schema users.

2. Update the datasource to use the DATA schema name as outlined in the Oracle Tomcat install guide and remove any references to PegaDATA, as they are not needed.

3.. Add entries to conf/context.xml file to define the default rules and data schema names
< Environment name="prconfig/database/databases/PegaRULES/defaultSchema" value="v71rules" type="java.lang.String"/>
< Environment name="prconfig/database/databases/PegaDATA/defaultSchema" value="v71data" type="java.lang.String"/>

4. Update prconfig.xml file to the version that comes with the 7.1 media to make sure environment variables are set like the following:

<env name="database/databases/PegaRULES/dataSource" value="java:comp/env/jdbc/PegaRULES"/>
<env name="database/databases/PegaDATA/dataSource" value="java:comp/env/jdbc/PegaRULES"/>

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