Discussion
Mindtree
IN
Last activity: 6 Apr 2018 19:26 EDT
Unable to check for obsolete database triggers error on upgraded environment after application server restart
Hi,
We recently upgraded an application that was developed in PRPC 5.5 SP1. Post upgrade when we tried bringing up the application server we recieved the error "Unable to check for obsolete database triggers". Our database has triggers that are on a view, this view does not refer to rule view or cache table.
My question here is, in what scenarios do we get this error? Does it come when there is a trigger refering to rule view or cache tables for which pega dropped triggers that were being used for versions prior to 7, or we get this error if there is any trigger present in the database?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Mindtree
IN
We were able to start application server by doing following change:
- Disable the startup trigger check by setting the following prconfig setting to false (the default is true): database/performTriggerCheckAtStartup
I am trying to understand how this check from Pega works.
Pegasystems Inc.
IN