My Oracle Support Banner

Starting A Second OID 10g Instance For SSL Only Fails With Oidldapd02.log Errors: Sgslunllisten: Bind Failed (Port=<NON_SSL_PORT>), Os Error=(98) / FATAL * main * Dispatcher Process unable to bind to port (Doc ID 887865.1)

Last updated on NOVEMBER 15, 2019

Applies to:

Oracle Internet Directory - Version 9.0.4 to 10.1.4 [Release 10gR1 to 10gR3]
Information in this document applies to any platform.


Existing Oracle Internet Directory (OID) instance 1 is already running off the Default Configuration Set (Configset 0)

Unable to start a second instance of OID, instance 2, using Configset 1 which has been changed to
have SSL Enable (orclsslenable) set to "SSL only" (no non-ssl usage), and the SSL port set to a new and unique port number

The $ORACLE_HOME/ldap/log/oidldapd02.log shows following error, reporting a conflict for the non-ssl port of configset 0

2009/09/04:14:27:33 * Main:0 * sgslunlListen: Bind failed (port=<NON_SSL_PORT>), OS error=(98)
2009/09/04:14:27:33 * Main:0 * FATAL * main * Dispatcher Process unable to bind to port


Configset 1 was changed to use SSL only.


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

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