RE: sqlnet.ora and tcp node checking on issue

  • From: "Newman, Christopher" <cjnewman@xxxxxxxxxxxxx>
  • To: <QuijadJC@xxxxxxxxxxxxxxx>, "Jared Still" <jkstill@xxxxxxxxx>
  • Date: Wed, 14 Jan 2009 19:20:19 -0600

node checking doesn't allow wildcards, so if you have clients using DHCP, 
better to use a firewall instead.  The built in mechanism is more appropriate 
for database which are only accessed by a few application nodes.

- Chris

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx on behalf of QuijadaReina, Julio C
Sent: Wed 1/14/2009 7:17 PM
To: Jared Still
Cc: oracle-l@xxxxxxxxxxxxx
Subject: RE: sqlnet.ora and tcp node checking on issue
This particular client uses DHCP. Our Systems guys would be able to reserve the 
IP for this machine, but I was most interested on whether Oracle has a fix for 
it. I have not been able to find anything on ML site nor on the web.

From: Jared Still [jkstill@xxxxxxxxx]
Sent: Wednesday, January 14, 2009 5:37 PM
To: QuijadaReina, Julio C
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: sqlnet.ora and tcp node checking on issue

On Wed, Jan 14, 2009 at 11:03 AM, QuijadaReina, Julio C 
<QuijadJC@xxxxxxxxxxxxxxx<mailto:QuijadJC@xxxxxxxxxxxxxxx>> wrote:

Has anyone run into issues with the listener not starting when sqlnet.ora 
includes tcp node checking? It appears that the problem is a computer name that 
is not resolvable through DNS - or that it just happens to be turned off at the 
time. I am using this setting as part of a security strategy to only allow 
certain clients direct access to the database servers.

If you're concerned enough to use tcp node checking, you should probably
consider using IP addresses rather than server names.

Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist



Other related posts: