Idea for testing: looking for redo associated with select
statement(s) that are cleaning out row level locks in
block(s) from previously committed DML transaction(s).
Have Fun :)
Tanel Poder wrote:
Hi!
Maybe they were thinking that if you audit select statements, you can
analyze inserts on AUD$
Hi!
Maybe they were thinking that if you audit select statements, you can
analyze inserts on AUD$ using logminer later on
Anyway, if there's any future release where selects can be in redo, I hope
they aren't there by default..
Tanel.
- Original Message -
To: "Multiple recipients of
Hi Arup and Joe
When I wrote the SANS Oracle security step-by-step book I wrote in there
the list of restrictions for log miner including that is didn't support
selects and during the review process of my book someone in Oracle who
was reviewing it informed me that selects would be in the redo in
Arup, I kinda shook my head on that one also. So Pete, you got some
inside-scoop that i've missed, i admit i've not much touched logminer in
9ir2(did alot of it and presentations back in 8i days), but have been
spending my days now doing DR/RMAN implementations.
joe
Arup Nanda wrote:
Hi Pet
Hi Pete,
I am a little prerplexed by "selects are not recorded in redo prior to 9i ".
AFAIK selects are nevere recorded in the redo, and therefore archived logs -
so they are never unearthed by LogMiner, even in 9i Release2. Isn't that
true?
Thanks.
Arup
- Original Message -
To: "Multip
Joe and Pete,
Thanks for the response, that confirms my thoughts.
Robin
Pete Finnigan wrote:
>
> Hi Robin,
>
> LogMiner is a good tool for forensics, after the fact type work i.e to
> find out when your junior dba dropped that table. It shouldn't be used
> to do run of the mill daily work. It
Hi Robin,
LogMiner is a good tool for forensics, after the fact type work i.e to
find out when your junior dba dropped that table. It shouldn't be used
to do run of the mill daily work. It has a few deficiencies that are
hard to work around:
o - log miner user PGA memory so cannot be used in MTS
Robin, only in a recovery situation, but not to track changes
consistently, what version of oracle, since in 8i days, logminer didn't
support certain datatypes, etc and forget about chained, migrated rows. :)
joe
Robin Li wrote:
Hi all,
The users want to keep the old information on certain f
Hi all,
The users want to keep the old information on certain fields once an
update occurs for one (maybe two) table. I recommend to create a history
table and use trigger. And the developer says LogMiner is the idea.
I played with LogMiner once a year ago. I remember I had to specified a
start/
