RE: TNSNAMES.ORA QUEUESIZE?

  • From: Wolfson Larry - lwolfs <lawrence.wolfson@xxxxxxxxxx>
  • To: "rjoralist2@xxxxxxxxxxxxxxxxxxxxx" <rjoralist2@xxxxxxxxxxxxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 27 Jan 2011 02:05:08 +0000

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 (10.2.0.4) and the one it was 
copied to (11.2.0.2).
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
        Larry

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Rich Jesse
Sent: Wednesday, January 26, 2011 1:55 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: TNSNAMES.ORA QUEUESIZE?

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 10.1.0.5 client
against same DB version).  I added a connection to my local TNSNAMES.ORA
file:

OTNSTEST=
  (DESCRIPTION=
    (ADDRESS=
      (PROTOCOL=TCP)
      (HOST=192.168.101.101)
      (PORT=1521)
    )
    (CONNECT_DATA=
      (SERVICE=mytestdb)
    )
  )

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.

Enjoy!

Rich


--
http://www.freelists.org/webpage/oracle-l



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

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.
****************************************************************************

Other related posts: