RE: OEM Repository ; Collection time for Management Repository Views

From: Jorgensen, Finn <Finn.Jorgensen_at_constellation.com>
Date: Tue, 4 Sep 2012 15:06:48 -0400
Message-ID: <9CE162BC5ED2C643956B526A7EDE46FF0346CC7BE3D7_at_EXM-OMF-04.Ceg.Corp.Net>

Why would you do this using a table and some custom query? Why don't you just set the thresholds on the metric the way OEM is designed to do it?

Thanks,
Finn

-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Sukumar Kurup Sent: Friday, August 31, 2012 2:56 PM
To: oracle-l_at_freelists.org
Subject: OEM Repository ; Collection time for Management Repository Views

Hi,

I am trying to use Management Repository Views from the OEM repository database. In particular, extract TABLESPACE_SIZE, TABLESPACE_USED_SIZE from SYSMAN.MGMT$DB_TABLESPACES view and compare them against a table having thresholds (warn & page) for each database target in OEM, and generate alarms if the TABLESPACE_USED_SIZE  is more than the thresholds. 

The problem is with collection timestamp. It does not happen daily , and hence SYSMAN.MGMT$DB_TABLESPACES does not have the latest data. 

I opened a SR with Oracle support, but no help so far.

Can anyone please clarify :

1. When does the collection happen? Is it configurable ?  I see a wide range, spread across a week or so. 2. How can we force  collection for all databases at a specific time, before I run the report against the MGMT$DB_TABLESPACES view ?

Thanks,

Sukumar

--
http://www.freelists.org/webpage/oracle-l




>>> This e-mail and any attachments are confidential, may contain legal,

professional or other privileged information, and are intended solely for the
addressee.  If you are not the intended recipient, do not use the information
in this e-mail in any way, delete this e-mail and notify the sender. -IP2

--
http://www.freelists.org/webpage/oracle-l

Received on Tue Sep 04 2012 - 14:06:48 CDT