In 7.1.7 there are still database triggers in use which would have schema qualified table references in the trigger body. Did you use a database tool to rename the schemas from pegarules to pegarules1? Or is this just that you have 2 new data and rules schemas that you installed/updated and you just want to know if there is anything other than the defaultSchema references in the context.xml that needs to be updated?
I am confused by what you are going to use if not a db tool to restore the database.
Here is an example scenario for an Oracle database. Export pegarules schema using Oracle datapump. Create new schema pegarules1 and then use datapump to import pegarules schema to pegarules1. If you do this in 7.1.7 you will need to make changes to the database triggers as Oracle datapump will remap the signature lines of the triggers, stored procedures, etc. but will not change anything within the body. Within the body you will have schema qualified references which will still point to pegarules schema instead of pegarules1.
We have created new schemas by importing exisitng in to the existing DB.
Old DB: Admin, PEGARules, PEGAData
New DB: Admin, PEGARules, PEGAData, Admin_DEV, PEGARules_DEV, PEGAData_DEV
We have not modified any connection details in the application server but when we restarted the application server observing the following error:
com.pega.pegarules.pub.database.DatabaseException: Database-General Problem writing an instance to the database 4098 42000 ORA-04098: trigger 'PEGADATA_DEV.TRPR_DATAADM' is invalid and failed re-validation
Application is not getting started and showing as "PegaRULES server not available". Why it is accessing the other schama objects without configrations?
Posted: 4 years ago
Posted: 11 Jul 2017 10:38 EDT
Celeste Dufresne (CelesteDufresne_GCS)
Principal Software Solutions Engineer
What is in this trigger body that is causing it to fail? Is it pointing to a table in the old schema perhaps? The signature and body need to match and the user running the system needs to have the appropriate privileges on everything in the new rules and data schemas.
ORA-04098: trigger 'PEGADATA_DEV.TRPR_DATAADM' is invalid and failed re-validation