Monday, 6 April 2015

R1213 SSO-OID-LDAP Error oame OAMSSA-20027 Could not get user : username, idstore: EBSIdStore == oam_server1.log

Error ==>

<Mar 17, 2015 5:47:20 AM PDT> <Error> <oracle.oam.user.identity.provider> <OAMSSA-20027> <Could not get user : ledefall, idstore: EBSIdStore, with exception: oracle.security.idm.OperationFailureException: javax.naming.NamingException: LDAP response read timed out, timeout used:2000ms.; remaining name 'cn=adusers,cn=users,dc=vijoraapps,dc=com'.>

Solution :

Collected data using
1) Collect data using - >  oiddiag collect_all=true
2) All OID logs from the time of the Timeout errors
(Oracle_Instance/diagnostics/logs/OID/oid1 or instance name)

OID1 instance you have the following default attributes set:
3000 : orclmaxcc=4
3000 : orclserverprocs=1

Reference Doc: http://docs.oracle.com/cd/E28280_01/core.1111/e10108/oid.htm#ASPER99273
Check out the section labeled "23.3.2 LDAP Server Attributes"
http://docs.oracle.com/cd/E28280_01/core.1111/e10108/oid.htm#ASPER99964

You will notice the chart where orclserverprocs and orclmaxcc is mentioned
For orclserverprocs the recommendation is :orclserverprocs Number of CPU cores
and for orclmaxcc, the recommendation is 10

Another suggestion would be the tuning wizard documented here:
http://docs.oracle.com/cd/E28280_01/core.1111/e10108/oid.htm#ASPER106

Also refer:  OID Performance Tuning Checklist (Doc ID 458703.1)

Thanks
Vijay

No comments:

Post a Comment

SQL Shared Area - BIND MISMATCH