Last updated on JANUARY 28, 2010
Applies to:Advanced Networking Option - Version: 10.2.0 to 220.127.116.11 - Release: to 11.2
Information in this document applies to any platform.
For each user session connecting using LDAP authentication (EUS), there is one session between the database server and OID server that is left alive. In time, they tend to pile up until the OID server becomes unresponsive.
This fact can be checked using network utilities such as netstat (here on OID side):
netstat -an|grep 4031
*.4031 *.* 0 0 262144 0 LISTEN
18.104.22.168.4031 22.214.171.124.58979 263536 0 263536 0 ESTABLISHED
126.96.36.199.4031 188.8.131.52.58980 263536 0 263536 0 ESTABLISHED
184.108.40.206.4031 220.127.116.11.58981 263536 0 263536 0 ESTABLISHED
NAMES.NO_PERSISTENT_RESOURCES = TRUE
does not help.
The OID setting: orclLDAPconnTimeOut on OID does work, only that it cuts down all the existing connections to the OID server, hence disrupting other activities that use LDAP for whatever purpose.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms