Error modes for writing to an audit file
If the database server encounters an error when it writes to the audit file, it can behave in various ways called error modes. You can change the error mode, as Setting the error mode describes, at any time during database server operation, even after an error occurs. See also the explanation of onaudit error modes in The onaudit utility: Configure audit masks.
Halt error modes
When the database server is in a halt error mode (1 or 3), it does not allow the session that received the error to continue processing after it writes to the audit trail. The database server might even terminate the session or shut down, depending on the error mode. Descriptions of halt error modes follow:
- Mode 1: A thread is suspended but the session continues when the audit record is successfully written.
- Mode 3: The database server shuts down and the user session cannot continue.
Processing for the session does not continue until the error condition is resolved.
Continue error mode
When the database server is in continue error mode (0), it allows the session that received the error to continue processing after it writes to the audit trail. However, the audit record that was being written when the error occurred is lost. The database server writes an error to the message log stating that an error made while writing an audit record has occurred.
If the error continues to occur, all subsequent attempts to write to the audit trail also generate messages in the message log, which can quickly grow very large.