IBM Support

PH27793: IF INTEGRATED SYNCHRONIZATION IS FORCED TO RESTART, AN ERROR MSGLIKE "2 ROWS PARSED, BUT APPLY CHANGED 4 ROWS" MAY OCCUR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • If IBM Integrated Synchronization (InSync) is forced to restart
    (due to network issue, db2z is down, ...) while some
    tables have ongoing replication work, the InSync crash recovery
    process may apply changes between last commit log position and
    the restart log position again.
    As a result, an error message like "2 rows parsed, but apply
    changed 4 rows" may occur.
    The target table will be set to replication ERROR state.
    A RELOAD is required to enable replication for the table again.
    
    The issue has been fixed with maintenance level 7.5.2.
    
    Additional Keywords:
    TS003938760 InSync crash recovery inconsistent table
    

Local fix

  • Use stored procedure ACCEL_LOAD_TABLES to reload the affected
    table on the accelerator.
    

Problem summary

  • In case Integrated Synchronization restarted unexpectedly while
    there is active Insert/Update/Delete operation on the
    replication-enabled table, the crash recovery process might
    incorrectly be restarted from an earlier log position.
    As a result, Integrated Synchronization could mistakenly apply
    the changes between last commit log position and the restart
    log position again. This will result in a replication event
    such as "2 ROWS PARSED, BUT APPLY CHANGED 4 ROWS".
    

Problem conclusion

  • Integrated Synchronization has been modified to correctly set
    the restart position during crash recovery.
    The fix is part of maintenance level 7.5.2.
    Upgrade your accelerator accordingly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH27793

  • Reported component name

    ANYTCS ACCLTR Z

  • Reported component ID

    5697DA700

  • Reported release

    750

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-07-23

  • Closed date

    2020-11-11

  • Last modified date

    2020-11-11

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"750"}]

Document Information

Modified date:
12 November 2020