Re: Trigger SMON to dump table statistics to ALL_TAB_MODIFICATIONS

The issue here was the object was incorrect. The SQL was an INSERT into table A, the query was showing an INSERT into table B.

On 6/6/07, Alexander Fatkulin <afatkulin_at_gmail.com> wrote:
>
> The SGA monitoring counters are not fully serialized (imagine an
> overhead otherwise).
>
> The numbers are "about" and not 100% correct. You can insert and later
> rollback - the counters will add up.
>

--
http://www.freelists.org/webpage/oracle-l