NonexistentTableException during the split schema insallation of PRPC 7.1.7
I've faced the exception below during a split schema installation of PRPC 7.1.7 on a Windows-Tomcat-Oracle stack. Tried both manual installation and automatic insallation but both failed with the same exception.
Anyone faced the same exception before or know the solution?
PDN says : This exception is thrown when PegaRULES configuration points to a database table that does not exist.
Can you do a select of the table and check if the user id of the installation has access to it. Alternatively you can grant access (from sys user) to the pr_assign table for the current user and then re-try.
Thanks for the reply, I've checked that and the table APP_PEGA_COLL_DATA.pr_assign exists and the user APP_PEGA_COLL_DATA has access to it. I can select and desc the table without any issues but still facing the exception com.pega.pegarules.pub.database.NonexistentTableException: Database-NonexistentTable APP_PEGA_COLL_DATA.pr_assign
This exception direcly inherits from ConfigurationException for which details are as below :-
This exception is thrown if there is bad configuration. This might be due to a database table with missing columns, or invalid information in a Rule used by the database (such as Rule-Obj-Class, Data-Admin-DB-Name, or Data-Admin-DB-Table).
I've another PRPC 7.17 instance. I've compared the pr_assign table with APP_PEGA_COLL_DATA.pr_assign and they are identical. I've dropped the data and rules user and re-created the schemas and tried again with both automatic and manual installations but faced the same exception each time :(
Hi Emin, is the deployment using a user that has the select_catalog_role role? It grants the ability to perform meta-data queries about the database structure such as column names and their size & type. Also, please review all privileges and roles required on pages 21 & 22 of the guide, and verify.
The root cause was a mismatch of the character encoding between the server performing the deployment and the database configuration. Please refer to the deployment guides for proper environment configuration.