There is typically a delay of up two two or three hours before you will see
these changes. The modifications are intermittantly written to a structure in
memory and then periodically written down to the tab_modifications table. If
this wern't the case, you'd have massive contention on the table with
monitoring turned on because every session changing that table would have to
serialize to write their modification data. A couple side effects of this are
1) rollbacks are still counted as modifications 2) no locks are taken out on
the structure so two processes can overwrite oneanothers' data if they hit at
exactly the same time. Basically that table is supposed to give an
approximation of what is going on with the base tables being monitored.
"a" <dbadba62_at_hotmail.com> wrote in message
news:%75%7.22729$tz1.19838_at_nwrddc01.gnilink.net...
> After I alter table monitoring as the owner of the table, I insert one row
> into the table, and then commit. After that, I select count(*) form
> sys.dba_tab_modifications as system, the result is 0.
>
> Is there anything I did wrong? How do you collect the info after you alter
> table monitoring?
>
> I am using Oracle 817 on Solaris.
>
> Thanks for your help.
--
Posted via Mailgate.ORG Server - http://www.Mailgate.ORG
Received on Wed Jan 09 2002 - 22:21:46 CST
