Well it is true that RHEL7 is not supported in OEM 12.1.0.3 but it is in 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.
Bertrand Guillaumin
De : oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] De la ;
part de Ashoke Mandal
Envoyé : mardi 21 mars 2017 12:35
À : Franky Weber Faust
Cc : peter.sharman@xxxxxxxxxxxxxx; ORACLE-L
Objet : Re: Fwd: OEM Database Control related questions
Frank,
Thanks for your suggestions. But I have an unique situation.
Currently my databases are on Solaris 10 and being monitored using OEM Grid
Control Oracle 11g. I am in the process of moving my databases from Solaris 10
to Red Hat Enterprise Linux 7. But databases on RHEL 7 is not supported by OEM
12C. Our Grid Control administration team has OEM 12.1.0.3 and that doesn't
support databases on RHEL 7 and said that RHEL 7 is supported on OEM 13C only.
So as an alternative short-term solution I am planning to use Database Control
on 11.2.0.4 database on RHEL 7 and trying to understand if I could monitor the
database and send alerts as it is done using Grid control.
If someone could help me in replying to my questions then that would be really
helpful.
Ashoke
On Tue, Mar 21, 2017 at 4:22 AM, Franky Weber Faust
<weber08weber@xxxxxxxxx<mailto:weber08weber@xxxxxxxxx>> wrote:
I think a better approach would be implementing a highly available OEM:
https://docs.oracle.com/cd/E24628_01/install.121/e24089/ha_setup.htm#EMADV10663
This way you minimize your risk of downtime in OEM.
Kind regards / Cordialmente / Saludos cordiales / Sincères amitiés / Mit
freundlichen Grüßen / Cordiali saluti,
Franky Weber Faust
Oracle DBA
Skype: franky.faust
[https://docs.google.com/uc?export=download&id=0B_N3mqs0olHhc0tYRkl5MlEwNlU&revid=0B_N3mqs0olHhR1JXS2tndlMwKzlTVllwQVVCTm1ud0RvWWVZPQ][https://docs.google.com/uc?id=0B_N3mqs0olHhVlZaSVNoTC1LdnM&export=download][https://docs.google.com/uc?export=download&id=0B_N3mqs0olHhSlZ5c0xaaXgzUUU&revid=0B_N3mqs0olHhWmFvWGJEeVJWK2k0bVVKb2MvR1JGVENjd3dJPQ][https://docs.google.com/uc?export=download&id=0B_N3mqs0olHhcllQQTJDbmZNa0U&revid=0B_N3mqs0olHhVW9udEtVOWlnRS8rUGJFMFVkN1BKbC94aHJzPQ]
2017-03-20 18:18 GMT-03:00
<peter.sharman@xxxxxxxxxxxxxx<mailto:peter.sharman@xxxxxxxxxxxxxx>>:
I'm fairly sure I saw this before, so what makes you think it didn't go through?
Pete
----- Original Message -----
From:
ramukam1983@xxxxxxxxx<mailto:ramukam1983@xxxxxxxxx>
To:
"ORACLE-L" <oracle-l@xxxxxxxxxxxxx<mailto:oracle-l@xxxxxxxxxxxxx>>
Cc:
Sent:
Mon, 20 Mar 2017 09:58:01 -0500
Subject:
Fwd: OEM Database Control related questions
Dear List members,
Any idea why my following post didn't go through? Ashoke
---------- Forwarded message ----------
From: Ashoke Mandal <ramukam1983@xxxxxxxxx<mailto:ramukam1983@xxxxxxxxx>>
Date: Fri, Mar 17, 2017 at 1:34 PM
Subject: OEM Database Control related questions
To: ORACLE-L <oracle-l@xxxxxxxxxxxxx<mailto:oracle-l@xxxxxxxxxxxxx>>
I have created a 11.2.0.4 database on RHEL 7.1 and configured DB Control. I
have few questions.
Q1. In OEM DB control the same database hosts the repository. So if this
database is down will there be any notification from DB control?
Q2. What all different monitoring is possible using DB Control?
Q3. I stopped the listener but the DB control didn't send any alert indicating
that the listener was down. But when I restarted the listener then it sent the
alerts. What does this mean?
Q4. Is there a document, which describes how to configure notification properly
and what all could be monitored?
Thanks,
Ashoke
