Question
Accenture
IN
Last activity: 15 Dec 2015 5:53 EST
While starting Pega 7.1.7 application getting "com.pega.pegarules.pub.database.DatabaseException: ORA-04098: trigger 'schema2.TRPR_DATAADM' is invalid and failed re-validation error"
Hi Team,
My Pega Application is down and it is test environment.
When I'm trying to bring it up getting error as com.pega.pegarules.pub.database.DatabaseException: ORA-04098: trigger 'schema2.TRPR_DATAADM' is invalid and failed re-validation error.
I observed that, server is trying to execute a trigger in another schema which not connected to our application.
For Ex: My application schema is schema1
In the error i can see as it is trying to trigger in schema2 as schema2.TRPR_DATAADM.
This schema2 is not belongs to our application but both schemas are lies in same Database.
please find the attached log file.
If I connect the same environment to different schema(schema2), application is working fine.
Could you let me know what's wrong with my application.
Accepted Solution
Accenture
IN
Issue got resolved.
There was some issue with PEGARULES_AUT.TRPR_DATAADM trigger.
I re-compiled PEGARULES_AUT.TRPR_DATAADM,now it not connecting pegasevenrules schema.
Root cause: Trigger had pegasevenrules schema name in it's procedural code.
Pegasystems Inc.
US
This looks like you have an error in your configuration. Is this a new install or upgrade? Is it a split schema? Please share the full PegaRules log file showing the start of the system.
From the error log I see 3 different schema references - schema1, schema2 and pegarules_aut. What are the actual names of your rules and data schemas? What database user are you using in your PegaRULES datasource?
Accenture
IN
It is not new installation/upgrade.
it is single schema configuration.
the actual schema name is "pegasevenrules" and using the same schema in weblogic datasource.
But it is trying to execute a trigger in another schema i.e. PegaRules_AUT in the same DB.
Let me know for further information.
Pegasystems Inc.
US
In the startup logs we see that the default schema is set to pegasevenrules as you want. Was this system starting previously and all of a sudden stopped working? It seems like someone is setting up an environment in the PEGARULES_AUT schema and it is interferring with your environment.
It seems like there is a trigger PEGARULES_AUT.TRPR_DATAADM which is incorrectly linked to the PEGASEVENRULES.pr_data_admin table. You should have a PEGASEVENRULES.trpr_dataadm trigger in your schema. Get the trigger content for both versions so we can confirm that is what the issue is.
Accepted Solution
Accenture
IN
Issue got resolved.
There was some issue with PEGARULES_AUT.TRPR_DATAADM trigger.
I re-compiled PEGARULES_AUT.TRPR_DATAADM,now it not connecting pegasevenrules schema.
Root cause: Trigger had pegasevenrules schema name in it's procedural code.