After OID Upgrade From 220.127.116.11 To 18.104.22.168, ldapbind Fails with: sgslufread: Hard error on read, OS error = 104 | ldap_bind: Can't contact LDAP server. OAM SSL Connections Fail with: <LIBOVD-40118> | simple bind failed: <HOSTNAME>.example.com:3131
(Doc ID 2441054.1)
Last updated on AUGUST 20, 2019
Applies to:Oracle Internet Directory - Version 22.214.171.124.0 to 126.96.36.199.3 [Release 11g]
Information in this document applies to any platform.
After upgrading Oracle Internet Directory (OID) 11g from 188.8.131.52 to 184.108.40.206, starting Directory Integrated Platform (DIP) Managed Server hangs with log error:
OID 220.127.116.11 had been configured for TLS with orclcryptoversion set to 0 as per: Document 2061665.1 - OID: How To Configure Orclcryptoversion After Applying Patch 19935701 in order to set SSLv3 or TLSv1 in OID 18.104.22.168.3. Additionally, ciphers in the OID instances may have been modified/replaced.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document