EM 12c, EM 13c : OS Command Notification Script is Being Executed Only on One of the OMS Nodes in a Multi-OMS setup
(Doc ID 1514173.1)
Last updated on NOVEMBER 22, 2019
Applies to:Enterprise Manager Base Platform - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Checked for relevance on 06-Aug-2014
Using a multi-OMS setup, for example:
Server OMSA is the primary OMS where Adminserver is configured as well.
Server OMSB is the additional OMS.
'OS Command' notification method has been configured to execute a script named 12c_oem_notify.ksh and an incident rule has been configured to invoke this notification method when certain events are generated. The script is physically present on both the OMS machines in the same location: /home/oracle/scripts directory and it echos the event's environment variables to a log file on the OMS machine itself. So, when the 12c_oem_notify.ksh script is executed, a time-based log file is created on the OMS machine.
It was noticed that when the OMSA is shutdown, the script is not executed i.e there are no time-based logs created on the OMSB machine.
Also, the <EM_INSTANCE_BASE>/sysman/log/emctl.msg file shows:
This issue could also occur in a multi-OMS setup with more than 2 OMS.
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