Database Table connection error
User reports that they have changed the Database rule from 'use JDBC URL listed below' to 'use JDBC Connection Pool' and this does not work due to the error on test connection on the database rule.
Oracle 12c is used to host the external schema.
Connection Problem: Class MyOrg-Data-Class is mapped to table WRONG_SCHEMA_NAME.MY_TABLE_NAME which contains no columns
Steps to Reproduce
- Add a JDBC datasource for the external database.
- Add the necessary database driver in the classpath.
- Define a Database Table rule to 'use JDBC Connection Pool' and do not mention the schema name.
- Perform the test connection for the database rule.
A defect in Pegasystems’ code or rules:
Oracle synonyms have been only passively supported within the platform, and historically there have been a number of issues surrounding the use of synonyms within the Pega platform.
Perform the following local-change:
Use the defaultSchema settings within either Application Server specific configuration setting, like Tomcat's context.xml or the User's prconfig.xml file to define the default schema for the given Data-Admin-DB-Name.
This would make it so that all queries against the given Data-Admin-DB-Name would be schema qualified with the provided schema name. This would give the User a single place to update their schema information should the value change in the future.
To change the value in the context.xml file, a setting such as the following can be used:
<Environment name="prconfig/database/databases/<Name of Data-Admin-DB-Name>/defaultSchema" value="<Name Of Schema>" type="java.lang.String" />
If the value is to be set in the prconfig.xml file, the setting can be formatted as follows:
<env name="database/databases/<Name of Data-Admin-DB-Name>/defaultSchema" value="<Name Of Schema>" />
0% found this useful