![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Problem Resolution Sure Solution 1632798.1 : Exadata and other Engineered Systems: ILOM Listed as a Dependent Target on the Wrong Host When Creating a Blackout
Created from <SR 3-8538859071> Applies to:Enterprise Manager for Exadata - Version 12.1.0.2.0 and laterOracle Exadata Hardware - Version 11.2.0.1 and later Oracle Database Appliance Software - Version 2.1.0.1 and later Oracle Exalogic Elastic Cloud Software - Version 2.0.0.0.0 and later Oracle SuperCluster M6-32 Hardware - Version All Versions and later Information in this document applies to any platform. SymptomsWhen attempting to create a Blackout on a DB node that is part of an Exadata Rack, the ILOM target for a different node may be listed as a dependent target. CauseThis is by design. The 12c Console assigns 2 agents per Exadata target (where an Exadata target can be a storage cell, ILOM, pdu ...etc). For example on a four node cluster: The db01 agent owns ILOM01 and ILOM03. SolutionFor easier future blackout management, you can select the Primary agent that monitors each ILOM target to match up with the target name. For example, in a two node environment, db01 agent owns both ILOMs. If we attempt to blackout node 1, then ILOM02 is listed as a dependent target:
We can change this by navigating to the Exadata Database Machine home page in EM, then select Monitoring Agents from the menu:
And you see the backup agent also changes:
Attachments This solution has no attachment |
||||||||||||
|