RE: Use EM 11g Grid Control (or 12c) versus opatch to save time with quarterly PSUs?
- From: "Ramadoss, Karthik" <Karthik.Ramadoss@xxxxxxxxxxxxxxxx>
- To: "'mschmitt@xxxxxxxxxxxx'" <mschmitt@xxxxxxxxxxxx>, oracle-l <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 25 Jul 2012 12:30:16 +0000
We have been dealing with this blackout issue as well. I was thrilled to find
this morning that there looks to be a patch to fix this issue in 12.1.0.1.
Patch 13584107: CRITICAL ALERT IS TRIGGERED WHEN BLACKOUT ENDED EVEN THOUGH
TARGET REMAIN UP
Thanks,
Karthik Ramadoss
DBA Lead, Accident Fund
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Michael Schmitt
Sent: Friday, July 20, 2012 2:07 PM
To: oracle-l
Subject: RE: Use EM 11g Grid Control (or 12c) versus opatch to save time with
quarterly PSUs?
We have been moving off of EM10g and to EM12c and have been happy with the it.
I would recommend the upgrade to EM12c, except there is an issue that causes an
alert to get sent out when a blackout ends. I believe this is a showstopper to
anyone who uses EM12c to page and utilizes some cold backups as well. It has
caused us to keep our production in EM10g while monitoring DEV in EM12c. If
anyone knows a workaround to this issue please let me know.
I would love to try out the automated patching features, but unfortunately we
are not licensed for it. It does not look like you are licensed for it either
since I do not believe it is not included in the diagnostics + tunning packs.
Please see "Lifecycle management pack"
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Dana Nibby
Sent: Friday, July 20, 2012 3:39 AM
To: oracle-l
Subject: Use EM 11g Grid Control (or 12c) versus opatch to save time with
quarterly PSUs?
For a shop with 30 instances on a dozen hosts, would it make sense to use Grid
Control EM 11g or EM 12c to deploy PSUs? Is one more reliable than the other?
Our approach is opatch. And each quarter it takes much labor, time, and
frustration to complete. We have an aging but functioning EM 10g Grid Control
infrastructure. Never tried to use it for patching. But we have the diagnostic
+ tuning packs for our instances. So we should be licensed to use this
technology for PSUs.
When I've suggested we upgrade to EM 11g or EM 12c I typically get a response
of the variety "we don't have time for that" (e.g. researching, testing, and
then deploying EM 11g or 12c). My opinion? We don't have time *not* to do this.
It's an investment in efficiency and I take the long view. It gives me no
pleasure, and much pain, to repeatedly hear "we don't have time to learn X"
when X is something that will improve efficiency, customer service, excellence,
etc.
Sound familiar to anyone? If so, how have you played it short of finding
another gig? I may try to track all staff hours involved with getting July PSUs
completed to have some baseline metrics--everyone from the DBA team (reading
about quirks and idiosyncracies of various PSUs on particular platforms/Oracle
releases) to sysadmins to ops to managers, etc. In the time it takes to
coordinate and execute the work using opatch, I can't help but wonder if we
could have set-up at least EM 11g Grid Control in preparation for the next
quarter. For now, I'm trying to socialize a January 1st, 2013 date to deploy EM
11g or EM 12c for patching and other goodness. You know, try to implement it,
at least on some Production Floor dev and test boxes, when things have slowed
down and most people (here in the U.S.) will be out of the office.
It may be that patching with EM 11g or EM 12c isn't patching nirvana. I'm not
sure precisely how many staff hours (and frustration) it might save. Would love
to hear personal stories here. But I'll settle for incremental improvement so
we can move on to work higher up the value chain. If all my instances got moved
to The Cloud, for instance, patching is a task I wouldn't miss.
Finally, are there cases in which folks would recommend sticking with opatch
versus applying patches with Grid/Cloud Control? I imagine in very small shops
using opatch would be fine. But in shops as large as the one I've described or
larger--when DBAs are managing hundreds or thousands of instances--I can't
imagine using opatch. Not unless it is fully scripted in some way.
If no one bites, and persists in saying "we don't have time for this", I'm
going to make time on my home sandbox and work everything out there on my own
time. Feels like The Right Thing To Do. Because an operational DBA group could
always say "we don't have time for X." It's a bit like saying "I don't have
money to invest in a retirement plan." Decades pass and then you find you have
to work forever...
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
