Re: Grid alerts
- From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- To: mati.vapper@xxxxxxxxx
- Date: Thu, 2 Jul 2009 14:25:32 +0100
At the risk of being another person recommending an upgrade.....
The 'correct' solution for this is to create a monitoring template for your
database instance targets, that doesn't include those metrics. Then you can
apply the same metric to multiple targets of the same type across your
enterprise. Unfortunately before 10.2.0.5 Oracle's definition of a
'template' is different to every other use of the word under the sun. In
previous versions if you apply a template to a target then metrics that are
set in the template are updated, but metrics that are unset in the template
are not changed at all on the target, Starting with 10.2.0.5 when you apply
a monitoring template to a target you actually can get that monitoring
template in effect on the target. In prior versions you'd have to define all
metrics, some with mad values, or else remove unwanted metrics from each
target before you applied the template.
so I'd say go with 10.2.0.5 and use the template functionality. There are
other nice things in 10.2.0.5 that make it a good upgrade as well by the
way.
Niall
On Thu, Jul 2, 2009 at 11:42 AM, Mati Vapper <mati.vapper@xxxxxxxxx> wrote:
> Hi!
> I have a question about OEM Grid Control. We have over 150 production DB
> targets and normal alerts for some DB-s are out of temp and out of undo
> errors.
> It's just happening and there is nothing that DBA could handle.
> My question is: how to disable temp and undo space checks for all DB
> targets in Grid?
> (Just don't want to wake up after every hour and read sms's about how
> oracle is unable to extend temp segment)
>
> I tried to use dbms_server_alert package:
>
> DBMS_SERVER_ALERT.SET_THRESHOLD(DBMS_SERVER_ALERT.TABLESPACE_PCT_FULL,DBMS_SERVER_ALERT.OPERATOR_GT,'90',
>
> DBMS_SERVER_ALERT.OPERATOR_GT,'100',1,1,'ORASID',DBMS_SERVER_ALERT.OBJECT_TYPE_TABLESPACE,'TEMP');
>
> It didn't work on grid side, but it worked on 10.2 database side. Still
> it's a bit annoyng to apply this in every monitored database.
> And anyway there is no such package in older DB-s, about 70% of our systems
> are older than 10.2. So its not a solution.
>
> Is there anything else to try/to do?
>
> --
> Cheers,
> Mati Vapper,
> Oracle DBA.
>
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
Other related posts:
