OAM Runtime Access Is Impacted When OAM DB Is Not Available.
(Doc ID 1638851.1)
Last updated on MARCH 20, 2019
Applies to:Oracle Access Manager - Version 126.96.36.199.3 and later
Information in this document applies to any platform.
Oracle Access Manager (OAM) 188.8.131.52.3.
Customer brought the DB down for maintenance activity on the OAM Audit DB the DB server had been stopped. Before doing so, they switched the OAM audit from the DB to file and even the Oracle coherence session worked from memory.
During this activity we expected that the OAM service would not have been impacted by the Policy Store Down. But what happened is that the authentication process started to be very slow and sometimes not reachable.
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