RE: Auditing, how to capture sql statement issued

You're right, I was just thinking about "normal" data changes. LogMiner is good stuff but it is NOT a complete audit trail of all database activity.

-----Original Message-----
From: root_at_fatcity.com [mailto:root_at_fatcity.com]On Behalf Of Rachel Carmichael
Sent: Tuesday, January 16, 2001 11:56 AM To: Multiple recipients of list ORACLE-L Subject: RE: Auditing, how to capture sql statement issued

unfortunately, as Joe Testa said last week, logminer doesn't capture select statements (or any DML done as unrecoverable).

So if Rick is looking to catch someone illegally reading data he can't through logminer

Rachel

>From: "Steve Orr" <sorr_at_arzoo.com>
>Reply-To: ORACLE-L_at_fatcity.com
>To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
>Subject: RE: Auditing, how to capture sql statement issued
>Date: Tue, 16 Jan 2001 09:31:03 -0800
>
>If you implement log miner you can query v$logmnr_contents from SQL*Plus.
>You can set this up to give a complete audit trail of all SQL.
>
>Steve Orr
>
>
>-----Original Message-----
>T (Richard)
>Sent: Tuesday, January 16, 2001 8:41 AM
>To: Multiple recipients of list ORACLE-L
>
>
>I want to capture the sql statements for auditing purposes not for reuse of
>sql statements.
>
>Thanks
>Rick
>
> > -----Original Message-----
> > From: Sachin Puri [SMTP:sachin_at_siworldwide.com]
> > Sent: Tuesday, January 16, 2001 9:31 AM
> > To: Multiple recipients of list ORACLE-L
> > Subject: RE: Auditing, how to capture sql statement issued
> >
> >
> >
> > Cale
> > I think you mean to reuse the sql statement sometime again.
> > if this is the case then u can save the query in the sql*plus
>editor
> > in
> > some file location
> > or u can just use SAVE <A> after your query in the sql*plus .
> > The next time u want to use the query u can just use ' @ A ' .
> >
> > e.g select * from tab;
> >
> >
> > TNAME TABTYPE CLUSTERID
> > ------------------------------ ------- ---------
> > AB TABLE
> > CD TABLE
> > DISTINCT_TEST TABLE
> > EMP TABLE
> > LXAPPLICATION TABLE
> > LXAUCTION TABLE
> > LXAUCTIONHISTORY TABLE
> > LXAUCTIONSTATUS TABLE
> > LXBID TABLE
> >
> >
> > SQL> save a replace
> > Wrote file a
> >
> > SQL> @ a
> >
> > TNAME TABTYPE CLUSTERID
> > ------------------------------ ------- ---------
> > AB TABLE
> > CD TABLE
> > DISTINCT_TEST TABLE
> > EMP TABLE
> > LXAPPLICATION TABLE
> > LXAUCTION TABLE
> > LXAUCTIONHISTORY TABLE
> > LXAUCTIONSTATUS TABLE
> > LXBID TABLE
> >
> >
> > you can also use the sql*plus editor by just typing 'ed' as it will
>load
> > the last executed sql query in
> > the editor where you save your query.
> >
> > Rgds,
> > ======
> > Sachin Puri
> > Oracle Development and Administration
> > Solutions NY
> > Tel : +91-11-6220102 x 22
> > Direct : +919810373243
> >
> >
> >
> > -----Original Message-----
> > Sent: Tuesday, January 16, 2001 6:31 PM
> > To: Multiple recipients of list ORACLE-L
> >
> >
> > Hi DBAs,
> >
> > Is there a way to capture the actual sql statement issued while in
> > sql*plus,worksheet,etc?
> >
> > Thanks,
> > Rick Cale, Science Applications International Corp.
> > Phone:865-481-2198, fax:865-481-8555
Received on Tue Jan 16 2001 - 15:59:43 CST