Re: Anyone have DISABLE_OOB=ON set in sqlnet.ora?

From: Rich J <rjoralist3_at_society.servebeer.com>
Date: Thu, 16 Jul 2015 14:04:18 -0500
Message-ID: <9a17a08f2010c5fd51447c859765b5fe_at_society.servebeer.com>


 

On 2015/07/16 13:20, Øyvind Isene wrote:

> We have set this at a customer because their network equipment apparently strips off the "urgent flag". I haven't seen any negative effects, but I guess we would have to measure it in order to notice. I have seen this parameter as a remedy for other issues as well at MOS.
>
> 2015-07-14 22:57 GMT+02:00 Peter Hitchman <pjhoraclel_at_gmail.com>:
>

>> Hi 
>> All you are doing is stopping this client from sending a break via a different channel to the server. So it might make things a bit less efficient from the clients point of view, I guess it depends on exactly what the client is doing. 
>> Does the analyst think this is just a 11.2.0.3 issue combined with the type of client you are using? 
>> I saw issues like this years ago, back in the Oracle 8.0 days, but from memory the disable_oob was a temp fix because the real issue was a client using oci that as not up to date enough.

Thanks Pete and Øyvind! It looks like I'll be starting to test this to see if it might take care of those errors I've been seeing.

Rich

--
http://www.freelists.org/webpage/oracle-l
Received on Thu Jul 16 2015 - 21:04:18 CEST

Original text of this message