After Moving OID 11g Servers on AIX to a New Frame with New IP Addresses, ldapbinds from 18.104.22.168 DB Homes Work when Using IP Address for OID but Fail with Hostname: Cannot connect to the LDAP server
Last updated on MARCH 08, 2017
Applies to:Oracle Internet Directory - Version 22.214.171.124 to 126.96.36.199 [Release 11g]
Oracle Net Services - Version 188.8.131.52 to 184.108.40.206 [Release 11.1]
IBM AIX on POWER Systems (64-bit)
Four AIX servers were Oracle Internet Directory (OID) 11g servers are installed. All had been working fine.
Two of the AIX servers were moved to a new Frame and their IP Addresses changed as a result. Nothing else changed.
Since then, the ldapbinds (and other ldap tools) from clients using 220.127.116.11 Database (RDBMS or DB), whether remote of in another home on the same OID server, fail to connect to these OID servers when using the hostname (short or fully qualified):
No errors in the OID logs, as the request fails at the client level and never reaches OID server. DNS and /etc/hosts file are configured correctly and nslookups work. General OID server functionality also works. WebLogic and Oracle Directory Services Manager (ODSM) work and can view,add and delete database (tns) entries in 'Data Browser' without problems.
The same ldapbinds from other versions RDBMS homes, such as 10.2.0.3, and from the OID server homes themselves, all work using the hostname. So this affects only version 18.104.22.168 ldap client homes.
Further, later another set of AIX servers were also moved to a new Frame but this issue did Not occur and binds using hostnames worked fine with those servers. So this affects only that first set of AIX servers.
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 hundreds of Community platforms