Any of you guys ever run into the problem with 10.2.0.x databases having the V$SYSMETRIC tables future dated?? This causes Grid Control no problem of headaches. The future dated "data" gets sent to the grid control server in xml files. The grid control repository is unable to insert the data into the MGMT_METRICS_RAW table. Also, if you click on the performance graph for the affected target, it causes the Grid Control components to crash and restart (OC4J etc). Just curious if any of you have found a way to clear the V$SYSMETRIC tables without restarting the DB. I've been "playing" around with these parameters, but so far no luck. NAME VALUE DESCRIPTION UPDATE_COMMENT _swrf_test_action 0 test action parameter for SWRF _swrf_mmon_flush FALSE Enable/disable SWRF MMON FLushing _awr_corrupt_mode FALSE AWR Corrupt Mode _awr_restrict_mode FALSE AWR Restrict Mode _swrf_mmon_metrics FALSE Enable/disable SWRF MMON Metrics Collection _swrf_metric_frequent_mode TRUE Enable/disable SWRF Metric Frequent Mode Collection _awr_flush_threshold_metrics TRUE Enable/Disable Flushing AWR Workload Metrics _awr_flush_workload_metrics TRUE Enable/Disable Flushing AWR Workload Metrics _awr_disabled_flush_tables Disable flushing of specified AWR tables _swrf_on_disk_enabled TRUE Parameter to enable/disable SWRF _swrf_mmon_dbfus TRUE Enable/disable SWRF MMON DB Feature Usage _awr_mmon_cpuusage TRUE Enable/disable AWR MMON CPU Usage Tracking _swrf_test_dbfus FALSE Enable/disable DB Feature Usage Testing _awr_sql_child_limit 200 Setting for AWR SQL Child Limit Chris Taylor Sr. Oracle DBA Ingram Barge Company Nashville, TN 37205 Office: 615-517-3355 Cell: 615-354-4799 Email: chris.taylor@xxxxxxxxxxxxxxx