Kbase P185869: How are the database recovery files, bi and ai effected by audit archiving?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/04/2011 |
|
Status: Unverified
GOAL:
How are the database recovery files, bi and ai effected by audit archiving?
GOAL:
How is the bi file effected by audit archiving?
GOAL:
How is the ai file effected by audit archiving?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.2x
FIX:
Since the default audit archiving is to dump all the audit records and then delete them, the bi file and ai file are effected as in any other delete operation. The amount of audit data collected is determined by your audit policies which will effect the number of deletes during the archiving operation.
You can choose to not delete the records, -nodelete, which is then only a read operation and no deletes notes are recorded. You can change the scope of the deletes, -recs num-recs, which could effect the bi growth.
The command is: proutil db-name -C auditarchive [date-range][-recs num-recs][-nodelete] [-checkseal] [-directory directory-name][-userid user-id [-password passwd]]
-nodelete Specifies that AUDITARCHIVE copy the audit data records to the archive file, leaving the audit data in the database. If not specified, AUDITARCHIVE will delete the audit data records as they are archived
-recs num-recs Specifies the number of records to delete in a single transaction. AUDITARCHIVE executes a transaction for every num-recs records it delete. The default for num-recs is 100, and the maximum is your current Lock Table Entries (-L) setting. The multi-user default for -L is 8192.