My Oracle Support Banner

How to Troubleshoot OID Startup (Including "Bind failed on communication endpoint (13)") (Doc ID 329808.1)

Last updated on APRIL 05, 2018

Applies to:

Oracle Internet Directory - Version 10.1.2 to 11.1.1 [Release 10gR2 to 11g]
Information in this document applies to any platform.

Symptoms

OID fails to start with errors in the OID 10g $ORACLE_HOME/ldap/log/oidldapd0*.log

or

OID 11g $ORACLE_Instance/diagnostics/logs/OID/oid1 or instance name

2006/05/24:13:40:21 * Main:0 * sgslunlListen: Bind failed on communication endpoint (13)
2006/05/24:13:40:21 * Main:0 * FATAL * main * Dispatcher Process unable to bind to port

 

 

NOTE: These steps may also be used when OID fails to start using OPMNCTL.

 

This article applies to OID 10.1.2 through 11g.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References

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