OAM Application Domain Stops Working After Adding New Policy In Existing App Domain
(Doc ID 2706374.1)
Last updated on OCTOBER 15, 2020
Applies to:Oracle Access Manager - Version 18.104.22.168.190209 and later
Information in this document applies to any platform.
When an OAM system has a large set of policy data (for this particular case there were of 800 applications integrated with OAM) the OAM policy loaded mechanism can break such that when policy reload is called it reads some of the data but gets corrupted and never finishes the loading. In an MDC environment this seems to happen more frequently on the clone side of things after APS replicates the data. However, the same problem can be seen on an MDC Primary as well as single-node environment.
The typical symptoms seen are that previously protected resources nor the newly added resources are no longer protected.
From the OAM diagnostic logs it can be seen that the policy refresh is started but never completed. For example, the diagnostic log will show the following for a successful start/end of a policy load:
However, when the policy reload fails the 2nd line above is not displayed for an application domain.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document