Hi,
We have setup oracle names server. Is there anyway i can force all the clients to use only ONAMES for address resolution? I want to block all other requests.
Thanks
Manohar
Printable View
Hi,
We have setup oracle names server. Is there anyway i can force all the clients to use only ONAMES for address resolution? I want to block all other requests.
Thanks
Manohar
No responses/ ideas on this???
Well, let me explain my whole case..
i dont want my users using TNSNAMES for names resolution and come to me saying i am unable to access a particular database if any changes occured. I want all users to use ONAMES first in names.directory_path.
Also, in a high availability environment, i can specify failover stuff in connection thru ONAMES but users using TNSNAMES not knowing the details can make ordinary connection.
Is there any way for the Listener to find out how a service name is resolved (using TNSNAMES/ONAMES/HOSTNAME..) and then block certain requests?
Although its some crazy idea, i just want to know if an option exists!!!
-mano
Here's a crazy idea: get rid of Oracle Names. It is deprecated in 9i. It was buggy to begin with, and it never really went anywhere. Gazillions of people use local naming, very successfully, all the time. You can have all your users use TNS_ADMIN. To make a change (e.g., a database moves to a different server), you change one word in one file. What's your problem with doing that?
Thats a totally crazy stecal idea!!
Its depricated in 10g not 9i and Oracle provides a clean method to upgrade it to a LDAP based server. And centralized administration has numerous advantages over local naming, and especially in a big organization like ours.
To make a change, u just change 1 word in 1 file - thats right, but has to be done on every single client.
what u suggested no solution, rather its like running away.
Go with what Stecal says, Oracle NAMES is a PITA.Quote:
Originally posted by manodba
Thats a totally crazy stecal idea!!
Its depricated in 10g not 9i and Oracle provides a clean method to upgrade it to a LDAP based server. And centralized administration has numerous advantages over local naming, and especially in a big organization like ours.
To make a change, u just change 1 word in 1 file - thats right, but has to be done on every single client.
what u suggested no solution, rather its like running away.
I dont understand, but i heard the same from some other sources.
any particular reason why it is such a PITA?
Don't u get it, because it doesn't work most of the times, and that's why Oracle itself is deprecating its usage.Quote:
Originally posted by manodba
I dont understand, but i heard the same from some other sources.
any particular reason why it is such a PITA?