Manual Recovery from a Rollback

If you are unable to restore a Span Accessory parameter file corresponding to just before the rollback point, an audit discontinuity may occur. In this case, you will probably get an error message, such as one of the following:

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 <<<

DATABridge cannot continue replication until the audit locations in the parameter file are manually corrected using the following instructions.

To manually recover from a rollback

  1. Run Info Utility in Interactive Mode and enter the AFN and ABSN of the rollback point when you are prompted. Record the information when it appears. The result is similar to the following (the actual date and audit location numbers will vary). The following is an example.

    Quiet point found on January 30, 2010 @ 09:12:17 at audit location

    AFN = 18 ABSN = 17090 SEG = 9 INX = 10

  2. Get the Span Accessory parameter file.
  3. In the replication status information, enter the values from the DATABridge Info interactive report for each data set:

    Caution: Take precautions to enter the information from the DBInfo interactive report correctly. If the numbers aren't entered correctly, valid updates may be skipped. For example, if the AFN is 100, make sure that you enter 100 and not 102. Entering 102 would prevent you from getting updates from audit files 100 and 101.

    • From the Info interactive report, enter the AFN value for File Nbr.
    • From the Info interactive report, enter the ABSN value for Aud Block SerialNbr.
    • From the Info interactive report, enter the SEG value for Segment Number.
    • From the Info interactive report, enter the INX value for Word Index.
    • Change the date and time values to all zeros.(If you omit this, Span Accessory will fail with an invalid timestamp error or 0033, which indicates a corrupt audit file because of the invalid timestamp.)
    • Change the Mode to 2 if it is not already 2. (If you know that the value was something else, use that value; in most cases, however, the value will be 2. A value of 2 indicates that the data set is ready to be updated.)

    An example of the pertinent columns in the replication status information follows.

    %Data Rec File Aud Block Segment Word Date Time Mo- Format-Lvl

    %-set Type Nbr SerialNbr Number Index YYYYMMDDhhmmss de DMS Client

    %---- --- ---- --------- ------- ----- -------------- - ---- ----

    % .

    % .

    % .

    %0003 000 0018 0000017090 0000009 00010 0000000000000 2 00000 00000

  4. When you have finished making the changes to each data set, save the Span Accessory parameter file.
  5. Remove all of the previous Span Accessory UPDATES files to prevent the new files from appending on to the older files.
  6. Run the Span Accessory as usual.

    Caution: If the entered audit location does not exactly match the secondary database, or if you do not know the exact state of the secondary database, there is a possibility of record duplication or loss.