Need Help !! Oracle Auditing

Question

Hi All,
We are trying to turn On auditing for our Oracle Database(9i/10g).
Requirement is to audit the insert/delete/update statements of the team members. So for every delete/update statement we would like to have the before image and after image of the database. What the row data was before updating the database.
We have 100 tables and 12 schemas. I do not want to write triggers. I am looking for any functionality in Oracle itself which will help me achieve this. I am aware of the Fine Grain Auditing but it does not meet my requirement of actually getting the rows before update. I do not intend to store the actual sql text.
Please reply if you have already done something similar.
Thanks in advance.
Regards,
Rahul

Answer 1

Why do you believe that Workspace Manager would not be transparent? And why do you believe that you would not be able to determine who made a change?
SQL> create table my_new_table (
  2    col1 number,
  3    col2 number,
  4    constraint pk_new_tbl primary key( col1 )
  5  );
Table created.
SQL> exec dbms_wm.enableVersioning( 'MY_NEW_TABLE', 'VIEW_WO_OVERWRITE' );
PL/SQL procedure successfully completed.
SQL> insert into my_new_table values( 1, 10 );
1 row created.
SQL> insert into my_new_table values( 2, 20 );
1 row created.
SQL> commit;
Commit complete.
SQL> update my_new_table
  2     set col2 = col2 + 1;
2 rows updated.
SQL> commit;
Commit complete.
SQL> select * from my_new_table;
      COL1       COL2
         1         11
         2         21
SQL> column col1 format 9999
SQL> column col2 format 9999
SQL> column wm_username format a10;
SQL> column wm_username format a15;
SQL> column wm_createtime format a25;
SQL> column wm_retiretime format a25;
SQL> select col1, col2, wm_optype, wm_username, wm_createtime, wm_retiretime
  2    from my_new_table_hist;
COL1  COL2 W WM_USERNAM WM_CREATETIME             WM_RETIRETIME
    1    10 I SCOTT      11-JUL-09 10.50.13.859000 11-JUL-09 10.50.37.062000
                          AM -04:00                 AM -04:00
    2    20 I SCOTT      11-JUL-09 10.50.24.171000 11-JUL-09 10.50.37.109000
                          AM -04:00                 AM -04:00
    1    11 U SCOTT      11-JUL-09 10.50.37.062000
                          AM -04:00
    2    21 U SCOTT      11-JUL-09 10.50.37.109000
                          AM -04:00I assume that you don't literally want a single ROW_DATA column that has some amalgamation of all the other columns in the table-- that would seem to be a rather poor way to store historical data. Workspace Manager will have a column in the _HIST view for each column in the regular view. 
Justin