Hi Robin,
LogMiner is a good tool for forensics, after the fact type work i.e to
find out when your junior dba dropped that table. It shouldn't be used
to do run of the mill daily work. It has a few deficiencies that are
hard to work around:
o - log miner user PGA memory so cannot be used in MTS environment
o - it doesn't fully support objects
o - doesn't support chained or migrated rows (fixed in 9i, not sure
which release.)
o - doesn't support analysis of clustered tables or indexes or IOT's
o - selects are not recorded in redo prior to 9i (again not sure which
release).
creating a trigger and a history table is far far more sensible and
robust.
hth
kind regards
Pete
--
Pete Finnigan
email:[EMAIL PROTECTED]
Web site: http://www.petefinnigan.com - Oracle security audit specialists
Book:Oracle security step-by-step Guide - see http://store.sans.org for details.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Pete Finnigan
INET: [EMAIL PROTECTED]
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
