Re: Auditing: Trigger or Audit_Trail?

On Mon, 01 Mar 2004 20:15:01 GMT, in comp.databases.oracle.server, Teresa Redmond <NJZLIRWUWYGI_at_spammotel.com> scribbled:

>On Mon, 1 Mar 2004 21:05:55 +0100, in comp.databases.oracle.server,
>"Michel Cadot" <micadot{at}altern{dot}org> scribbled:
>
>>
>>"Teresa Redmond" <NJZLIRWUWYGI_at_spammotel.com> a écrit dans le message de
>>news:bf8a96e8f85fdf98a5cd3fa61bf74075_at_news.teranews.com...
>
>>> Unfortunately, after
>>> performing 'audit delete, update on schema.table' for all tables,
>>> adding some records to "schema.atest", then updating and deleting from
>>> atest, I got "no rows selected" when running the above script.
>>
>>You have to set AUDIT_TRAIL init parameter to DB.
>>This is a static parameter, so you have to restart the instance.
>
>*smacks hand to forehead*. I totally forgot about that. Thanks...

...and I still can't get it to work. Changed the init parameter, restarted Oracle, made sure init.ora matches, put in some data, commit; updated some data, commit; ran the script, no rows selected. I even ran the audit command again. Sigh.

Any idea of what I'm not doing?

Thanks!

-- 
Teresa Redmond
Programmer/Analyst III
Anteon Corporation
tredmond at anteon dot com