audit record

If you did not use the REQUIRES_NEW attribute on the audit method, the audit record would be rolled back along with the attempted trade.

Table 2 summarizes the meaning of each of the fields in the audit record for the AUDIT event type shown in Listing 3 and Listing 4.

Consult the DB2 UDB documentation for a description of the audit record layouts for the other event types.

In this configuration, the event generating the audit record must wait until the record is written to disk before returning its status.

From the query results, shown in Listing 8, you can see that one audit record was generated for the failed update statement.

With synchronous log writing, one record may be lost because the error could only prevent, at most, one audit record from being written.

Table 1 lists the different types of database events that can be audited and describes when an audit record is generated.

The first argument represents the file name and the second argument, the audit record.

A simple approach is to generate the audit record in an XML representation. We could then use an audit table with the following format

Each audit record consists of a single line, in the following format

initiating an independent audit record thread, and tracking the audit log set by using the independent audit record thread;

One row for each audit record