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 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 ----- Original Message ----- From: "Mohan, Ross" <RMohan@xxxxxxxxxxxxxx> To: <oracle-l@xxxxxxxxxxxxx> Sent: Tuesday, May 04, 2004 10:30 PM Subject: Transaction_audit FALSE 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 ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------