Shared Memory problem in secaudit

Former Member — Thu, 05 Oct 2006 20:19:58 GMT

Hi,

I see the following profile parameters in SM19 -> Environment -> Profile Parameters screen where the size of the audit file is set to 250000000:

DIR_AUDIT mod. /usr/sap/secaudit

of /usr/sap/PET/D00/log

FN_AUDIT mod. PET_00_++++++++_######.AUD

of audit_++++++++

rsau/enable mod. 1

of 0

rsau/local/file

mod. /usr/sap/secaudit/PET_00_++++++++_######.AUD

of /usr/sap/PET/D00/log/audit_++++++++

rsau/max_diskspace/local mod. 250000000

of 1000000

________________________________________________________

But when I execute the rsau_get_audit_config function

I get the following results where the max

file size is 1024:

VERSION 4

POSITION 1.048.500

ENABLE X

SLOTCOUNT 2

MAXFILESIZE 1.024

DATE 05.10.2006

CURFILESIZE 0

CURFILENUM 0

SIZEOFFILE 0

FILESTATUS 3

________________________________________________________

The inconsistent state leads to FILESTATUS = 3. What is the reason of the different results? What can I do?

thanks,

Re: Shared Memory problem in secaudit

Frank_Buchholz — Fri, 06 Oct 2006 14:43:28 GMT

The parameter MAXFILESIZE of function RSAU_GET_AUDIT_CONFIG shows the value of profile parameter rsau/max_diskspace/local with unit kB. -> ok

I assume that you execute the function and Tx SM19 on the same application server and therefore use the same profile parameter settings. -> ok

Please have a look into the trace file searching for the string "SecAudit" to ensure that the profile parameters are correctly loaded.

If this does not help I recommend to create a <a href="http://service.sap.com/message">Support Ticket</a>

Kind regards

Frank Buchholz