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

Tags: Database

Similar Questions

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

    Hello

    I know that a strong recommendation for 11g is that we house the SYS. AUD$ and SYS. FGA_LOG$ table in a tablespace SAMS and certainly NOT the system tablespace.

    However, I am struggling to find anywhere where it says the same for previous versions of the database - specific 9i and 10g.

    I thought I had read somewhere that Oracle do not support move the tables out of the SYSTEM tables audit trail in previous versions, but I can't find where I read that.

    Basically, I presume I can create a tablespace of VERIFICATION that uses the SAMS and move the tables on 9i / 10g? (Yes, I know things being out-of-support - application vendor has not yet certified 11 g!)

    Mark

    Erman Arslan says:
    Yes... interesting... maybe he can perform certain operations such as upgrade version and that is why it s not supported...

    But knowing how do has been public knowledge for several versions and is very common. I have been at this since 7.3 and have never heard a question resulting from travel sys.aud$ and he associated with the index another tablespace. And that's really it, that is. If you look at the script "unsupported" provided by oracle, you will set it's just move a table and rebuild its indexes. No tricks Super hidden guru.

    The question is not SAMS vs non-SAMS. It is a very volatile table of the TS system.

  • 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

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

  • 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

  • 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

  • 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

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

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

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

  • 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

  • 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

  • Can I sent some info custom as the name of the db in my audit standard audit trails?

    Hello

    I want to register my audit trails db name while doing a standard audit. Audit process can you provide some contexts custom as the name of the comic?

    Hello

    In 11 GR 2, the only custom value that can be set and which is also found in the audit trail is the aud$ .clientid that you can set with dbms_session.set_identifier.

    in 12 c with Unified audit there is a new feature to include data of application context in the audit trail to the statement of VERIFICATION OF NAMES of CONTEXT,

    Greetings,

    Damage ten Monkshood

  • 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

  • Apex - with the external database audit trail

    I'm currently installing a primitive audit trail that allows me to record data, create users, update, update user. I currently have 3/4 but I can not get the user name in the database like V ('APP_USER') is at the top and the database in Oracle 10 G elsewhere.

    Suggestions or alternative ideas?

    f1f7a787-7f56-4451-8300-5a9a0215226b

    If v() and apex_application.g_user are not available in the trigger on the external database code.

    But the external database package variables and procedures are available on the database running APEX.

    What I would do, is to create a package with a package variable that will contain the user of the apex. (in the external database)

    Then, in the application definition > session database > initialization code PL/SQL defined this package to the apex user variable.

    Clear the package again variable in the cleanup code.

    Using a package variable means that the value is aviable at the session of entire database but not outside the East.

    Apex every page load or submit and load next page is a database session.

    Now the package variable will be set when a user of the apex and the null value when there is a database user.

    Using an nvl around the package with user variable as an alternative, will give you the user apex when the action was made by a user of the apex and the database user is not.

    Nicolette

    PS change your handle or at the signing of all least your post will result in a more friendly welcome message.

Maybe you are looking for