OIDLDAPD and/or OIDDISPD Processes Fail to Start with Log Error "Bind failed" "OS error=(13)"
Last updated on APRIL 06, 2018
Applies to:Oracle Internet Directory - Version 10.1.2 to 18.104.22.168.0 [Release 10gR2 to 12c]
During the attempted start of the OID processes, the OIDLDAPD and/or OIDDISPD processes will not start when configured to use ports 389 and/or 636.
However, OID does start on non-privileged ports.
This issue can be experienced during initial OID configuration, after upgrading, after patching the home (even with non OID specific patches), or another operation where file level permissions, ownership, or access to binary file $ORACLE_HOME/bin/oiddispd has been altered. Other known scenarios include mounting the the OS Volume OID is installed onto with the NOSUID or NOEXEC mount options
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