AW: auditing tables

TNX for your answers.

What I need is exactly what Oracle doesn't support. Logging "who" changed "what" in a
special area of our database.

I think triggering the events will be much more specific and more easy to change.

In case all our applications use the same database and user, I am trying to check out
what application is changing monitored tables (i.e. c:\app\userapp\app.exe is changing
table1).
What do you think of that ??

greets

> Frank <

>Von: Rachel Carmichael [mailto:wisernet100_at_yahoo.com]
>
>what sort of information are you looking to audit? if you want any
>sort of detail, you are better off with triggers and possibly an audit
>table. Oracle doesn't record WHAT has been changed, just that the
>table was accessed. So you don't know the row etc...
>
>
>--- "Foelz.Frank" <Foelz.Frank_at_Scheidt-Bachmann.de> wrote:
>> Hi all,
>>
>> does anyone have experience in using Oracle's possibilities of
>> auditing
>> a database ??
>>
>> I am interested in performance questions i.e. is it a hughe loss of
>> performance
>> when auditing tables Inserts/Updates/Deletes. Should I use triggers
>> instead
>> ?
>>
>> any hints (comments, websites, etc...) are welcome.
>>
>> > Frank <
>> --

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Foelz.Frank
  INET: Foelz.Frank_at_Scheidt-Bachmann.de

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (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).