A single audit trail is collected for each privilege check. Sometimes, another SQL is executed as an extension to an executed SQL. In this case, HiRDB also collects an audit trail during privilege checking for the SQL that is executed as an extension to the original SQL. For details, see 24.13 Audit trail record items (during privilege checking).

When an event terminates, HiRDB collects an audit trail for each object that was the target of the event. However, for a consecutive certification failure account lock state that is released because the account lock period has passed, the audit trail is collected not when the account lock period has passed, but when the next event occurs after the passage of the account lock period.

• When CONNECT is executed
• When DROP CONNECTION SECURITY is executed
• When the pdacunlck command is executed

For details about the audit trail output patterns at event termination, see 24.3 Audit trail output patterns.

For details about the audit trails that are output at event termination, see 24.14 Audit trail record items (at event termination).