Re: OID/LDAP problem - Any help with a fix would be appreciated
- From: "Robert" <b126775@xxxxxxxxx>
- Date: Wed, 15 Aug 2007 15:32:43 GMT
Thank you Frank, I read the metalink articles. We are still looking. My
analysis at this point suggests a configuration problem but we have not
found the cause yet. We are using a tracing tool which shows "the virtual
circuit was terminated due to a time out or other failure". We are unsing
Oracle 9.2.0.6 on a Win2k host.
"Frank van Bortel" <frank.van.bortel@xxxxxxxxx> wrote in message
news:f9hfrd$o67$1@xxxxxxxxxxxxxxxxxxxxxxxxxx
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Robert wrote:
Oracle servers on Windows servers crash after converting to OID from TNSSearch Metaclunk for "sgslufread" - three hits.
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@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.
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-----
.
- References:
- Re: OID/LDAP problem - Any help with a fix would be appreciated
- From: Frank van Bortel
- Re: OID/LDAP problem - Any help with a fix would be appreciated
- Prev by Date: Re: Core files of Oracle and Security
- Next by Date: Re: above average CPU usage
- Previous by thread: Re: OID/LDAP problem - Any help with a fix would be appreciated
- Next by thread: Re: OID/LDAP problem - Any help with a fix would be appreciated
- Index(es):
Relevant Pages
|
