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

PegaRULES initialization failed during update



When updating from Pega 7.1.5 to 7.1.9 the PegaRULES engine fails to initialize, and causes the update process to abort.

Error Messages

2016-03-07 10:07:53,951 [ <ID>] [ ] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: vslmlopsd1 PRNodeImpl init failed
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(
Caused by: Problem initializing Connection Manager
... 18 more
Caused by: Database-General Unable to check for obsolete database triggers 904 42000 ORA-00904: : invalid identifier

From: (unknown)
Caused by SQL Problems.
Problem #1, SQLState 42000, Error code 904: java.sql.SQLSyntaxErrorException: ORA-00904: : invalid identifier

... 37 more

Steps to Reproduce

Run the script to start an update.

Root Cause

A third-party product issue: The Oracle database user did not have required privileges for the update process.


Please see pages 9, 10 and 11 of the installation guide regarding the necessary privileges for the database user during upgrade/update processing:

Published March 18, 2016 - 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