Hi Ashoke,
DB Control isn’t a replacement for Enterprise Manager. It is dependent upon
the database instance it runs on, so if the database goes down, the
notifications, etc. aren’t available. Cron jobs on a second box that can ping
for the database, check for the listener, etc. would be more reliable, but
again, they are dependent on the server up, but more robust than db control
that’s dependent on the database.
Even EM Express isn’t built as a replacement for Enterprise Manager. It simply
doesn’t have the framework to run independent of the database, (or notify of an
outage if the database is down.)
Hope this helps!
Kellyn
On Mar 29, 2017, at 5:14 PM, Ashoke Mandal <ramukam1983@xxxxxxxxx> wrote:
Hi Kellyn,
Thanks for your tips. But my database is still at 11.2.0.4. We are trying
migrate our 11g database from Solaris to Linux first and use the DB control
as an interim solution for database administration and monitoring. Once that
project is done then we would upgrade our 11g databases to 12C and could use
12 EM Express. So for now I was looking for the document or tips for DB
control on 11.2.0.4.
Sorry for the delayed response as I was on vacation for few days.
Ashoke
On Thu, Mar 23, 2017 at 7:55 AM, Kellyn Pot'Vin-Gorman <dbakevlar@xxxxxxxxx
<mailto:dbakevlar@xxxxxxxxx>> wrote:
Hi Niall,
Yes and I recommended Ashoke take Rich's advice as well after linking to the
documentation he requested...:)
Sent from myMail for iOS
Thursday, March 23, 2017, 5:21 AM -0600 from Niall Litchfield
<niall.litchfield@xxxxxxxxx <mailto:niall.litchfield@xxxxxxxxx>>:
Hi Kellyn
My understanding is that Ashoke went down the DB Control route because his
understanding was that OEM 12 didn't support databases on RHEL7. That might
be true of 12.1.0.3 but it isn't true of 12.1.0.5.
Rich - you were looking at the certification for the OMS - the correct search
would be for the agent
https://support.oracle.com/epmos/faces/CertifyResults?_adf.ctrl-state=10p5kx9y0f_4&searchCtx=st%255EANY%257Cpa%255Epi%255E932_Enterprise%2BManager%2BBase%2BPlatform%2B-%2BAgent%257Evi%255E335752%257Epln%255EAny%257E%257C&_afrLoop=456648746087497
<https://support.oracle.com/epmos/faces/CertifyResults?_adf.ctrl-state=10p5kx9y0f_4&searchCtx=st%255EANY%257Cpa%255Epi%255E932_Enterprise%2BManager%2BBase%2BPlatform%2B-%2BAgent%257Evi%255E335752%257Epln%255EAny%257E%257C&_afrLoop=456648746087497>
RHEL7 is a supported target for the agent.
Ashoke, I'd second the advice about investigating whether an OMS upgrade is
planned/acceptable - especially given the lifecycle stage that RHEL6 is in.
It's a long time since I used db control for management so take what I say
with a pinch of salt. My understanding is that you won't get notifications
when the db is down (a fairly serious flaw) but that you should in the other
cases. You might find
http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/11g/r2/2day_dba/monitoring/monitoring.htm
<http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/11g/r2/2day_dba/monitoring/monitoring.htm>
helpful as a resource for monitoring and notifications.
On Tue, Mar 21, 2017 at 6:09 PM, Kellyn Pot'Vin-Gorman <dbakevlar@xxxxxxxxx
<mailto:dbakevlar@xxxxxxxxx>> wrote:
Could we first verify that the original question is about DB Control, (aka
Enterprise Manager Express) and not the Enterprise Manager product that’s
installed on a separate repository, with a separate management service? If
it’s the former and not the latter, then these responses, although excellent
recommendations on what he should be installing, is not instance dependent
and wouldn’t explain why with the former, no notifications were received
about the database until the database, (and the locally installed repository)
were again, accessible.
Just a thought… :)
Best Regards,
Kellyn Pot’vin-Gorman
On Mar 21, 2017, at 9:55 AM, Rich J <rjoralist3@xxxxxxxxxxxxxxxxxxxxx
<mailto:rjoralist3@xxxxxxxxxxxxxxxxxxxxx>> wrote:
On 2017/03/21 10:42, Bertrand Guillaumin wrote:
Well it is true that RHEL7 is not supported in OEM 12.1.0.3 but it is inWhere did you find that info? I can't find RHEL7 in the Certifications of
OEM 12.1.0.5 so maybe ask your Grid Control Admin team if it is possible to
upgrade to the last 12c version of Cloud Control, which might be less
complicated than migrating to 13c.
OMS 12.1.0.5 in MOS. For those with an Oracle contract (link taken from
"Share" in the MOS Certifications screen):
https://support.oracle.com/epmos/faces/CertifyResults?_afrLoop=295719592217065&searchCtx=st%255EANY%257Cpa%255Epi%255E931_Enterprise%2BManager%2BBase%2BPlatform%2B-%2BOMS%257Evi%255E299128%257Epln%255EAny%257E%257C&_afrWindowMode=0
<https://support.oracle.com/epmos/faces/CertifyResults?_afrLoop=295719592217065&searchCtx=st%255EANY%257Cpa%255Epi%255E931_Enterprise%2BManager%2BBase%2BPlatform%2B-%2BOMS%257Evi%255E299128%257Epln%255EAny%257E%257C&_afrWindowMode=0>
There's no mention of any OS being a "managed target", so I suspect that if
the target database supports an OS, EM 12.1.0.5 will too. But I don't see
that here or in the drilldowns.
Rich
<blocked.gif>
--
Niall Litchfield
Oracle DBA
http://www.orawin.info ;<http://www.orawin.info/>
