instead of being confused by the options -- why not list your specific requirments?
If you have the requirement to know "user X updated the EMP table" the right answer is "audit command"
If you have a requirment to know the "sql that user X used to update the EMP table", a trigger is correct (using ora_sql_txt to capture it) or in 10g, dbms_fga can capture modifications as well as select queries.
If you have a reqirement to row by row capture the before/after values to know that user X changed the row from "this to that", perhaps workspace management is right for you:
</code>
http://asktom.oracle.com/pls/asktom/f?p=100:11:::::P11_QUESTION_ID:4529781014729 http://docs.oracle.com/cd/B10501_01/appdev.920/a96628/toc.htm <code>
or you do it yourself via triggers and "a shadow table that looks like the original table but you save the :old values" into it.
You cannot use "audit" (event auditing) to do what "dbms_fga" (statement auditing) does and you cannot use "dbms_fga" to do what "dbms_wm" (versioning of data including date/time/who did the operation) does...
Not sure if the install will fly or not, I have never attempted it without a machine "at spec"