Whenever SqlNet Clients (SqlPlus or Tnsping) Disconnect, OID Server Log File Shows: On HP "sgslufread: Hard Error On Read, OS Error = 232" (OS Error = 131 on Solaris; 104 On Linux; 10054 on Windows) (Doc ID 437493.1)

Symptoms

Oracle Internet Directory (OID) Server 10g or 11g.

Several of the following error messages appear in OID server's $ORACLE_HOME/ldap/log/oidldapd01s<pid>;.log file:

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: Connection reset by peer

Note: To find these and other unix/OS error codes and corresponding messages:
- On solaris and HP: 
   cd /usr/include/sys 
   grep <error number or text> errno.h
- On Linux:
   cd /usr/include/asm
   grep <error number or text> errno.h
- On Windows:
   net helpmsg 10054
   See also <Note 67211.1> Network.Troubleshooting / WINSOCK Error Codes

The errors appear on the oidldap log file when Oracle clients version 8i, 9i, 10gR1, 10gR2 resolve database aliases / tnsnames connect descriptors via ldap naming.

Clients do not get any errors and resolve tnsnames properly using LDAP method.

However, as reported for OID servers on Windows, the error can be displayed directly to client's sqlplus/tnsping sessions as well as show up in the OID Server log.

After further research, found that the problem is related to client disconnecting from the oid (ldap) server, i.e. when trying to connect to the database using LDAP names resolution everything works fine and there are no error messages. However the error message appears at the time of disconnection from the server, i.e. exiting or disconnecting from sqlplus session, and at the time when a tnsping operation completes.

Problem exist with all client versions, i.e. 8.1, 9.2, 10GR1, 10GR2.

OID server itself, as well as Metadata Repository Database, are both using local names resolution, i.e. tnsnames.ora, and only the clients are setup to resolve tnsnames via ldap method.

There could be OID Replication configured and working. However replication is not directly related to the problem, and the issue can occur on standalone servers or before replication configuration. There is no any indication of errors on Metadata repository database side.

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.