I didn't see this message come through, so my apologies if it is a duplicate post <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< I have a few test databases that are on the same box. They are reporting several hundred "Concurrency" alerts in DBA_ALERT_HISTORY each day. My first thought is that since the databases are rarely used, some scheduled jobs are triggering these alerts and I probably need to tweak the thresholds. The customer does not have Grid control or the database console setup for these databases. A sample of recent records in dba_alert_history is shown below. Can somebody explain to me why the alert is triggered for this metric when all of my warning_values for "Database Time Spent Waiting (%) are set to 30 (in DBA_THRESHOLDS)? And why do I see so many alerts for a value of 0? It would make sense to see a 0 when the alert is cleared, but I don't understand why I see so many zeros in a row. Thank you, Jay REASON TO_CHAR(TIME_SUG METRIC_VALUE ------------------------------------------------------------------------------------------ ---------------- ------------ Metrics "Database Time Spent Waiting (%)" is at 0 for event class "Concurrency" 04-22-2010 13:49 0 Metrics "Database Time Spent Waiting (%)" is at 0 for event class "Concurrency" 04-22-2010 13:38 0 Metrics "Database Time Spent Waiting (%)" is at 0 for event class "Concurrency" 04-22-2010 13:34 0 Metrics "Database Time Spent Waiting (%)" is at 0 for event class "Concurrency" 04-22-2010 13:16 0 Metrics "Database Time Spent Waiting (%)" is at 0 for event class "Concurrency" 04-22-2010 13:13 0 Metrics "Database Time Spent Waiting (%)" is at 0 for event class "Concurrency" 04-22-2010 13:11 0 Metrics "Database Time Spent Waiting (%)" is at 28.40031 for event class "Concurrency" 04-22-2010 13:05 28.4003091