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

Error occurs when tried to start Pega 7.1.8 while installing CPM



When installing CPM 7.1.3 (prior to attempting to import jar files) and attempting to start the Pega 7.1.8 instance with the cpmDDL scripts, errors are received.

Error Messages

Unable to check for obsolete database triggers 31603 99999 ORA-31603: object "PWBV4_CIRCUMSTANCE_DUPLICATES" of type
VIEW not found in schema <rule schema name>

*We have verified that the view "PWBV4_CIRCUMSTANCE_DUPLICATES"exists for <rule schema name>

Steps to Reproduce

Start JVM hosting Pega.

Root Cause

The root cause of this problem is defect/misconfiguration in the operating environment.  The user is using a Pega database runtime user that is not granted the required privilege to inspect the database objects for example triggers.


This issue is resolved through the following local-change: 

1. Ensure that there are no Pega triggers that write to pr_sys_updatescache (under data schema) and pr4_rule_vw table (under rules schema) - all the triggers must be dropped during the update process.
2. Disable the startup trigger check by setting the prconfig setting to false (default is true): database/performTriggerCheckAtStartup. 

Published June 30, 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