Re: merge statemet

Raj,

My understanding is that DBA_TABLE_MODIFICATIONS is based on the "good enough" assumption. Since its purpose is to simply track when statistics need refreshed, blood won't be spilled if the count is slightly off, so it doesn't have the heavy-duty locking requirements like transaction integrity does, but also doesn't have the performance overhead that requires. If you have a "blood will be spilled" situation, then MERGE probably doesn't meet your requirements.

Another idea would be to turn on tracing within your session, then create a program with something like Perl program that would scan the trace file for insert or update counts and get your count there. You would have to experiment to see which trace file options gave you the best results.

Dennis Williams

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