Audit trail Tables should be in SAMS tablespaces in 9i / 10g?

Similar Questions

• Audit trail - on tables

  Hello, I got where I got to watch the scenario changes which makes the user.
  
  It was easy for me to monitor on a regular basis. But when it comes in the form that the form doesn't have any associated point page... I had to use the trigger on the table.
  
  But on the use of the trigger on table, I noticed that the relaxation begins when you delete records from all the tables changing. COS even the Audit trail data in table are deleted right here. So is there a way I can monitor the removal of records from APEX part INSTEAD OF trigger on table tabular presentation.
  
  Thank you.

  So is there a way I can monitor the removal of records from APEX part INSTEAD OF trigger on table tabular presentation.

  I recommend you implement the verification on the side of the database, rather than on the side 'client' (Apex), as this would work regardless of the client (sqlplus, ODP.NET program, etc.) is used to update the data.

  Depending on your version of the database and the license, you can use the "Total Recall" feature, which manages in fact for you:

  http://www.Oracle.com/technetwork/issue-archive/2008/08-Jul/o48totalrecall-092147.html

  + "Oracle Total Recall provides many advantages over traditional archival methods based on demand and trigger.» First of all, archiving data are inviolable. No database user, not even privileged users, cannot change the historical record. This level of security is increasingly required by government regulation. No programming effort is necessary. There is no table archive design, no code to write and no trigger to debug. The result has much less risk than any which can damage inadvertently archive. The performance impact is minimal. There is no direct impact on the flow of transactions, because the processes involved in archiving run asynchronously. Oracle Total Recall is implemented natively in the Oracle database and application-transparent. You can implement it under a running application without making changes to existing code. » +

  Or you can use the trigger approach as you tried.

  But on the use of the trigger on table, I noticed that the relaxation begins when you delete records from all the tables changing. COS even the Audit trail data in table are deleted right here.

  This should not happen if you use a separate table to save the audit trail information in.

  For example, if you have the EMP table, you create a table named (for example) $ AUD EMP, which is identical in structure, except that it has additional columns to track audit date, user name and operation (insert, update, delete).

  Then you put a trigger "for each line" on EMP to save the changes to the AUD$ EMP. You can delete all you want from EMP, it does not table mutation error.

  -Morten

  http://ORA-00001.blogspot.com

• Audit trail tablespace is incorrect according to DBA_AUDIT_MGMT_CONFIG_PARAMS

  Hi all
  
  I enabled the audit on my database and subsequently activated audit DML on a single table. Everything works as documented, except for this question: according to documents official sys.aud$ lies in the SYSTEM tablespace and I checked by running the following statement:
  SQL > select table_name, tablespace_name dba_tables where table_name = '$ ';
  table_name, nom_tablespace
  AUD$, SYSTEM
  
  But when I query the DBA_AUDIT_MGMT_CONFIG_PARAMS view it shows "SYSAUX" as the current tablespace:
  SQL > select * from DBA_AUDIT_MGMT_CONFIG_PARAMS;
  parameter_name, parameter_value, audit_trail
  DB_AUDIT_TABLESPACE, SYSAUX, STANDARD_AUDIT_TRAIL
  
  Even when I explicitly move sys.aud$ to the tablespace defined by the user as follows:
  SQL > create tablespace AUDIT_LOG datafile 'G:\ORADATA\audit_log.dbf' size 1024M autoextend on next 1024M;
  SQL > exec DBMS_AUDIT_MGMT.set_audit_trail_location (audit_trail_type = > DBMS_AUDIT_MGMT.) AUDIT_TRAIL_AUD_STD, audit_trail_location_value = > "AUDIT_LOG");
  
  .. .the DBA_AUDIT_MGMT_CONFIG_PARAMS view still shows as "SYSAUX. My system specs are: Windows 2008 Server, ORACLE, EE 11.1.0.7.0.
  
  
  (1) am I missing any step in-between here?
  (2) is it permissible to move audit trail to tablespace tablespace defined by the user in the version of database I'm using (ORACLE 11 g R1 on Windows)?

  Hello

  Usually it's not recommended to remove or truncate Tables belonging to SYS as all the user Tables.

  Instead, you can use the CREATE_PURGE_JOB procedure to purge the audit trail.

  Please find attached a link about this procedure and the use of the DBMS_AUDIT_MGMT package:

  http://download.Oracle.com/docs/CD/E11062_01/admin.1023/e11059/avadm_app_d_audit_mgmt.htm#BABFJHCB
  http://download.Oracle.com/docs/CD/E11062_01/admin.1023/e11059/avadm_app_d_audit_mgmt.htm#insertedID0

  If this procedure is not applicable to 11.1, you follow carefully the following way:

  http://download.Oracle.com/docs/CD/B28359_01/network.111/B28531/auditing.htm#BCGIHBAF

  You must connect SYS to get the necessary privileges.

  Hope this helps.
  Best regards
  Jean Valentine

  Published by: Lubiez John Valentine on March 7, 2010 10:49

• PURGE AUDIT TRAIL

  SELECT COUNT (*) FROM aud$;
  
  2063225
  
  BEGIN
  DBMS_AUDIT_MGMT. () INIT_CLEANUP
  AUDIT_TRAIL_TYPE = > DBMS_AUDIT_MGMT. AUDIT_TRAIL_ALL,
  DEFAULT_CLEANUP_INTERVAL = > 12);
  END;
  /
  
  anonymous block filled
  
  SELECT * FROM dba_audit_mgmt_config_params;
  
  STANDARD DB TABLESPACE SYSAUX AUDIT AUDIT TRAIL
  DB AUDIT TABLESPACE SYSAUX FGA AUDIT TRAIL
  AUDIT OF AUDIT FILE MAX TRAIL SIZE 10000 OS
  CHECKING FILE MAX SIZE 10000 XML AUDIT TRAIL
  AUDIT FILE MAX 5 YEARS AUDIT TRAIL OS
  AUDIT FILE MAX 5 YEARS AUDIT TRAIL XML
  DB AUDIT OWN LOT SIZE 10000 AUDIT STANDARD
  DB AUDIT OWN LOT SIZE 10000 FGA AUDIT TRAIL
  1000 OS OS OWN BATCH FILE AUDIT TRAIL SIZE
  OS OWN BATCH FILE AUDIT TRAIL SIZE 1000 XML
  DEFAULT CLEANUP INTERVAL 12 STANDARD AUDIT TRAIL
  DEFAULT CLEANUP INTERVAL 12 FGA AUDIT TRAIL
  DEFAULT CLEANUP INTERVAL 12 OS AUDIT TRAIL
  DEFAULT CLEANUP INTERVAL 12 XML AUDIT TRAIL
  
  BEGIN
  () DBMS_AUDIT_MGMT.clean_audit_trail
  audit_trail_type = > DBMS_AUDIT_MGMT. AUDIT_TRAIL_ALL,
  use_last_arch_timestamp = > false);
  END;
  /
  
  anonymous block filled
  
  
  SELECT COUNT (*) FROM aud$;
  
  2063225
  
  I do not use Archive Timestamp to Audit records
  I think that all runners should be bleeding?

  Depending on your exact version, you may have a bug experienced with AUDIT_TRAIL_ALL (11.2.0.2 resolved):
  Bug 9164488 - DBMS_AUDIT_MGMT . CLEAN_AUDIT_TRAIL does not delete the sys.aud$ and the sys.fga_log$ tables 9164488.8 ID+.

  Nicolas.

• Another audit trail is not purged.

  Oracle 11.2.0.3 SE - One

  Oracle Linux 5.6 x 86-64

  I seem to have a problem very similar to that described in thread https://community.Oracle.com/thread/3574919

  Went through the usual steps of moving tables to audit a dedicated TS and the initialization of audit management infrastructure.  Working on 3 different databases on a test server, two work exactly as planned but the third (rman duplicate every weekend production) is not purge.

  Here is the testimony of the installation.  For display, I changed the names of database a simply DB1, DB2, DB3.  Those designated as DB3 is the "enfant terrible".

  SQL > select name from v$ database;

  NAME

  ---------

  DB1

  1 selected line.

  SQL > SET SERVEROUTPUT ON

  SQL > START

  2. IF DBMS_AUDIT_MGMT.is_cleanup_initialized (DBMS_AUDIT_MGMT. AUDIT_TRAIL_DB_STD) THEN

  3 DBMS_OUTPUT.put_line ('YES');

  4 SOMETHING ELSE

  5 DBMS_OUTPUT.put_line ('NO');

  6 END IF;

  7 END;

  8.

  YES

  PL/SQL procedure successfully completed.

  SQL > SELECT * FROM dba_audit_mgmt_config_params;

  PARAMETER_NAME, PARAMETER_VALUE AUDIT_TRAIL

  ------------------------------ -------------------- --------------------

  STANDARD DB TABLESPACE AUDIT_TRAIL AUDIT AUDIT TRAIL

  FGA DB TABLESPACE AUDIT_TRAIL AUDIT AUDIT TRAIL

  AUDIT OF AUDIT FILE MAX TRAIL SIZE 10000 OS

  CHECKING FILE MAX SIZE 10000 XML AUDIT TRAIL

  AUDIT FILE MAX 5 YEARS AUDIT TRAIL OS

  AUDIT FILE MAX 5 YEARS AUDIT TRAIL XML

  DB AUDIT OWN LOT SIZE 10000 AUDIT STANDARD

  DB AUDIT OWN LOT SIZE 10000 FGA AUDIT TRAIL

  1000 OS OS OWN BATCH FILE AUDIT TRAIL SIZE

  OS OWN BATCH FILE AUDIT TRAIL SIZE 1000 XML

  DEFAULT CLEANUP INTERVAL 24 STANDARD AUDIT TRAIL

  PARAMETER_NAME, PARAMETER_VALUE AUDIT_TRAIL

  ------------------------------ -------------------- --------------------

  DEFAULT CLEANUP INTERVAL 24 FGA AUDIT TRAIL

  DEFAULT CLEANUP INTERVAL 24 OS AUDIT TRAIL

  DEFAULT CLEANUP INTERVAL 24 XML AUDIT TRAIL

  14 selected lines.

  SQL >

  SQL > exit

  < snip >

  SQL > select name from v$ database;

  NAME

  ---------

  DB2

  1 selected line.

  SQL > SET SERVEROUTPUT ON

  SQL > START

  2. IF DBMS_AUDIT_MGMT.is_cleanup_initialized (DBMS_AUDIT_MGMT. AUDIT_TRAIL_DB_STD) THEN

  3 DBMS_OUTPUT.put_line ('YES');

  4 SOMETHING ELSE

  5 DBMS_OUTPUT.put_line ('NO');

  6 END IF;

  7 END;

  8.

  YES

  PL/SQL procedure successfully completed.

  SQL > SELECT * FROM dba_audit_mgmt_config_params;

  PARAMETER_NAME, PARAMETER_VALUE AUDIT_TRAIL

  ------------------------------ -------------------- --------------------

  STANDARD DB TABLESPACE AUDIT AUDIT TRAIL

  FGA DB TABLESPACE AUDIT AUDIT TRAIL

  AUDIT OF AUDIT FILE MAX TRAIL SIZE 10000 OS

  CHECKING FILE MAX SIZE 10000 XML AUDIT TRAIL

  AUDIT FILE MAX 5 YEARS AUDIT TRAIL OS

  AUDIT FILE MAX 5 YEARS AUDIT TRAIL XML

  DB AUDIT OWN LOT SIZE 10000 AUDIT STANDARD

  DB AUDIT OWN LOT SIZE 10000 FGA AUDIT TRAIL

  1000 OS OS OWN BATCH FILE AUDIT TRAIL SIZE

  OS OWN BATCH FILE AUDIT TRAIL SIZE 1000 XML

  DEFAULT CLEANUP INTERVAL 24 STANDARD AUDIT TRAIL

  PARAMETER_NAME, PARAMETER_VALUE AUDIT_TRAIL

  ------------------------------ -------------------- --------------------

  DEFAULT CLEANUP INTERVAL 24 FGA AUDIT TRAIL

  DEFAULT CLEANUP INTERVAL 24 OS AUDIT TRAIL

  DEFAULT CLEANUP INTERVAL 24 XML AUDIT TRAIL

  14 selected lines.

  SQL >

  SQL > exit

  < snip >

  SQL > select name from v$ database;

  NAME

  ---------

  GBP

  1 selected line.

  SQL > SET SERVEROUTPUT ON

  SQL > START

  2. IF DBMS_AUDIT_MGMT.is_cleanup_initialized (DBMS_AUDIT_MGMT. AUDIT_TRAIL_DB_STD) THEN

  3 DBMS_OUTPUT.put_line ('YES');

  4 SOMETHING ELSE

  5 DBMS_OUTPUT.put_line ('NO');

  6 END IF;

  7 END;

  8.

  YES

  PL/SQL procedure successfully completed.

  SQL > SELECT * FROM dba_audit_mgmt_config_params;

  PARAMETER_NAME, PARAMETER_VALUE AUDIT_TRAIL

  ------------------------------ -------------------- --------------------

  STANDARD DB TABLESPACE AUDIT AUDIT TRAIL

  FGA DB TABLESPACE AUDIT AUDIT TRAIL

  AUDIT OF AUDIT FILE MAX TRAIL SIZE 10000 OS

  CHECKING FILE MAX SIZE 10000 XML AUDIT TRAIL

  AUDIT FILE MAX 5 YEARS AUDIT TRAIL OS

  AUDIT FILE MAX 5 YEARS AUDIT TRAIL XML

  DB AUDIT OWN LOT SIZE 10000 AUDIT STANDARD

  DB AUDIT OWN LOT SIZE 10000 FGA AUDIT TRAIL

  1000 OS OS OWN BATCH FILE AUDIT TRAIL SIZE

  OS OWN BATCH FILE AUDIT TRAIL SIZE 1000 XML

  DEFAULT CLEANUP INTERVAL 24 STANDARD AUDIT TRAIL

  PARAMETER_NAME, PARAMETER_VALUE AUDIT_TRAIL

  ------------------------------ -------------------- --------------------

  DEFAULT CLEANUP INTERVAL 24 FGA AUDIT TRAIL

  DEFAULT CLEANUP INTERVAL 24 OS AUDIT TRAIL

  DEFAULT CLEANUP INTERVAL 24 XML AUDIT TRAIL

  14 selected lines.

  SQL >

  SQL > exit

  Here are the guts of the purge script

  Conn / as sysdba

  ALTER session set nls_date_format = 'DD-MON-YYYY HH24:MI:SS ";

  Select the name,

  SYSDATE RUN_TIME

  from v$ database;

  --

  Select count (*) audit_recs,

  min (timestamp) oldest.

  Max (timestamp) new

  of dba_audit_trail;

  --

  BEGIN

  DBMS_AUDIT_MGMT. SET_LAST_ARCHIVE_TIMESTAMP (DBMS_AUDIT_MGMT. AUDIT_TRAIL_AUD_STD, TRUNC (SYSTIMESTAMP)-90);

  DBMS_AUDIT_MGMT. SET_LAST_ARCHIVE_TIMESTAMP (DBMS_AUDIT_MGMT. AUDIT_TRAIL_FGA_STD, TRUNC (SYSTIMESTAMP)-90);

  DBMS_AUDIT_MGMT. SET_LAST_ARCHIVE_TIMESTAMP (DBMS_AUDIT_MGMT. AUDIT_TRAIL_OS, TRUNC (SYSTIMESTAMP)-90);

  DBMS_AUDIT_MGMT. SET_LAST_ARCHIVE_TIMESTAMP (DBMS_AUDIT_MGMT. AUDIT_TRAIL_XML, TRUNC (SYSTIMESTAMP)-90);

  END;

  /

  --

  BEGIN

  DBMS_AUDIT_MGMT. CLEAN_AUDIT_TRAIL (DBMS_AUDIT_MGMT. AUDIT_TRAIL_ALL, TRUE);

  END;

  /

  --

  Select count (*) audit_recs,

  min (timestamp) oldest.

  Max (timestamp) new

  of dba_audit_trail;

  --

  and here are the results of the problem child

  Modified session.

  NAME RUN_TIME

  --------- --------------------

  DB3 24 JUNE 2014 08:05:01

  AUDIT_RECS MOST RECENT FORMER

  ---------- -------------------- --------------------

  3535812 17 JUNE 2013 02:45:49 JUNE 24, 2014 08:01:33

  PL/SQL procedure successfully completed.

  PL/SQL procedure successfully completed.

  AUDIT_RECS MOST RECENT FORMER

  ---------- -------------------- --------------------

  3535812 17 JUNE 2013 02:45:49 JUNE 24, 2014 08:01:33

  As usual, I'm sure I have forgotten any essential difference between the 'good' and 'bad', but it eludes me.

  > but the third (rman duplicate every weekend production) is not purge.

  If the DBID changed?

  See footnote support Oracle #1431343.1

  Hemant K Collette

• Audit trail is not purged.

  Hello

  my current database version is 11.2.0.3.0. I am currently serving my with a procedure audit trail. In my home, I had this part of the code:

  SYS.dbms_audit_mgmt.clean_audit_trail( audit_trail_type  =>  SYS.dbms_audit_mgmt.audit_trail_aud_std, use_last_arch_timestamp => TRUE );

  I'm not under the procedure under SYS so there... in SYS.dbms code. Everything works without errors. But the table of sys.aud audit trail $ is not purged!

  Any ideas why it doesn't work?

  I read that: Bug 9164488 - DBMS_AUDIT_MGMT. CLEAN_AUDIT_TRAIL does not delete the tables sys.aud$ and sys.fga_log$ ID 9164488.8 + has been fixed in 11.2.0.2 version, so this should not be the case.

  Also last setting archive timestamp works very well!

  SYS.dbms_audit_mgmt.set_last_archive_timestamp( audit_trail_type  => SYS.dbms_audit_mgmt.audit_trail_aud_std, last_archive_time => to_timestamp(SYSDATE - pocet_dnu), rac_instance_number  => null ); 

  Thank you

  Honza

  See Support of Oracle 1431343.1 Note for a possible cause.

  Hemant K Collette

• Configuration of the audit trail of data

  Hello
  
  I am brand new with Hyperion Planning/Essbase and I'm trying to implement an audit trail of data. I already turned on the audit data in the workspace-> Navigate-> Applications-> planning-> DBName-> Administration-> Application reports. I also downloaded SQLDeveloper in my laptop and have it operational. However, I can not understand how to connect with Hyperion Planning/Essbase. Is there documentation on how to setup the connection? Any help will be greatly appreciated.
  
  Thank you

  If you go into the administration of planning and change the data source for your application, then it should provide all the connection information.
  In SQLdeveloper add a new connection and enter the details of the data source to connect to the schema and expand tables and view or query the data in HSP_AUDIT_RECORDS

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• He had to capture the old value and new values using the oracle audit trail

  Hello
  
  I put the parameter audit_trail for db, extended. I am in treatment of the LMD. I need to display the values changed by these instructions DML audit trail stored in dba_audit_trail. How can I achieve the same?
  
  Kindly guide me.

  If you want images of column of the table target before and after then the native audit function is probably not your best option. I think that you want to set triggers to audit for the insert tables and write either the CDC or duplicate lines in a historical table of change.

  HTH - Mark D Powell.

• DB Audit trail

  Hi all
  
  I just wanted to check my understanding of something. Am I right in thinking that the audit trail can only be written to SYS. AUD$ (or SYS. FGA_LOG$) OR a file in an operating system? (That is, it is not possible to save the logs to audit on location table/tablespace).
  
  Oracle 11.1.0.7, AIX
  
  Kind regards
  
  Graham

  >
  I just wanted to check my understanding of something. Am I right in thinking that the audit trail can only be written to SYS. AUD$ (or SYS. FGA_LOG$) OR a file in an operating system? (That is, it is not possible to save the logs to audit on location table/tablespace).
  >

  You can move tables check the space of system tables in a different tablespace. Check
  http://dbatrain.WordPress.com/2009/05/14/is-your-audit-trailing-behind/

  Kind regards
  Uwe

  http://uhesse.WordPress.com

• Options of alias for POV while implementing the data audit trails

  Hi all

  I have a request to implement the option Alias for the account dimension, which gets exported to the HSP_AUDIT_RECORDS table when the Audit trail for data is enabled.

  In the column of ID2, user want to see Alias name of the Member account.

  Do we not have this feature?

  Kind regards

  NGO

  Audit records will still be stored with the name of the Member, not alias, to do this, you will need to do a post on the table processing and replace the names of the members with the alias, I don't know any other way to get.

• 11 GR 2: periodically purge the question of audit trail

  Hello
  
  I have a question about automatic and periodically audit trail is serving to 11g.
  
  I went through the docs and went ahead scheduling periodic purge of my audit trail based on archive timestamp.
  
  Here are the steps I did:
  
  (1) run dbms_audit_mgmt.init_cleanup
  (2) run dbms_audit_mgmt.set_last_archive_timestamp as follows:
  

  SQL>begin
   2  dbms_audit_mgmt.set_last_archive_timestamp(
   3  audit_trail_type => DBMS_AUDIT_MGMT.AUDIT_TRAIL_AUD_STD,
   4  last_archive_time => SYSTIMESTAMP-365);
   5  end;
   6  /

  (3) created a purge with dbms_audit_mgmt.create_purge_job job that uses the timestamp of set_last_archive_timestamp
  
  
  That went well, and the first work of purge delete all records of 365 days. But I expect I would be the timestamp increment any, so that the recurring task always deletes records older than systimestamp-365.
  But this does not happen and the initial date of SYSTIMESTAMP-365 remains on the original date.
  Am I supposed to run dbms_audit_mgmt.set_last_archive_timestamp every time before work to purge itself?
  
  Thanks a lot for any advice / experience on this. :)

  Hi AJ,.
  set_last_archive_timestamp is considered to be the last stage of the audit manual archiving data. Doc States:

  This procedure sets a timestamp that indicates when the audit records were finally archived. The Director of audit provides the time stamp to affix the audit records. The CLEAN_AUDIT_TRAIL procedure uses this timestamp to decide on audit records should be deleted.

  So you have to run set_last_archive_timestamp on a regular basis and thus confirm the audit data archiving.

  CREATE_PURGE_JOB calls CLEAN_AUDIT_TRAIL which checks archive timestamp of last call of set_last_archive_timestamp.

  In short, yes call set_last_archive_timestamp each time before purge jobs runs or working purge purge more recent verification of data.

  Concerning
  Martin

• After spending tables and index a different tablespace, index got unusable?

  Hello
  
  I moved to table and index a different tablespace. After the many indices obtained unusable. I did not understand thiis?
  
  How can I do still usable?
  
  best regards and thank you?

  If you bâtait the index (after moving the table, by the way), then they should be usable without something extra to see.
  Check this procedure only one (small) table and index if this index can be used later. If not, then you have a mystery :-)

  Kind regards
  Uwe Hesse

  http://uhesse.WordPress.com

• ORA-09925: cannot create the audit trail file / RCONFIG

  Hello
  
  I tried to convert a single DB instance named TESTDB in a RAC - DB named CARS on two nodes stb & dwh with rconfig!
  
  After running I got following error messages on one of the two nodes:

  /u01/app/oracle/product/11.2.0.2/db_1/dbs>sqlplus / as sysdba
  
  SQL*Plus: Release 11.2.0.2.0 Production on Tue Mar 8 15:17:09 2011
  
  Copyright (c) 1982, 2010, Oracle.  All rights reserved.
  
  ERROR:
  ORA-09925: Unable to create audit trail file
  Linux-x86_64 Error: 2: No such file or directory
  Additional information: 9925
  ORA-01075: you are currently logged on
  
  
  Enter user-name:
  ERROR:
  ORA-01017: invalid username/password; logon denied

  I tried to change the setting audit_file_dest on the instance of execution yet.
  
  And now I get the same errors on both instances.
  
  Help, please.
  
  hqt200475

  you do not need to change your spfile, create a valid directory for AUDIT_FILE_DEST

  If you do not know the value necessary relating to alert.log
  or take a look at your spfile
  or connect as a system with the parameter checking
  or find your spfile by see the spfile parameter
  or find your spfile in your alert.log
  or find with the trial obviously ist started and open.

  RN

• Views audit trails

  What is the typical RDBMS of reporting tools used to report audit trail data?
  
  As a good practice in General, although this can vary from client to client, what are the objects, you must generally audit?
  
  What is the mechanism to keep the table of audit such as the removal of the old records etc.?
  
  Thank you.

  Is this something that you want to use and write sql to retrieve information? If yes then you just need a tool such as sql developer sql.

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• 9.3.1 audit trail

  Hello all-
  
  I lived this doecument http://www.oracle.com/technology/obe/hyp_fp/PLN11.1.1_Audit_Trail/pln_audit_trail.htm. This audit trail feature works the same way in the 9.3.1? Has anyone used this for version 9.3.1?
  
  Thank you!

  Hello

  Yes, audit functionality is very similar in the 9.3.1 here is the documentation for 9.3.1 establishing an audit trail:-http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/html_hp_admin/rep_aud.html

  See you soon

  John
  http://John-Goodwin.blogspot.com/