To create a transaction notification

The two-phase commit protocol used in previous versions has been replaced by the transaction notification. This eliminates the in-doubt transactions that can occur if the transaction is prepared but the data is not yet committed or aborted.

The bshell writes this transaction notification into a notification table in the database, within the user transaction. If the transaction commits, the bshell writes the transaction notification, and if the transaction aborts, the bshell does not write the notification. The bshell creates a transaction notification for each transaction that is logged in the audit trail.

The transaction notification contains the transaction ID and information on where to find the transaction information in the audit sequence file. These transaction notifications can be used as a trigger for any process that needs to react to database changes such as a replication process, and enables fast access to the audit trail data.