Support Article
ORA-00942 : on RULES.pr_data pxObjClass = 'Data-Project-Task'
Summary
While performing an upgrade from 6.2SP2 to 7.2 the following error is being encountered and the upgrade fails.
Error Messages
[java] User ID: (unknown)
[java] Last SQL: select count(*) as "count" from UPGRADE718.pr_data where pxObjClass = 'Data-Project-Task'
[java] 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)
[java] at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802)
[java] at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)
[java] at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
[java] at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521)
[java] at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:205)
[java] at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:861)
[java] at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1145)
[java] at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1267)
[java] at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3449)
[java] at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3493)
[java] at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1491)
[java] at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.executeQuery(DatabasePreparedStatementImpl.java:411)
[java] at com.pega.pegarules.deploy.internal.archive.importer.ImporterDataModelImpl.getCountOfClassInTable(ImporterDataModelImpl.java:428)
Steps to Reproduce
1. Migrate the RULES table to a new schema using the migrate.sh script
2. Run the upgrade script
Root Cause
During the upgrade it is necessary to copy some of the Data tables to the new Rules schema.
However, if the setupDatabase.properties file setting bypass.pega.schema is set to true, then these table do not get copied to the Rules schema which leads to the above failure.
Resolution
Prior to running the upgrade modify the setupDatabase.properties files so that the bypass.pega.schema does not equal true.
bypass.pega.schema
====
Secondary issue.
The above setting helped to get further into the upgrade process, but this was then failing with the error below
The above failure appeared to be related to the USERS tablespace being full.
This was subsequently increased to 15GB and the upgrade restarted.
Published April 13, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.