RE: How do you rotate OEM 12c paging different DBAs on the team....

From: Patterson, Joel <>
Date: Mon, 14 Apr 2014 16:15:34 -0400
Message-ID: <C1117B1AA0340645894671E09A7891F715F4599991_at_EIHQEXVM2.ei.local>

Nice idea,

For phones:
I have been 24/7 for years, so I don’t rotate at the moment, but in the past I found that two weeks on, and Wed to Wed to work great, especially around holidays. And it’s a lot longer before it comes around again.

The person going ‘off’ call could be responsible for forwarding the number to the next DBA’s phone on Wed morning.

So many Holidays fall on Monday and Friday, that it makes it hard to schedule a three day weekend vacation.

If you physically ‘hand’ a phone to the next DBA, you would virtually have to do it on a weekday, and Monday holidays make it so that can’t happen.

You can ‘forward’ a number to next DBA phone – and it would not matter if it is Friday, Saturday, Sunday or Monday… but who even wants to make sure they are up every Sat morning to forward it.

Well, that’s my Ç.02

From: [] On Behalf Of Cunningham, Mike Sent: Monday, April 14, 2014 4:12 PM
Subject: RE: How do you rotate OEM 12c paging different DBAs on the team....

We use two layers of alerts setup like this.

  1. WARNINGS get emails sent to all DBA’s. The on-call DBA should be checking emails. There are times when the on-call DBA may need to step away and asks another to watch his back and that is why we all get the emails. The subject line is formatted to make easy sorting. This might be something like filesystem >= 85%.
  2. CRITICAL alerts send text messages to all DBA’s. This is valuable because my phone is sent to silent for emails, but makes an obnoxious sound for text messages and I will pay attention to them. Regardless of on-call or not our team will communicate and figure out who is attending to the alert so we know someone is on it. This is something like blocking locks, filesystem >= 95%, etc. In our environment if we get a text there will also be an email with more detailed information.

Michael Cunningham
Senior Database Administrator
The Doctors' Company
707.226.0221 - desk
707.337.0184 - cell

Joel Patterson
Sr. Database Administrator | Enterprise Integration Phone: 904-928-2790 | Fax: 904-733-4916<>


[]<> [] <!/entint> [] <> [] <>

This message (and any associated files) is intended only for the use of the addressee and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient, you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from us may be monitored. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company. [v.1.1] From:<> [] On Behalf Of Chris Grabowy Sent: Monday, April 14, 2014 12:44 PM
Subject: How do you rotate OEM 12c paging different DBAs on the team....

We are in the middle of setting up OEM 12c. I setup a separate Incident Rule set for the production group and critical alerts.

I am thinking about setting up a different OEM user whose email is the texting addresses of the DBA team.

We do not carry a pager but we have corporate Blackberrys. So I am trying to determine how we would rotate who receives the page dependent on who is on call.

So I am wondering what other sites do? Any pointers? Links? Ideas?

TIA. Chris

Confidentiality Notice: This message and any attachments hereto may contain confidential and privileged communications or information and/or attorney client communications or work-product protected by law. The information contained herein is transmitted for the sole use of the intended recipient(s). If you are not the intended recipient or designated agent of the recipient of such information, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited and may subject you to penalties under federal and/or state law. If you received this e-mail in error, please notify the sender immediately and permanently delete this e-mail.

Received on Mon Apr 14 2014 - 22:15:34 CEST

Original text of this message