Re: TNS alias synonym entry

That's my interpretation as well.

I would be defining a "MONIT" service on each database server, and then using the local TNSNAMES on the (presumably app) servers to provide resolution for that service. Does this not work for some reason that is as yet unexplained.

On Wed, May 27, 2020 at 10:29 AM Norman Dunbar <oracle_at_dunbar-it.co.uk> wrote:

> On 27/05/2020 00:26, Mladen Gogala wrote:
> > Yes, it is possible to alias a TNS connection name. It's done like this:
> >
> > ...
> >
> > *As you can see, both TNS entries work as advertised. I'm not quite sure
> > what are you trying to do with "MONIT" entries?*
> >
>
> I think the OP has a couple of servers and wants to set up a local
> tnsnames.ora on each pointing a tnsnames alias at an LDAP "alias". It
> seems that the two servers both have a database DB01 and DB02 defined in
> LDAP.
>
> The OP wants to set up a new alias, pointing at either DB01 or DB02
> depending on which server is logged in to, but using the same alias --
> so MONIT on server01 points at DB01, while MONIT on server02 points at
> DB02, but using the LDAP configuration as opposed to hard coding the
> full details in tnsnames.ora.
>
> I don't do LDAP, so I don't know if it can be done, I don't think so but
> given my motto is "don't think, find out", I'm not about to start guessing!
>
>
> HTH
>
> Cheers,
> Norm.
>
> --
> Norman Dunbar
> Dunbar IT Consultants Ltd
>
> Registered address:
> 27a Lidget Hill
> Pudsey
> West Yorkshire
> United Kingdom
> LS28 7LG
>
> Company Number: 05132767
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

-- 
Niall Litchfield
Oracle DBA
http://www.orawin.info

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