Too bad Steve Adams' site is not available, cuz that's
the place to be.
He says it better than I can, so I've appended a bit
of info from him. I'd suggest getting to Steve's site
as soon as it's up.
We have monitoring enabled on our 9.2.0.4 database,
but it's not currently heavily used. But so
The number of rows affected by an SQL statement
is something that has been available to Oracle for
a long time. Monitoring just records that number in
a memory structure.
I'd guess the memory structure is a hash table, and
there are no latches protecting it (so I've heard, and
I can't see any in
Especially on high transaction tables? I dont have any numbers for transactions/second
since we are not live. Any known issues? how does the monitoring work? Does it use an
internal trigger and then use SQL to write the data? or does the monitoring data
bypass the SQL layer and get written direc
