Other parameters of audit files
The location of the audit files is controlled as described in Location of audit files.
The user can control other parameters, as defined in a file named $BSE/lib/audit_spec.
Information file
The tables for which audit trail is enabled can contain sensitive data such as company financial information. Therefore, the audit files also contain sensitive data. Audit management contains a security mechanism by which access to the audit-data can be controlled according to user requirement.
A security level is defined for each table/company number combination.
Depending on the security level, users either can or cannot access or modify
the audit data. The audit server reads the security level from the
audit_spec file and stores the security level in the
information file of the table.
The central audit management utility, uses this security level to control audit-data access and modification.
See Audit management.
Sequence file
The start sequence number for a table is fixed and always
000. The end sequence number for a table is specified
in the
audit_spec file. For example, if the end sequence
number for the ppbdb000 table in company
000 is
999, the table has these sequence files:
abdb000000.000
abdb000000.001
....
abdb000000.998
abdb000000.999For the same table, if the end sequence number is 50, the files are:
abdb000100.000
abdb000100.001
abdb000100.002
....
abdb000100.049
abdb000100.050In principle, all audit-data for a table/company number combination can be written to a single sequence file. But because this file becomes too large to manage properly, the audit-data is split across multiple sequence files.
The maximum size of a sequence file for a table is defined in the
Audit_spec file. If the limit is exceeded, the audit
server tries to use the next sequence file.