OIDLDAPD and/or OIDDISPD Processes Fail to Start with Log Error "Bind failed" "OS error=(13)" and/or "OS error=97" (Doc ID 1432825.1)

Last updated on AUGUST 30, 2023

Applies to:

Symptoms

When starting 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, which are port numbers 1024 and above.

Changes

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

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.