Re: Shell Script to Supress OEM alerts during shutdown immediate

From: Kellyn Pot'Vin-Gorman <dbakevlar_at_gmail.com>
Date: Sat, 26 Mar 2016 08:57:26 -0600
Message-ID: <CAN6wuX1hTHjnxtWV0Bk1iJ1VGr9N7Ujv0UbMJih92qcUqVD1BA_at_mail.gmail.com>

I'm going to make a few assumptions here, so please let me know if this is correct-

1. You begin maintenance and submit the blackout.
2. A flurry of alert notifications are sent and alarm the DBA on call
3. You are looking for a way to avoid these.

The reason behind this situation is that the blackout signal to the agent is controlled by the OMS in any verion 12.*. With the introduction of EM13c, the AGENT now controls the blackout, the communication to the OMS and then the agent availability. This change is valuable to correcting this notification issue that [I believe] you're describing.

Let me know, as I can tell you, EM13c will solve this if you're already planning on upgrading in the near future.

Kellyn Pot'Vin-Gorman
Consulting Member of Technical Team, SCP Oracle Enterprise Manager and Oracle Management Cloud

[image: Kellyn Pot'Vin on about.me]

Kellyn Pot'Vin-Gorman
about.me/dbakevlar
  <http://about.me/dbakevlar>

On Sat, Mar 26, 2016 at 7:35 AM, Arun Chugh <arun.chugh1610_at_gmail.com> wrote:

> Thanks for the suggestion.
>
> It would be great if anyone of you is having the procedure handy for this
> task.
>
> But one thing I want to mentioned here is that the database is running
> thru oracle user and emagent is running thru grid user, so we need to setup
> passwordless connection(ssh) for every server in order to run emcli command
> via procedure and it would be very tedious task for entire setup or correct
> me if I am wrong.
>
> Regards,
> Arun Chugh
>
> Regards,
> Arun Chugh
>
> Sent from my iPhone
>
> On 26-Mar-2016, at 5:59 PM, Niall Litchfield <niall.litchfield_at_gmail.com>
> wrote:
>
> You should
>
> a) have procedures and script(s) for shutting down databases that everyone
> follows
> b) include the necessary emcli commands in the scripts
>
> If someone doesn't follow procedure then I'd say that an alert and an
> on-call page is exactly what you want to happen.
>
>
> On Sat, Mar 26, 2016 at 10:54 AM, Arun Chugh <arun.chugh1610_at_gmail.com>
> wrote:
>
>> Hi,
>>
>> Thanks for the response.
>>
>> Yes, this could be one of the solution but what happens, we forget to put
>> the blackout in OEM and start getting the alerts for the same, so we want
>> the automatic solution of it, if any DBA put down the DB with "shutdown
>> immediate" we should not receive any alerts.
>>
>> Regards,
>> Arun Chugh
>>
>> Sent from my iPhone
>>
>> On 26-Mar-2016, at 4:05 PM, Ls Cheng <exriscer_at_gmail.com> wrote:
>>
>> Hi
>>
>> You mean Blackout? You can run emcli, this is an example
>>
>> emcli create_blackout \
>> -name="MAINTENANCE" \
>> -add_targets="XXXX:oracle_database;ZZZZ:oracle_listener" \
>> -reason="MAINTENANCE WINDOW" \
>> -schedule="frequency:once;duration:0:30"
>>
>> It blackouts 2 targets, one database and one listener for 30 minutes
>>
>> Regards
>>
>>
>>
>>
>> On Sat, Mar 26, 2016 at 11:25 AM, Arun Chugh <arun.chugh1610_at_gmail.com>
>> wrote:
>>
>>> Hello Team,
>>>
>>> Our requirement is to automatically supress the OEM alerts whenever the
>>> database undergoes "shutdown immediate" during the refresh or maintenance
>>> windows.
>>>
>>> If someone have any script, please share. Thanks !!!
>>>
>>> Regards,
>>> Arun Chugh
>>>
>>> Sent from my iPhone--
>>> http://www.freelists.org/webpage/oracle-l
>>>
>>>
>>>
>>
>
>
> --
> Niall Litchfield
> Oracle DBA
> http://www.orawin.info
>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Sat Mar 26 2016 - 15:57:26 CET