Upgrade Failed with ORA-00942: table or view does not exist – pr4_base
The upgrade failed stating pr4_base table not exists. But when we connect to SQL Developer, we were able to see the table present in the migrated schema.
[java] 2015-11-24 09:03:49,326 [ WHE-304] [ ] [ ] ( priv.management.MBeanSecurity) INFO - deny.DatabaseManagement.DatabaseConnectionDetails=true
[java] 2015-11-24 09:03:49,621 [ WHE-304] [ ] [ ] (riv.management.MBeanManagement) INFO - MBean Management (Web) initialized for DefaultDomain
[java] 2015-11-24 09:03:49,645 [ WHE-304] [ ] [ ] ( internal.mgmt.PRRequestorImpl) INFO - RecordWorkInProgress is not enabled
[java] 2015-11-24 09:03:49,851 [ WHE-304] [ ] [ ] (orization.SessionAuthorization) INFO - RSL Update Behavior: Eager
[java] 2015-11-24 09:03:49,951 [ WHE-304] [ ] [ ] ( internal.access.DatabaseImpl) INFO - Bytes input per interaction warning threshold: 50M
[java] 2015-11-24 09:03:49,954 [ WHE-304] [ ] [ ] (ternal.dictionary.ClassMapImpl) INFO - ClassMap using multi-tenant environment: false
[java] 2015-11-24 09:03:49,954 [ WHE-304] [ ] [ ] (ternal.dictionary.ClassMapImpl) INFO - Reading the class group definitions
[java] 2015-11-24 09:03:49,961 [ WHE-304] [ ] [ ] (l.access.ConnectionManagerImpl) ERROR - Not returning connection 0 for database "pegarules" to the pool as it previously encountered the following error
[java] User ID: (unknown)
[java] Last SQL: select pzPVStream from RULESNEW.pr4_base where pxObjClass = ?
[java] java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
[java]
[java] at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91)
[java] at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)
[java] at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173)
Pegasystems Inc.
IN
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.
Cognizant
IN
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]
[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.
[java] java.sql.SQLSyntaxErrorException: ORA-01031: insufficient privileges
This comment has been branched out as a new node and the new thread can be followed here