OID DIP / odisrv Process Dies when Oidldapd Log Shows Error: Os Error = 10054 (Doc ID 553422.1)

Last updated on AUGUST 11, 2022

Applies to:

Symptoms

Using Oracle Internet Directory (OID) and DIP (Directory Integration Platform) odisrv processes for both provisioning and synchronization.

ODISRV process dies intermittently.  It may take weeks for the error to reoccur.

Error shown in (10g) <ORACLE_HOME>/ldap/log/oidldapd01s<pid>.log:

Note 1:   There may be nothing logged in the <ORACLE_HOME>/ldap/log/odisrv<instance#>.log files, just an abrupt end of logging at the time of the oidldapd failure, followed by a normal restart.

Note 2:   The OS error 10054 on Windows platform means:
>net helpmsg 10054
An existing connection was forcibly closed by the remote host.

The OS error number varies by platform:

For OID Server on HP:
2007/06/05:10:41:12 * ServerDispatcher :2 * sgslufread: Hard error on read, OS error = 232

For OID Server on Solaris:
2007/06/13:08:36:26 * ServerDispatcher :2 * sgslufread: Hard error on read, OS error = 131

For OID Server on Linux:
2008/07/01:02:41:17 * ServerDispatcher :1 * sgslufread: Hard error on read, OS error = 104

For OID Server onWindows:
2008/07/01:02:41:17 * ServerDispatcher :1 * sgslufread: Hard error on read, OS error = 10054

These OS errors (232, 131, 104, 10054) all mean the same: Connection reset by peer

Changes

Cause

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