Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Logminer Question
Jim Conboy wrote:
Why not turn on the built-in auditing features?
>>>
Three reasons:
1) Because Oracle auditing traces access to tables or objects, but
not to specific records within the table; not sure if logminer can satisfy this either, hence the question 2) Why incur the additional overhead of turning on auditing if
the redo logs already contain sufficient data to satisfy auditing needs? It seems to me there's a lot of overlap between Oracle's auditing system and the information in the redo logs (?). 3) Auditing requires a lot of additional space; this is in addition to the
space already used for archiving redo logs.
Original question:
>>
Hello,
My env is Oracle 8.1.6 on Solaris 2.7.
I know logminer can be used to track inserts, updates, deletes, but can it also be used to track select statements? I'm thinking of a situation where we want to identify everyone who accessed a certain record or a group of records in an Oracle table in any way, even if they only viewed records.
Given a certain record in some table identified by some unique key, is there any way to search v$logmnr_contents to find anyone who has viewed that record? Received on Fri Jan 12 2001 - 12:45:00 CST
![]() |
![]() |