My Oracle Support Banner

Unable to modify OUD store settings with error connection failed from oamconsole or wlst (Doc ID 1933071.1)

Last updated on JUNE 06, 2017

Applies to:

Oracle Access Manager - Version and later
Information in this document applies to any platform.


On : version

User  not able to change any ID store setting (like MAX_CONNECTIONS or MIN_CONNECTIONS)– either via the OAM console or through WLST.
OAM does a search using uid=* on the user base and fails if there are millions of  entries there.

Issue is  similar to outlined in Note 1632867.1
The workaround suggested in the Note and bug is to use the equivalent WLST command to do this.
However, when  we try that, it tests the connection in a manner similar to what the console does and fails.

OAM Logs:-

Caused by:
Caused by: javax.naming.ServiceUnavailableException: [LDAP: error code 52 - Unavailable]; remaining name 'ou=user,dc=myco,dc=com,dc=au'

OUD Access logs output:-

[03/Oct/2014:08:37:13 +1000] SEARCH RES conn=28692 op=176 msgID=177 result=118 message="Client Unbind" nentries=0 additionalInfo="Unindexed" etime=10998




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.