Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!news-FFM2.ecrc.net!newsfeed.vmunix.org!kibo.news.demon.net!news.demon.co.uk!demon!peterfinnigan.demon.co.uk!pete From: Pete Finnigan Newsgroups: comp.databases.oracle.server Subject: Re: Recording Logon and SQL Date: Mon, 7 Jul 2003 13:27:26 +0100 Organization: www.petefinnigan.com Lines: 31 Message-ID: References: NNTP-Posting-Host: peterfinnigan.demon.co.uk Mime-Version: 1.0 X-Trace: news.demon.co.uk 1057582496 20316 212.228.17.70 (7 Jul 2003 12:54:56 GMT) X-Complaints-To: abuse@demon.net NNTP-Posting-Date: Mon, 7 Jul 2003 12:54:56 +0000 (UTC) X-Newsreader: Turnpike Integrated Version 5.01 S Xref: newssvr20.news.prodigy.com comp.databases.oracle.server:237051 Hi Why not just use audit session to capture the logon/logoff. To capture all SQL you can use fine grained audit and use a predicate that will be true for every access to each table and record the SQL from the trigger. If you do not have the correct version to support FGA then use normal audit to track access but you will not get the SQL that way and will also not get selects. I think Fine grained audit is the way to go for you. hth kind regards Pete In article , netnews.comcast.net writes >Does anybody know of a way to track every user >and SQL statement from the v$session and >v$sqlarea without using auditing. Currently we are using >a stored procedure that polls these tables but sometimes >the pool is flushed allowing statements to slip in between the cracks. >Looking for a better way of doing this. -- Pete Finnigan email:pete@petefinnigan.com Web site: http://www.petefinnigan.com - Oracle security audit specialists Book:Oracle security step-by-step Guide - see http://store.sans.org for details.