Anomalies That Can Occur In Updates

When the DATABridge Client updates the relational database, the following anomalies can occur:

Last quiet point (QPT) in an audit file

When processing an update transaction group since the last quiet point, DBEngine or DBEnterprise does the following when it reaches the end of the last available audit file:

  • Aborts the current transaction group so that the updates are rolled back. These are not duplicate updates, but updates that could not be committed. These updates will be reapplied the next time you run a process command.
  • Sends the DATABridge Client a status indicating that the transaction group was rolled back. Upon receiving this status, the DATABridge Client does not display any messages.

Host application rolls back changes

(This is a partial DMSII rollback, not to be confused with a total DMSII rollback.)

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 sends an abort transaction status to the DATABridge Client and then reprocesses the transaction, excluding any updates by the program that rolled back its updates.