Limit on the size of audit data

All audit data generated in a transaction for a table is always placed in a single sequence file. The transaction data is never split up across sequence files. If the current sequence does not have enough space to write the transaction data, that is, if the data size exceeds the maximum sequence size, the audit server tries to write the transaction data in the next sequence file. If the transaction data cannot be accommodated in the entire sequence file, the audit server cancels the transaction. If this occurs, the application programmer must either reduce the scope of the transaction or increase the maximum file size for the sequence file.