Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Transaction_audit FALSE
Duly noted.
I've saved your instruction in my "Try This At Home" file,
for execution when my current job description is no longer
"It's the Urgent Crap, Stupid"
My anecdotal observation was based only on this -- we spit out about 750MB of redo every 3 minutes and I thought even 10% reduction over a day (we do two cleanouts of our log/arch/dest daily, and it's sized at just shy of half a terabyte ) would make the arch log sweep and volume run better.
But since my SAs did not march into my office with a shiny new revolver for this silver bullet I thought I found, I guess it didn't make much noticeable difference.
Thanks for the helpful paragraphs, and I'll update the list if anything joyous occurs.
-----Original Message-----
From: Jonathan Lewis [mailto:jonathan_at_jlcomp.demon.co.uk]
Sent: Thursday, May 06, 2004 8:59 AM
To: oracle-l_at_freelists.org
Subject: Re: Transaction_audit FALSE
If you dump a small redo log, you should find that the 4th redo vector of the first redo record of every transaction is a transaction audit record. In 8.1.7.3, I think this is still going to include data in all the fields marked, and can easily be a couple of hundred bytes long.
In 9i, it's only the first record of the session that has all the data, then every other record has only the session number and serial number, so the overhead is much smaller.
If you do a very large number of very small transactions (e.g. batch load via single row commits) the impact on the redo log can be significant. In more normal processing the overhead tends to have low visibility.
session number = 9 serial number = 14 current username = {...} login username = {...} client info = OS username = {...} Machine name = {...} OS terminal = {...} OS process id = {...} OS program name = {...} transaction name =
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk/faq/ind_faq.html The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/seminar.html Optimising Oracle Seminar - schedule updated May 1st
Piggybacking off DDL Audit thread....
I unset the transaction_auditing parameter to reduce redo logs and saw essentially no change in redo size generated.
81730/Solaris 8
![]() |
![]() |