Recover from a DMSII Rollback

Use the following procedure to recover from a DMSII rollback in DATABridge Span. This procedure requires that you routinely back up your DATABridge Span parameter file. See Prepare for a DMSII Rollback. If you don't have these files, use the procedure in Manual Recovery from a Rollback.

To recover from a DMSII rollback

  1. Read the DMSII rollback report to determine the audit location of the rollback point. The report will indicate the AFN (audit file number) and ABSN (audit block serial number) of the rollback point, or earlier.

    Alternatively, if you run DATABridge Span before reloading an older parameter file, DBEngine will detect an audit location mismatch and try to find the rollback point in the audit trail. If it is successful, DATABridge Span will receive the result code 0120 DATABridge Engine: Database rolled back to AFN=afn ABSN=absn Seg=seg Inx=inx timestamp

  2. Restore the DATABridge Span parameter file that corresponds to the rollback point, or earlier.
  3. Remove any DATABridge Span output files that were created after the rollback point.
  4. If DATABridge Span appends updates to data files created by previous replication runs, you must copy the data files from the backup you made matching the parameter file you loaded in step 2.
  5. Run DATABridge Span as usual.

    If you get an error similar to either of the following, an audit discontinuity has occurred. See the next procedure, Manual Recovery from a Rollback.

    DATABridge Engine: >>> [0033] tablename: Audit location mismatch, subtype = value is wrong. Check for DMS rollback <<<

    DATABridge Engine: >>> [0092] Expected ABSN=nnnn in AUDITnnn at segment nnnn but found ABSN=mmmm <<<