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.
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.
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:
- Move the PegaRULESDefaultSchema and PegaDATADefaultSchema bindings at the correct scope.
- Update the PegaRULES data source to use the data, or base user.
0% found this useful