Unable to Discover Targets on BRM Secondary Node
(Doc ID 2557880.1)
Last updated on AUGUST 28, 2019
Applies to:
Application Management Pack for Oracle Communications - Version 13.1.1.1.0 and laterInformation in this document applies to any platform.
Goal
In a multi-DB BRM setup, a server has been configured as primary node for one schema. The same server has been configured as secondary of 2 other schemas. Using "Configure Auto Discovery", all BRM processes are being discovered and then promoted.
This works for the primary node and one of the secondary nodes, but no processes are getting discovered when discovering the processes on the other secondary node. After clicking the "discover now", the server has been highlighted, but no processes are discovered.
No error is displayed on the screen and no error is present in "gcagent.log"
How to resolve this issue?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |