That's right, Spotlight was running on instance/database A showing no sessions, but from reading the alert log for instance/database B log switches were happening very fast. The mistake was having Spotlight connecting to instance/database A, when the person thought it was connecting to instance/database B. I've done the same kind of boneheaded mistakes. (e.g. dropping a table in the production database instead of the development database.) But in this case since it was someone else, I indulged in merciless ribbing. -----Original Message----- Niall Litchfield Oh I read that as "I've run my monitoring tool and it tells me for sure that there is nothing going on. " Obviously I'd never do that myself - oh no - I always set everything up just right and remember where I am at all times... Er I'll get me coat. Niall ----- Original Message ----- From: Jamadagni, Rajendra <rajendra.jamadagni@xxxxxxxx> why would a database monitoring tool cause so much data activity? hmmmm... makes me wonder ... Raj ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------