From: Wolfson Larry - lwolfs <>
Date: Thu, 27 Jan 2011 02:05:08 +0000
Message-ID: <>

Thanks Rich.
  I was thinking the same thing last nite when both Hemant Chitale & Tanel Poder nudged me to run a test. I did it on both servers. The original one ( and the one it was copied to ( And saw it was ignored. Tanel did the same.

  Frankly, I'd prefer an error message instead of someone copying a mistake. Probably lead to an argument.

Really appreciate your effort. I was low on sleep and working on priority items.

  Thanks again


-----Original Message-----
From: [] On Behalf Of Rich Jesse Sent: Wednesday, January 26, 2011 1:55 PM To:

Hey Larry,

> Guess I wasn't clear. Got a half dozen replies on how to use it in listener
> .ora

Sorry! That's what I get for replying to a reply... :(

Curiosity got the best of me, so I did some testing (using client against same DB version). I added a connection to my local TNSNAMES.ORA file:




tnsping and connections work fine, as expected. Now we add:

        (QUEUESIZE=32) ...immediately following the PORT spec. Again, tnsping and connections work fine. tnsping even shows the QUEUESIZE that was specified. Hmmm....let's get creative. I added this line after the errant QUEUESIZE:

        (SB_XLV_WINNER=GBP) Whatdya know? It worked! Starting up a client-side trace via SQLNET.ORA, I see the entries there, but they do not show up on the server listener's log.

I can glean from this overly-quaint test that unknown parameters are ignored. It could also cause the listener to crash for all I know. But this exercise suggests that the errant specs are most likely just silently ignored.

You can certainly repeat this exercise to see for yourself, perhaps expanding on the tracing, especially on the server side to determine exactly what's happening and/or not happening.




The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be legally

If the reader of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.

If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.

Thank You.

Received on Wed Jan 26 2011 - 20:05:08 CST

Original text of this message