EM target naming
We have a large OEM deployment (11.1) and invariably, we have some database targets with duplicate names on different hosts.
Is there some way to force agents to name discovered targets to include a host identifier? (e.g., orcl_host1, orcl_host2)
I have seen times when the agent has automatically named a discovered instance / listener with that sort of convention, but by and large it does not work that way.
Solutions that will NOT work for us include changing the discovery scripts, renaming databases so that there are no actual duplicates.
Surely Oracle recognizes that organizations have databases with identical names on their networks?
Is there some way to force agents to name discovered targets to include a host identifier? (e.g., orcl_host1, orcl_host2)
I have seen times when the agent has automatically named a discovered instance / listener with that sort of convention, but by and large it does not work that way.
Solutions that will NOT work for us include changing the discovery scripts, renaming databases so that there are no actual duplicates.
Surely Oracle recognizes that organizations have databases with identical names on their networks?
0