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

java.sql.SQLSyntaxErrorException: ORA-00942 during installation



Failing to complete the installation of Pega platform due to ORA-00942 errors.
When running, an error appears after an hour or so of installation processing.

Error Messages

[exec] [java] Last SQL: SELECT distinct pr4_rule_vw.pyRuleName as "pyRuleName",(pr4_rule_vw.pxInsId) as "pxInsId",pr_index_reference.pxRuleFamilyName as "pxRuleFamilyName", pr_index_reference.pxRuleClassName as "pxRuleClassName",pr_index_reference.pxRuleObjClass as "pxRuleObjClass" FROM PEGA_RULES_O.pr_index_reference INNER JOIN pr4_rule_vw ON (pr4_rule_vw.pxInsId = {fn concat('!', pr_index_reference.pxRuleFamilyName)} and pr_index_reference.pxRuleClassName is not NULL) or (pr4_rule_vw.pxInsId = pr_index_reference.pxRuleFamilyName and pr_index_reference.pxruleclassname is NULL) WHERE pr_index_reference.pxRuleObjClass not in('Rule-Method' ,'Rule-Obj-FieldValue', 'Rule-Obj-Class','Rule-File-Binary','Rule-File-Bundle','Rule-File-Text','Rule-Message','Rule-Connect-SOAP','Rule-Utility-Library','Rule-Utility-Function','Rule-Obj-Ticket','Rule-Access-Privilege') and pr_index_reference.pxInsIndexedKey = 'RULE-OBJ-FLOW PEGASAMPLE-TASK BASICPROCESS #20140912T072746.591 GMT' and pr_index_reference.pxIndexPurpose = 'RuleReference' and pr_index_reference.pxObjClass = 'Index-Reference'

[exec] [java] java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

[exec] [java]

[exec] [java] at oracle.jdbc.driver.T4CTTIoer.processError( ~[ojdbc-]


[exec] [java] at ~[prprivate.jar:?]

[exec] [java] at com.pega.pegarules.generation.internal.assembly.staticassembly.smartconfig.cache.ReferenceCache.loadReferencesFor(

Steps to Reproduce

1. Generate dl,sh to get the oracledata.sql
2: Execute oracledate.sql to create all db objects
3: Issue

Root Cause

A software use or operation error.

The install job is spun via Jenkins and --assembler = true JVM argument is passed which runs Static Assembly during installation.

Pega does not expect Static Assembly to be run as part of install job and out of the box scripts are shipped without it.


Make the following change to the operating environment:

Remove --assembler option from Jenkins for running install.

As a local change, if need to run with --assembler option, create appropriate synonym on pr4_rule_vw table.

The SQL query that does not include Schema qualification will be fixed in future Pega release.

Published February 9, 2018 - 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