Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    How do we turn off (Oracle) system auditing in Aleph 20?

    • Article Type: General
    • Product: Aleph
    • Product Version: 20, 21, 22, 23

    Description: 

    How do we turn off (Oracle) system auditing in Aleph 20?

     

    Resolution: 


    Aleph 500 version 20 uses Oracle 11. The default of Oracle 11 is to define the system auditing as "enabled".
    We have discovered cases where this causes the Oracle tablespace SYSAUX to fill up. (See article Unable to extend table SYS.AUD$ by 128 in tablespace.SYSTEM)
    Therefore, we recommend that all libraries on version 20 disable (define as not active) the system auditing. All future installations will already have the auditing defined as not active.

    First, check to see if system auditing enabled on your server:
    > sqlplus $ALEPH_ADMIN
    aleph_admin@ALEPH20> show parameter audit_trail

     

    If it states the following with "DB", then the auditing is on:
    audit_trail string DB
    If it states the following with "NONE", then the auditing is off:
    audit_trail string NONE
    (and there is no need to do anything).

    Second, for your convenience we have prepared a fix_sysaux.bash script which automatically disables the auditing.

    Note:
    *****************************************************************************
    Before doing the following make sure the mount point where the Database files are located has at least 3 GB free space.
    During the running of the script you will be prompted regarding this.
    This should be checked on the DB server using the command df -h

    In addition, the script checks if an spfile exists for your DB. If it does not,
    then the script will ask you to open your parameter file at the end
    and change the parameter audit_trail to NONE. For example:
    audit_trail=NONE

    > cd /tmp
    > ftp ftp.exlibrisgroup.com
    Connected to ftp.exlibrisgroup.com
    220 Serv-U FTP Server v9.3 ready...
    Name (ftp.exlibris.co.il:aleph): produser
    331 User name okay, need password.
    Password: xxxxxx    [Contact Ex Libris Support; the password is in an Internal Note..]
    230 User logged in, proceed.

    ftp> cd product_patches
    ftp> get fix_sysaux.bash
    ftp> quit


    Execute the script using: bash fix_sysaux.bash <application_dba_password>

    For example:

    For Primo:

    bash fix_sysaux.bash primo_dba


    For Aleph:

    bash fix_sysaux.bash aleph_dba

    After doing this, the change will be in effect only after you have: stopped Aleph, restarted Oracle, and restarted Aleph.


    • Article last edited: 2/6/2016