|
Actually, you can capture SQLs relatively
inexpensively by using FGA - simply add the "audit_condition => '1=1'" when
adding a policy to each table.
For OLTP, this wouldn't make much sense. For ad-hoc
(DSS), what you are going to do with all those captured SQLs is another
story.
----- Original Message -----
Sent: Wednesday, September 24, 2003 11:09
AM
Subject: Re: suggestion
For statistics, logon & logoff triggers
+ v$mystat + autonomous transactions.
If you want to capture all sql, it will be hard
& very resource hungry, you either enable trace for given session (which
slows stuff down enormously) or poll v$sql or v$open_cursor frequently. This
isn't a good idea either. You might want to look at fine grained auditing if
you want to track which data is viewed by anybody.
Tanel.
----- Original Message -----
Sent: Wednesday, September 24, 2003
1:39 AM
Subject: suggestion
hi
there is a requirement for capturing sqls and cpu consumed by any
session logging into the database . this info should be stored in the
database.
can you please give me suggestions as to how i do this?
thanks
sai
|
