Support Article

ORA-31603: PWBV4_CIRCUMSTANCE_DUPLICATES view not found

SA-32922

Summary



Application isn't available after JVM restart.

Error 503: PegaRULES server not available


Error Messages

Error 503: PegaRULES server not available

Caused by:
com.pega.pegarules.pub.database.DatabaseException: Database-General Unable to check for obsolete database triggers 31603 99999 ORA-31603: object "PWBV4_CIRCUMSTANCE_DUPLICATES" of type VIEW not found in schema "SCHEMANAME"
ORA-06512: at "SYS.DBMS_METADATA", line 5805
ORA-06512: at "SYS.DBMS_METADATA", line 8344
ORA-06512: at line 1

From: (unknown)
Caused by SQL Problems.
Problem #1, SQLState 99999, Error code 31603: java.sql.SQLException: ORA-31603: object "PWBV4_CIRCUMSTANCE_DUPLICATES" of type VIEW not found in schema "SCHEMANAME"
ORA-06512: at "SYS.DBMS_METADATA", line 5805
ORA-06512: at "SYS.DBMS_METADATA", line 8344
ORA-06512: at line 1

at com.pega.pegarules.data.internal.access.DatabaseImpl.confirmDependentTriggersRemoved(DatabaseImpl.java:15164)
at com.pega.pegarules.data.internal.access.DatabaseImpl.<init>(DatabaseImpl.java:1735)
... 70 more
Caused by:
java.sql.SQLException: ORA-31603: object "PWBV4_CIRCUMSTANCE_DUPLICATES" of type VIEW not found in schema "SCHEMANAME"
ORA-06512: at "SYS.DBMS_METADATA", line 5805
ORA-06512: at "SYS.DBMS_METADATA", line 8344
ORA-06512: at line 1


Steps to Reproduce



Login to application following a JVM restart


Root Cause



A defect or configuration issue in the operating environment Pega 7 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

In this instance, the TriggerCheck was failing, potentially due to a missing Oracle Privilege.



Resolution



Perform the following local-change:

Disable the Trigger check invocation from system start-up by modifying the proconfig.xml with the following setting:
  • database/performTriggerCheckAtStartup FALSE (defaults to true)

After adding this setting, the system was available and functionality restored.

Published January 26, 2017 - Updated January 29, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.