SA-17162

Summary

During the bootstrap process - "ERROR - PegaRULES initialization failed" is thrown. It is caused by an SQL ORA-00904 error (invalid identifier) when attempting to check for obsolete triggers in the database.

Error Messages

Caused by: com.pega.pegarules.pub.database.DatabaseException: 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

at com.pega.pegarules.data.internal.access.DatabaseImpl.confirmDependentTriggersRemoved(DatabaseImpl.java:15164)
at com.pega.pegarules.data.internal.access.DatabaseImpl.<init>(DatabaseImpl.java:1735)
... 83 more
Caused by: java.sql.SQLSyntaxErrorException: ORA-00904: : invalid identifier

Steps to Reproduce

Recycle Pega after installing Smart Investigate 7.11.

Root Cause

In Pega 7.1.8 and later versions, the updating of the pr_sys_updatescache and pr4_rule_vw tables are no longer handled by database triggers.

Release notes of Pega 7.1.8 states the following:

Startup check removes custom DB triggers<https://pdn.pega.com/release-notes>
The process for performing updates to the pr_sys_updatescache and pr4_rule_vw tables has been restructured to increase system processing efficiency. In previous releases, database (DB) triggers were used to perform updates to these tables. These updates are now performed directly within the Pega 7 engine and the DB triggers have been eliminated.
Accordingly, Pega 7 now checks at startup for any user-created triggers that are added after installation. If any triggers of this type are found, they are automatically removed.
For related information, see Custom DB triggers are dropped during upgrade<https://pdn.pega.com/node/139501>.

The framework that is installed was released at the time of an earlier version of Pega 7.1 when database triggers were still needed. To install this framework on Pega 7.1.9, these database triggers should not be added. When the engine was started, after the triggers were added, it detected that there were triggers added but did not have the database permissions necessary to determine if they were obsolete database triggers and to delete them so it failed to start the engine so these steps could be performed manually.

Resolution

Make the following change to the operating environment:

Drop the following 3 triggers:

Drop trigger TRPAF_RULE_INS;
Drop trigger TRPAF_RULE_UPD;
Drop trigger TRPAF_RULE_DEL;