Re: Is it just me

  • From: Carel-Jan Engel <cjpengel.dbalert@xxxxxxxxx>
  • To: oracle-l@xxxxxxxxxxxxx
  • Date: Thu, 12 Aug 2004 16:52:47 +0200

The idea is not using fashback as the audit trail, but use it very
temporarily (seconds, or minutes at most) to provide the AQ-handler with
actual information. When the queue cannot be handled within a very
limited amount of time, I think flashback/AQ isn't the right solution
either. I like the logminer thing very much. Extending that idea, one
could also think of streams to put the logging in a separate database on
another server. 
I worked for a lottery, where everything needed to be logged as well.
The systems could only be reached through some management server,
through personal ID's, (user oracle couldn't login, one could only sudo
to it) and all keystrokes from the management server were logged on a
blackbox with write-only disks (I think it was freeBSD based). This box
wasn't approachable for internal sysadmins or DBA's or whatever. 

The logminer/streams thing can be used to achieve a similar separated
environment. Might even help with meeting SOX-related requirements.....

Best regards,

Carel-Jan Engel

If you think education is expensive, try ignorance. (Derek Bok)

On Thu, 2004-08-12 at 16:19, Tanel Põder wrote:

> The problem with flashback is of course that you can't nor shouldn't go back
> in time too much using it.
> Imagine that even if you had 6 months worth of undo space, then when you'd
> want to flash back a very frequently modified block, all the undo blocks in
> given data block undo chain from present to requested point of time would
> have to be applied.
> This means lots of CPU + possibly many physical IOs for reading each of the
> old undo blocks in, just to get the old value of single row.. Also there is
> no possibility whatsoever to index a rollback segment (which, again, you
> might not want to do either, in order to keep the auditing overhead low)
> Nuno: You're welcome, but be sure to check logminers restrictions first
> (which I'm sure you do anyway ;)
> Tanel.

Please see the official ORACLE-L FAQ:
To unsubscribe send email to:  oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
Archives are at
FAQ is at

Other related posts: