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. -- //www.freelists.org/webpage/oracle-l