Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

ORA-00942 : on RULES.pr_data pxObjClass = 'Data-Project-Task'



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] at oracle.jdbc.driver.T4CTTIoer.processError(

     [java] at oracle.jdbc.driver.T4CTTIoer.processError(

     [java] at oracle.jdbc.driver.T4C8Oall.processError(

     [java] at oracle.jdbc.driver.T4CTTIfun.receive(

     [java] at oracle.jdbc.driver.T4CTTIfun.doRPC(

     [java] at oracle.jdbc.driver.T4C8Oall.doOALL(

     [java] at oracle.jdbc.driver.T4CPreparedStatement.doOall8(

     [java] at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(

     [java] at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(

     [java] at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(

     [java] at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(

     [java] at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(

     [java] at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(

     [java] at

     [java] at com.pega.pegarules.deploy.internal.archive.importer.ImporterDataModelImpl.getCountOfClassInTable(

Steps to Reproduce

1. Migrate the RULES table to a new schema using the 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 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.


Prior to running the upgrade modify the files so that the bypass.pega.schema does not equal true.


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

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us