This issue is caused because the connect type of JDBC URL of the PegaRUELS DB rule is set to “Use JDBC URL”. In PRPC 6.3 SP1, this rule was delivered as read only in OOTB. But customer has customized it to use the JDBC URL instead of the default “use configuration in preferences”.
Revert back this rule to use "use configuration in preferences" and start the upgrade.
Posted: 5 years ago
Posted: 2 Jun 2017 9:51 EDT
Vigneshwaran Aravindhan (VigneshAravind)
Senior Technology Architect
We received a similar error while performing the third upgrade step (Generate and Apply Rules Schema Objects)
[java] Exception in thread "main" com.pega.pegarules.install.SQLLoaderException: Error executing SQL statements
[java] at com.pega.pegarules.install.SQLLoader.load(SQLLoader.java:80)
[java] at com.pega.pegarules.install.SQLLoader.main(SQLLoader.java:65)
[java] Caused by: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
[java] at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
[java] at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395)
Later we realized that our "Deployment User" did not have enough privileges to read/modify the New Pega7 Rules Schema. Necessary privileges were grated and the issue was resolved.
Occasionally you may also encounter the following error when the deployment user does not have the necessary privileges.