PRPC Schema Report Shows DATA schema missing everything
The application was upgraded from PRPC 6.2 SP2 to Pega 7.1.6. The PRPC Schema Report wizard was run to check for missing schema objects in the upgraded database. The report states that everything was missed in the DATA Schema even though the objects existed when looking into the schema manually.
Steps to Reproduce
Run the PRPC Schema Report.
A defect or configuration issue in the operating environment:
The application server datasource configuration was not set up according to the installation guide. The PegaRULES datasource connected using the RULES schema name instead of the DATA schema name. Environment variables were also not included for the default schema names.
Make the following change to the operating environment:
1. Update the datasource to use the DATA schema name as outlined in the Oracle Tomcat installation guide and remove any references to PegaDATA, as they are not needed.
2. 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"/>
3. Update prconfig.xml file to the version that comes with the Pega 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"/>
0% found this useful