Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Q: IS SQL*Net for Linux buggy?
Hi experts,
as I wrote in an earlier article we still have connect problems on our Linux clients when connecting to some, not all, of our Oracle servers. There seems to be no functional dependence on the Server version or OS.
The result on the client are error messages
ORA-01017: invalid username/password; logon denied or ORA-01034: Oracle not available
although Oracle is running and username/password are correct.
When generating a SQL*Net trace file (via sqlnet.ora), we can compare a
working connect with a failed one:
After 2342 lines of diagnostics we find the first significant difference
between the two trace files:
nioqsm: entry
nsdo: cid=0, opcode=67, *bl=1, *what=18, uflgs=0x100, cflgs=0x3 nsdo: rank=64, nsctxrnk=0 nsdo: nsctx: state=8, flg=0x420d, mvd=0 nsdo: gtn=127, gtc=127, ptn=10, ptc=2047 nsdo: sending ATTN <<< instead of "sending DATA" nsdo: transport write error
nioqper: error from send-marker nioqper: nr err code: 0 nioqper: ns main err code: 12571 nioqper: ns (2) err code: 12560 nioqper: nt main err code: 504 nioqper: nt (2) err code: 0 nioqper: nt OS err code: 0
niqme: entry niqme: reporting ns (2) error: (12571) as rdbms err (12571) niqme: exit
This indicates an Oracle error 12571 which is - according to the documentation - not visible to the user but indicates a TNS:packet writer failure during data send.
Unfortunately we do not have a support contract for our Linux clients.
Obviously the problem must be due to SQL*Net: When we try to connect to these servers via JDBC everything works flawlessly!!!
Can anybody help me?
--
uwe.schneider_at_xlink.net
Received on Thu Nov 11 1999 - 04:02:44 CST