Re: SQLNet.ora per Listener?
- From: Frits Hoogland <frits.hoogland@xxxxxxxxx>
- To: japplewhite@xxxxxxxxxxxxx
- Date: Tue, 21 Apr 2009 00:01:06 +0200
how about setting TNS_ADMIN to a listener specific location per listener?
frits
On Mon, Apr 20, 2009 at 10:12 PM, <japplewhite@xxxxxxxxxxxxx> wrote:
>
> 9i on HP-UX and 10g on Linux.
>
> Basic question: Can you somehow tie a particular sqlnet.ora file to a
> specific listener for a database that has two Listeners? I've looked in the
> docs and everywhere else I can think of and I can't find that you can
> somehow specify that a sqlnet.ora file applies to only a specific Listener,
> it applies to all Listeners in that ORACLE_HOME. The only way that my
> little brain has come up with is to create another ORACLE_HOME and have a
> Listener there with its own sqlnet.ora.
>
> What we have is a Student Information database that is accessed
> District-wide via our internal WAN / LAN. It has a Listener on port 1521.
> We've had this setup for years. We also allow selected access to that
> database from the Internet. We opened up another port (not 1521 or any of
> the "usual" ones) in the firewall and we have a second Listener on that
> port. The sqlnet on the Client App server in the DMZ requires encryption,
> etc. via the parameters specific to those security settings. We'd like to
> require the matching encryption, etc. for any traffic coming to the
> non-standard Listener, but the single sqlnet.ora file on the server would
> apply to our internal Listener as well, killing our internal Users. For
> now, we only have the security settings Accepted, not Required, on the
> server.
>
> Am I an idiot? I've done the standard setup of Listeners lots and lots
> over the years but am not well-versed in unusual setups or Advanced
> Security. Is there a relatively simple way to do what we want or is the
> separate ORACLE_HOME the ticket? Any guidance would be appreciated.
>
> Thanks.
>
> Jack C. Applewhite - Database Administrator
> Austin I.S.D. - MIS Department
> 512.414.9715 (wk) / 512.935.5929 (pager)
>
Other related posts:
