This post is more than 5 years old
27 Posts
0
445
June 1st, 2009 06:00
DB agent for Oracle: DCP via proxy ineffective for DNS Aliases
Although initial discovery works, attempts to apply DCP to discovered database instances will NOT work unless there is a host agent that matches the HOST=HOSTXYZ statement in the proxy agent's TNSNAMES.ORA file.
See primus emc110201
Is there a workaround? I would sure hate having to rediscover... then have to rediscover AGAIN if the instance moves from one host to another.
See primus emc110201
Is there a workaround? I would sure hate having to rediscover... then have to rediscover AGAIN if the instance moves from one host to another.
No Events found!
cincypiper1
27 Posts
0
June 3rd, 2009 07:00
Proxy Discovery and use of Host Alias' = FAIL.
ECC can¿t use TNSNAMES HOST alias¿ because the result of:
Select HOST_NAME from V$INSTANCE
Is the hostname that is returned to ECC¿ and someone didn't realize that this is the hostname that will be used by the DCP. I sure wish ECC would have performed an NSLOOKUP to realize that the IP may be the same as the host running a Master Agent.
If you're doing proxy discovery, and are using an alias in TNSNAMES.ORA that is NOT the name of a host running a Master Agent... you are S.O.L.
Perhaps the EMC use cases didn't think that Database Discovery and subsequent Data Collection policies were linked. Golly gee that's too bad for anyone using DCP's on databases that are discovered via proxy.