| Transaction Notifications (ttaud1510m000) |  |
| Use this session to view the transaction notifications for a particular company and table. When changes to audited fields are saved, the transactions are first logged in the audit files, and subsequently are committed the database: when a transaction is logged in the audit files, the transaction gets the "Prepared" status and the bshell creates a transaction notification. A transaction notification contains the transaction ID and information on where to find the transaction information in the audit sequence file. Transaction notifications: can be used as a trigger for any process that needs to react to database changes such as a replication process. enable fast access to the audit trail data. are written into the Transaction Notifications (ttaud110) table in the database. The user transaction and the corresponding transaction notification are committed in the database within the same transaction scope: if the transaction is committed, the bshell writes the transaction notification into the Transaction Notifications table. In the audit file, the transaction status is changed to "Committed". if the transaction is aborted, the bshell does not write the notification. In the audit file, the transaction status is changed to "Aborted". This mechanism ensures that transaction notifications are only stored for transactions that are committed in the database. A replication process that is based on transaction notifications will therefore only replicate committed transactions. Example A transaction, "A", is saved in the audit file and a transaction notification is generated. The transaction is committed and the transaction notification is saved in the Transaction Notifications table. Another transaction, "B", is saved in the audit file and a transaction notification is generated. However, this transaction fails: the transaction is not committed and the transaction notification is not saved in the Transaction Notifications table. A replication process is used to transfer changes to another system. The replication process reads the Transaction Notifications table. Therefore only transaction "A" will be replicated. Note s Transaction notifications are the replacement of the two-phase commit protocol used in previous versions. They eliminate the in-doubt transactions that can occur if the transaction is prepared but the data is not yet committed or aborted. Refer to the Infor Enterprise Server 8.6 Technical Manual (U8172 US) for more details.
Fields | Description
Transaction ID | The transaction identification number.
Table number | A sequence number that indicates the order in which tables, within the same transaction, are updated. For example: a transaction (ID 10609546320000042619) performs the following actions in two tables (A and B): Update a row in table A Update a second row in table A Update a row in table B Update a third row in table A Two transaction notifications are generated for transaction 10609546320000042619: A notification for table A. The table number is 1, since the first update in the transaction is in table A. This notification contains information on where to find the audit information for the three update actions on table A. A notification for table B. The table number is 2. This notification contains information on where to find the audit information for the update action on table B.
Session | The name of the session that was used to perform the transaction.
User | The name of the user that performed the transaction.
Commit Time | Displays the UTC date and time at which the transaction was committed.
Index to Audit Files | The sequence number of the audit sequence file in which the transaction information is logged.
Offset in File | A number that indicates the position, in the audit sequence file, of the first log data of the first database action on the table.