Rolled Back Updates

This section explains some anomalies that can occur when the DATABridge Client is updating the relational database, as follows:

• Last QPT in audit file
• Host application rolls back changes

Last Quiet Point in Audit File

After DBEngine or DBEnterprise has reached the end of the last available audit file while processing an update transaction group since the last quiet point, it does the following:

• Aborts the current transaction group so that the updates are rolled back. Note that these are not duplicate updates, but updates that could not be committed. These updates will be reapplied the next time you run the process command.
• Sends the DATABridge Client a status indicating that the transaction group was rolled back. Upon receiving this status, the DATABridge Client displays the message, "WARNING: Transaction group aborted by DBEngine; nnnnnn SQL operations rolled back."

Error in Host Application

If a host application encounters an error condition while updating the DMSII database, it rolls back all of the changes it made. In this case, DBEngine aborts the updates when it finds the aborted transaction indication in the audit file. DBEngine then sends an abort transaction status to the DATABridge Client.