Restore PegaRules schema after a blocking issue
Hi all,
last week we mistakenly installed a product rule in our pre-production environment which had an application that was built on an other one that was not present in that environment. Due to this, the following exception appeared in the log "Unable to construct authorization core due to authorization failure" and we were not able to reach Pega Login page.
The only way we found to solve the issue was a complete restore of both the PEGARULES and PEGADATA database schema to a backup we created before installing the product rule.
When issue like this one appears would be enough to restore only PEGARULES schema or it is recommended to restore also the PEGADATA schema?
I am interested in this because if situation like that one should happen in Production, restoring also the DATASCHEMA would likely cause data loss.
Thanks a lot for your support.
Best regards.
Claudio
Proximus
BE
Hello,
We often import RULES Schema in Prod from a controlled lower env.
Yet what needs to be considered before working like this is all which is linked to the environment.
If you've got some rules holding some parameters for the environment (some paths, some URLs, etc...) then if not foreseen, it will be erased by the source envinroment info.
For each environment, we've got a circumstanced version of such rules which are there in all environments.
For your issue, did you try starting your application as prpc/pega and log with the famous [email protected].
This is a first attempt allowing to access the system without calling the rest of the rules.
Still, Rules import is safe if you know what to correct & where.
Your DBA should also make sure that all synonyms and grants and still properly defined post schema import.
Regards
Anthony