Common Oracle Access Manager 10g (OAM 10.1.4) Server Issues that a Restart Resolves
(Doc ID 1433634.1)
Last updated on OCTOBER 09, 2019
COREid Access - Version 10.1.4.3.0 to 10.1.4.3.0 Information in this document applies to any platform.
Oracle is not responsible for instructions/information from 3rd party sites that may be contained in this KM note.
There are times when the Oracle Access Manager 10g (OAM 10.1.4) can either hang or crash (memory usage problem). This results in the end user having issues when trying to authenticate to protected resources. The following will focus on the fact that the hang/crash of the Access Servers is due to the growing connections (no one to one relationship with its associated WebGates and LDAP servers) over a period of time until the adverse effect is seen; which when this occurs the only solution is to restart the AAA server in question.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!