Re: OID/LDAP problem - Any help with a fix would be appreciated

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert wrote:
> Oracle servers on Windows servers crash after converting to OID from TNS
> name resolution.
>
>
> Open a command prompt window (note: I have not seen this in the
> Windows version of SQL Plus or TOAD. You must use a DOS command
> prompt window). Make sure the windows workstation has SQLNET.ORA
> configuration that will use OID for TNS name resolution.
> Open a SQLPlus session to any database.
> Run a script that issues multiple "CONNECT uname/pwd_at_some-alias"
> commands.
> I use this environment often. I am running Windows XP on a laptop
> with an Oracle 10g client. At least once a day I will get a long
> series of messages that look like this:
>
> sgslufread: Hard error on read, OS error = 10054
> sgslufread: Hard error on read, OS error = 10054
> sgslufread: Hard error on read, OS error = 10054
> sgslufread: Hard error on read, OS error = 10054
> sgslufread: Hard error on read, OS error = 10054
>
> This error condition cannot be cleared short of CTRL-C to kill the
> SQL-Plus process. Microsoft MSDN and Google searches lead me to believe
> this is a WinSock error. MSDN says of this:
>
> 10054 WSAECONNRESET Connection reset by peer. An existing connection was
> forcibly closed by the remote host. This normally results if the peer
> application on the remote host is suddenly stopped, the host is
> rebooted, or the remote host uses a hard close (see setsockopt (Windows
> Sockets) for more information on the SO_LINGER option on the remote
> socket.) This error may also result if a connection was broken due to
> keep-alive activity detecting a failure while one or more operations are
> in progress. Operations that were in progress fail with WSAENETRESET.
> Subsequent operations fail with WSAECONNRESET.
>
>
> Some Observations:
>
> The database "hang" only occurs when database links are used.
>
> The database server only uses OID when invoking a database link.
>
> If OID is completely removed from the SQLNET.ORA you cannot make the
> server hang.
>
> If OID is present you can always make it hang by forcing a name
> resolution using OID. Within half an hour of running multiple queries
> through database links the windows server will hang.
>
> The WinSock error will not get written to any Oracle log file (it's a
> WinSock error, not an Oracle error).
>
> The WinSock error will not get written to any spool file (ditto).
>
> The WinSock error causes the client session to hang.
>
> Windows database servers can be made more resilient by granting them
> more resources and giving Oracle more control over resource management.
>

Search Metaclunk for "sgslufread" - three hits.

One doc suggests the version of the client may be the problem; patching 9iR2 and 10GR2 clients to the latest version would help. 10GR1 clients do not have this problem.

Post your versions.
- --
Regards,
Frank van Bortel

Top-posting is one way to shut me up...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iD8DBQFGvC9BLw8L4IAs830RAgwzAJ9m3z6GQPUvxJRtJwdo8P7yzfLjkQCdGIN5 EJ2GXE1IUb4iTXLi1Y5cLUY=
=pGQZ
-----END PGP SIGNATURE----- Received on Fri Aug 10 2007 - 04:26:25 CDT