Anyone have DISABLE_OOB=ON set in sqlnet.ora?

From: Rich Jesse <rjoralist3_at_society.servebeer.com>
Date: Wed, 8 Jul 2015 08:14:23 -0500 (CDT)
Message-ID: <4f3f0d8a1db6f5da92d64a35ccc2208e.squirrel_at_society.servebeer.com>

Hey all,

We've been getting sporadic ORA-3137 errors on our year-old 11.2.0.3 DB since testing started. It doesn't appear to be a showstopper, as I can't attribute any user complaints directly to these happening, so I've been mostly ignoring these when they happen.

This week, I had an instance where the first parameter of the error changed from [12333] to [12271], so I thought it worth an SR. The tech pointed me to MOS 1927582.1 that has a workaround of setting DISABLE_OOB=ON in the sqlnet.ora of the client.

Has anyone used this? I can't find any negatives or side effects on MOS about disabling it, but then why does OOB checking exist? It's like the equivalent of an appendix in humans...

TIA!
Rich

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

Received on Wed Jul 08 2015 - 15:14:23 CEST

This message: [ Message body ]
Next message: Kim Berg Hansen: "Re: Oracle 12c: ALL_SYNONYMS excludes Objects behind DB_LINKs"
Previous message: Powell, Mark: "RE: Oracle 12c: ALL_SYNONYMS excludes Objects behind DB_LINKs"
Next in thread: Peter Hitchman: "Re: Anyone have DISABLE_OOB=ON set in sqlnet.ora?"
Reply: Peter Hitchman: "Re: Anyone have DISABLE_OOB=ON set in sqlnet.ora?"
Maybe reply: Rich J: "Re: Anyone have DISABLE_OOB=ON set in sqlnet.ora?"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message