RESOLVED: GC metrics for plugin not rolling up

Thought I should note that I found an answer to my issue. It came from a note on:

http://forums.oracle.com/forums/thread.jspa?messageID=3504368

...which says that setting UPLOAD_ON_FETCH to TRUE in the default collection for a metric on a Grid Control plugin causes out-of-order timestamps, which in turn confuses the rollup process.

I did have that, so I removed it, dropped the target and plugin, imported the new version of the plugin archive, deployed the plugin and added the target. A day or two later and I have metrics rolled up. Yay!

Thanks for your help, Chris!

Rich

> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
> On Behalf Of Rich Jesse
> Sent: Tuesday, August 25, 2009 10:52 AM
> To: 'Oracle L'
> Subject: RE: GC metrics for plugin not rolling up
>
> Hey Chris,
>
> I think you're on the right track, because LAST_METRIC_LOAD_TIME is NULL and
> ROLLUP_TIMESTAMPS are '01/01/1900' for my targets.
>
> These targets are from a homegrown SQL Server plugin (can't justify the
> Oracle plugin cost), so it seems likely that the problem's on my end or
> there's a step I missed.
>
> Just looking at MGMT$TARGET_METRIC_COLLECTIONS, I see that my collections
> and metrics have a 1-1 relationship, whereas the Oracle DB default has many
> metrics per collection. I have a sneaking suspicion that I have my metrics
> defined incorrectly for GC to properly roll them up. Checking on that...
>
> Thanks much for your help, Chris!
>
> Rich
>
>
>> I had a similar problem.
>>
>> Do you have 10.2.0.3 databases you are monitoring? (I couldn't tell
>> from your email)
>>
>> There's a bug in 10.2.0.3 where the Metric Collection Timestamps get
>> future dated. Once these roll into GC, the last rollup timestamp gets
>> future dated inside GC and no more rollups occur.
>>
>> Really annoying.
>>
>> Anyway, query MGMT$TARGET and look at the LAST_METRIC_LOAD_TIME and
>> see if you have any future dated rows.
>>
>> Also check MGMT_TARGET_ROLLUP_TIMES and see if any ROLLUP_TIMESTAMPS
>> are > sysdate.
>>
>> Usually any future dated rows will appear as 2010, or 2011.

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