Re: audit "delete from" and logminer

"Stephan Bressler" <sbresslerx_no_spam_at_arcor.de> wrote in message news:c0ig8n$3ts$1_at_news.mch.sbs.de...
> For all those searching for this via google:
> I've solved the problem. The delete statements are produced due to
> migrating rows caused by an update (moving the row is in fact a
> delete-insert-operation).
> So only the display of logmnr is wrong. Can be fixed by "ALTER DATABASE
> ADD SUPPLEMENTAL LOG DATA".
>
> Stephan

Just note that what your command does is to switch on minimal supplemental logging, and this only needs doing in 9i Release 2 and above, because before that (ie, 9iR1) it was the default.

It is one of Oracle's more bizarre decisions. This is what their new features course material says on the matter: "In most situations, you should at least enable minimal supplemental logging. [...] the default is NO supplemental logging and it must be specifically enabled."

Now, call me old fashioned, but I rather thought the idea of a default option was for it to represent what ought most commonly to happen. If you should switch this feeature on "in most situations", then why is it not the default??!

Anyway, yes: minimal supplemental logging is indeed something one generally ought to switch on, and from 9i R2 upwards, yes, you have to do so explicitly with the command you mention. It allows Log Miner to cope not only with migrated rows (as you found out) but also with clusters (index and hash, not RA...!).

Regards
HJR

-- 
--------------------------------------------
Oracle Insights: www.dizwell.com
--------------------------------------------