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

AES71[Error]ORA-00942 for PR_DATA_ADMIN



In Pega 7.1.7 application, there are many occurrences of  "java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist" related to the table PR_DATA_ADMIN.

Error Messages

2015-05-15 10:09:53,046 [fault (self-tuning)'] [TABTHREAD1] [ PegaRULES:07.10] (l.access.ConnectionManagerImpl) ERROR a_hostname|win245.xx-yyy.zz a_user - Not returning connection 1 for database "pegadata" to the pool as it previously encountered the following error 
User ID: a_user
Last SQL: SELECT count(pyLabel) myDBResults FROM pr_data_admin WHERE pxObjClass='Data-Admin-Nodes' AND UPPER(pyLabel) = UPPER('a_hostname pegappaes 2015-05-12 09:48:12.878 GMT')AND pxInsName !='2B9C68FF0D68EE5D5A1D8B558AE99D3E' 
java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist 
at oracle.jdbc.driver.T4CTTIoer.processError( 
at oracle.jdbc.driver.T4CTTIoer.processError( 
at oracle.jdbc.driver.T4C8Oall.processError( 
at oracle.jdbc.driver.T4CTTIfun.receive( 
at oracle.jdbc.driver.T4CTTIfun.doRPC( 
at oracle.jdbc.driver.T4C8Oall.doOALL( 
at oracle.jdbc.driver.T4CPreparedStatement.doOall8( 
at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe( 
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe( 
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout( 
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal( 
at oracle.jdbc.driver.OraclePreparedStatement.execute( 
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute( 
at weblogic.jdbc.wrapper.PreparedStatement.execute( 
at com.pegarules.generated.activity.ra_action_validate_1d97360fe3d909311f09ed421e80277e.step3_circum0(
at com.pegarules.generated.activity.ra_action_validate_1d97360fe3d909311f09ed421e80277e.perform( 
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity( 

Steps to Reproduce

Modification of the “Node description" of the system node instance can trigger this error.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules.


Install HFix-23084 to resolve the issue.

Published July 31, 2015 - Updated October 8, 2020

Was this useful?

0% 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