Audit trail for task - what is logical graph?

Similar Questions

• Do not get the audit trail for oracle solaris running. It starts and then stops after a few seconds. How can I set up a secure target Oracle Solaris? cure

  I have installation BSM on my solaris 10 Server. I configured BSM to be sent to syslog. I registered my target secure on the server of the AV type Oracle Solaris. Add an audit trail of pointing to the syslog file. The Audit Trail starts and stops after a few seconds. the error I get from the agent log is

  [2014 11-25 T 11: 36:38.647 + 02:00] [collfwk] [ERROR] [] [] [tid: 10] [ecid: 192.169.1.50:11353:1416908198895:0, 0] FVO-8015: initialization of the instanceCollectionController AuditEventCollector error: run: process() Exception. [[

  Instance of Error initializing AuditEventCollector

  at oracle.av.platform.agent.collfwk.impl.controller.CollectionController.initialize(CollectionController.java:322)

  at oracle.av.platform.agent.collfwk.impl.controller.CollectionController.process(CollectionController.java:402)

  at oracle.av.platform.agent.collfwk.impl.controller.CollectionController.run(CollectionController.java:350)

  at java.lang.Thread.run(Thread.java:662)

  Nested exception:

  java.lang.NumberFormatException: for input string: "invalid audit trail: / var/adm."

  at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)

  at java.lang.Integer.parseInt(Integer.java:449)

  in java.lang.Integer. < init > (Integer.java:660)

  to oracle.av.platform.common.exception.AuditException. < init > (AuditException.java:118)

  to oracle.av.platform.agent.collfwk.AuditEventCollectorException. < init > (AuditEventCollectorException.java:59)

  at com.oracle.solaris.SolarisCollector.initializeCollector(SolarisCollector.java:86)

  at oracle.av.platform.agent.collfwk.impl.controller.CollectionController.initialize(CollectionController.java:316)

  at oracle.av.platform.agent.collfwk.impl.controller.CollectionController.process(CollectionController.java:402)

  at oracle.av.platform.agent.collfwk.impl.controller.CollectionController.run(CollectionController.java:350)

  at java.lang.Thread.run(Thread.java:662)

  ]]

  [2014 11-25 T 11: 47:49.248 + 02:00] [collfwk] [ERROR] [] [] [tid: 11] [ecid: 192.169.1.50:11353:1416908869249:1, 0] FVO-8015: initialization of the instanceCollectionController AuditEventCollector error: run: process() Exception. [[

  Instance of Error initializing AuditEventCollector

  at oracle.av.platform.agent.collfwk.impl.controller.CollectionController.initialize(CollectionController.java:322)

  at oracle.av.platform.agent.collfwk.impl.controller.CollectionController.process(CollectionController.java:402)

  at oracle.av.platform.agent.collfwk.impl.controller.CollectionController.run(CollectionController.java:350)

  at java.lang.Thread.run(Thread.java:662)

  Nested exception:

  java.lang.NumberFormatException: for input string: "invalid audit trail: / var/audit.

  at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)

  at java.lang.Integer.parseInt(Integer.java:449)

  in java.lang.Integer. < init > (Integer.java:660)

  to oracle.av.platform.common.exception.AuditException. < init > (AuditException.java:118)

  to oracle.av.platform.agent.collfwk.AuditEventCollectorException. < init > (AuditEventCollectorException.java:59)

  at com.oracle.solaris.SolarisCollector.initializeCollector(SolarisCollector.java:86)

  at oracle.av.platform.agent.collfwk.impl.controller.CollectionController.initialize(CollectionController.java:316)

  at oracle.av.platform.agent.collfwk.impl.controller.CollectionController.process(CollectionController.java:402)

  at oracle.av.platform.agent.collfwk.impl.controller.CollectionController.run(CollectionController.java:350)

  at java.lang.Thread.run(Thread.java:662)

  ]]

  Can you please help with instructions/solution implementation of Oracle Solaris secure target? A beginner in Audit Vault.

  I have the installation path for the database and which works very well

  concerning

  Thanks for the pointers. After you add hostname to the location of the trail, the audit trail is running

• How can I send a company of "the password audit trail" for a doc to e-sign?  They want to check it for their records. Thank you!

  
  I have need help send the 'audit trail of password for a document. A company, we work with will not accept the pdf of the signed document copy.

  Thank you.

  Hello

  You can find your report via the tab manage point culminating the document in question and select the history tab (on the right side). You will then see the option of audit report.

  Thank you

• Using the Audit trail for audit rollback and commit?

  Hello

  Although not always relevant because a "failure" session/program can issue a commit or a rollback, is possible to audit the validations and cancellations using the Audit trail?

  Thank you and best regards.

  
  

  Yes, 12 c.

• Audit trail for the ATG scenario

  Scenario records the audit trail in the audittrail.xml file. Can someone anyone tell me how/where to access this file?

  Well well its interior.

  C:\ATG\ATG10.0.2\DSS\config\config.jar in the \atg\registry\data\datasets folder

• 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.

• Unable to show the Audit trail

  Hey all,.
  
  I try to turn on the display of the Audit trail for a user. But here's what I've done so far:
  
  1. remove the check mark from the Web Client and dedicated customer
  
  2. After you make these changes I have restarted the services
  
  3 - I took the name of view and added to the responsibility of the user
  
  When you perform these steps the screen of the Audit trail is not always visible to the user. Can someone help me please?
  
  
  Kind regards

  Harnois,

  If it is specific to the Service request screen. Then you can try the following:

  Go to the Admin - responsibilities: choose the primary responsibility of the user. Then select the page "Tab Layout" below.

  Then look for the name of the Application you are using (for example. Services financiers Siebel)

  The tab of the screen layout, select the Service, and the query for the "Audit trail" in the below «See tab Layout»

  Check if the "Hide" option is selected or not.

  Kind regards
  Joseph

• Limit regarding the Audit trail cleaning

  Hello

  I have a RDBMS Oracle 11g, which makes use of the Standard Audit trail.

  I like to keep the audit for 3 months from the date, cleanup runs, which means that have the Audit trail for 3 months, back from the date I'm looking at.

  But I read that there is a limit of 999 hours to set "cleaning interval."

  For copyrighted I ise a regular as program:

  BEGIN

  DBMS_AUDIT_MGMT. () SET_AUDIT_TRAIL_PROPERTY

  AUDIT_TRAIL_TYPE = > DBMS_AUDIT_MGMT. AUDIT_TRAIL_AUD_STD,

  AUDIT_TRAIL_PROPERTY = > DBMS_AUDIT_MGMT. CLEAN_UP_INTERVAL,

  AUDIT_TRAIL_PROPERTY_VALUE = > 999);

  END;

  /

  
  Can anyone confirm if this is correct or not?

  If so, this also applies to Oracle RDBMS 12 c.

  Thank you in advance.

  Kind regards

  Laury, the cleanup interval is how much work to purge works, not how long the data are kept.  So the limit of 999 hours isn't a consideration for your target.  I suggest that you run the purge not less than every day.

  - -

  --

  -Implementation of audit purge

  --

  BEGIN

  DBMS_AUDIT_MGMT. () INIT_CLEANUP

  audit_trail_type-online DBMS_AUDIT_MGMT. AUDIT_TRAIL_DB_STD,

  default_cleanup_interval-online 30);

  DBMS_AUDIT_MGMT. () SET_LAST_ARCHIVE_TIMESTAMP

  audit_trail_type-online DBMS_AUDIT_MGMT. AUDIT_TRAIL_AUD_STD,

  last_archive_time-online to_timestamp (sysdate-(92)));

  DBMS_AUDIT_MGMT. () CLEAN_AUDIT_TRAIL

  audit_trail_type-online DBMS_AUDIT_MGMT. AUDIT_TRAIL_DB_STD,

  use_last_arch_timestamp-online true);

  END;

  /

  - -

  HTH - Mark D Powell.

• What are the advantage and disadvantage for Standy physical and logical standby

  Hello
  
  What are the advantage and disadvantage for Standy physical and logical standby configuration?
  
  Thank you
  Ken

  Just to add the open text of Vihang Astik that for physical standby, with 11g you can now have the database read write (new features).

• VPN audit trail

  NetPro dear friends,

  I use Cisco ACS 5.1 to authenticate VPN users that connect to our servers. Some users connect to the database, some connect to web services, etc. Is there a feature or function ACS from the inside audit trail users to keep track of what they did while they were connected. If this isn't the case, so please guide me what third-party device or software to use for this.

  Thanks and greetings

  Faiz

  You can use the Balabit Shell control box to record all activities

• 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

• Cannot start db &gt; ORA-09925: cannot create the audit trail file

  version 10.1.0.5.0
  AIX 3 5 00C9CEA04C00 dcxnim01
  
  When I'm trying to start db, getting this message any idea?
  
  SQL > connect virtue sysdba;
  ERROR:
  ORA-09925: cannot create the audit trail file
  IBM AIX RISC System/6000 error: 89: invalid file system control data detected
  Additional information: 9925
  ORA-09925: cannot create the audit trail file
  IBM AIX RISC System/6000 error: 89: invalid file system control data detected
  Additional information: 9925
  
  
  Here's the tail of the log of alerts
  
  3 Private_strands to the log command
  Thread 1 Advanced for you connect to sequence 3923
  Currently journal # 1, seq # 3923 mem # 0: /db01/oradata/ldapdcx1/ldapdcx1/redo01.log
  Fri 6 Aug 16:48:34 2010
  Errors in the /oracle/admin/ldapdcx1/bdump/ldapdcx1_j001_991348.trc file:
  [ORA-07445: exception encountered: core dump [] [] [] [] []]
  Fri 6 Aug 16:48:35 2010
  Errors in the /oracle/admin/ldapdcx1/bdump/ldapdcx1_mmnl_508106.trc file:
  [ORA-07445: exception encountered: core dump [] [] [] [] []]
  Fri 6 Aug 16:48:38 2010
  Errors in the /oracle/admin/ldapdcx1/bdump/ldapdcx1_ckpt_839714.trc file:
  [ORA-07445: exception encountered: core dump [] [] [] [] []]
  ORA-27072: IO file error
  IBM AIX RISC System/6000 error: 5: i/o error
  Additional information: 9
  Additional information: 3
  Fri 6 Aug 16:48:38 2010
  Errors in the /oracle/admin/ldapdcx1/bdump/ldapdcx1_lgwr_905470.trc file:
  [ORA-07445: exception encountered: core dump [] [] [] [] []]
  ORA-27063: number of bytes read or written is incorrect
  IBM AIX RISC System/6000 error: 5: i/o error
  Additional information:-1
  Additional information: 1024
  Fri 6 Aug 16:49:07 2010
  Errors in the /oracle/admin/ldapdcx1/bdump/ldapdcx1_pmon_848078.trc file:
  ORA-00470: LGWR process ended with the error

  IBM AIX RISC System/6000 error: 5: i/o error
  Additional information:-1

  Problem of the OS.
  What is the problem at the level of the BONE with the disc?

  unpacking of tail - 100

• Audit trail decreases performance on 11g?

  Oracle 11g DB actually active function of standard audit via DBCA trail.
  
  Could - what someone knows how the negative impact of this function is?
  
  Y at - it references (almost 5% performance impact)?
  
  
  THX so much.

  All Performance Audit is purely based on the specific environment and there is no impact defined as an optimal value.
  For example, if you SELECT no matter WHAT TABLE and then thousands of running SELECT statements, you can see a negative impact and are not a good approach to your appearance.

  You can check the below link for the statements for which checking can be enabled.
  http://download.Oracle.com/docs/CD/B28359_01/network.111/B28531/auditing.htm#CEGGCIAE

  Generally, you do not perform these actions as a SELECT statement, and so performance is not much affected. I have no idea on what you need, however, FGA can be your choice with the condition more detail.

• 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