IBM Support

PI22983: MISSED UNIQUE DEPENDENCY SERIALIZATION WHEN SECONDARY UNIQUE INDEX IS A PROPER SUBSET OF REPLICATION KEY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Missed unique dependency serialization when secondary unique
    index is a proper subset of replication key
    

Local fix

  • Workaround is to make sure secondary unique index has
    at least one column that is not IS_KEY=Y.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: 1- Capture                                   *
    *                 2- Q Apply                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1- Capture never releases lock on       *
    *                      IBMQREP_TABVERSION.                     *
    *                      2- Q Apply may not serialize            *
    *                      transactions correctly if there exists  *
    *                      a unique index / constraint that is on  *
    *                      a  proper subset of columns used for    *
    *                      the replication key.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1- Capture did not commit to release locks after a query.
    2- Q Apply transaction serialization based on secondary unique
    index / constraint may miss unique dependencies if the
    secondary unique index is an exact proper subset of the
    replication key. This only affects subscriptions for tables
    that have secondary unique index, such that all columns of the
    secondary unique index have IS_KEY=Y in IBMQREP_TRG_COLS, but
    some columns with IS_KEY=Y are not part of the secondary unique
    index. The incorrect serialization of transactions may lead to
    data  divergence or conflicts on the target table.
    

Problem conclusion

  • 1- Capture never releases lock on
    IBMQREP_TABVERSION.
    2- Q Apply may not serialize
    transactions correctly if there exists
    a unique index / constraint that is on
    a  proper subset of columns used for
    the replication key.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI22983

  • Reported component name

    WS REPLICATION

  • Reported component ID

    5655L8800

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-07-30

  • Closed date

    2014-08-14

  • Last modified date

    2014-09-03

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

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

    UI20554 UI20555 UI20556 UI20557

Modules/Macros

  •    ASNACMD  ASNADMSP ASNAPPLY ASNCAP   ASNCCMD
    ASNMCMD  ASNMIG8  ASNMON   ASNPLXFY ASNQACMD ASNQAPP  ASNQCAP
    ASNQCCMD ASNQCTLZ ASNQDEP  ASNQEXRP ASNQMFMT ASNQXFMT ASNRBASE
    ASNTDIFF ASNTDSP  ASNTRC   ASN2BASE
    

Fix information

  • Fixed component name

    WS REPLICATION

  • Fixed component ID

    5655L8800

Applicable component levels

  • RA10 PSY UI20554

       UP14/08/25 P F408

  • RA11 PSY UI20555

       UP14/08/26 P F408

  • RA12 PSY UI20556

       UP14/08/25 P F408

  • RA13 PSY UI20557

       UP14/08/26 P F408

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDP5R","label":"InfoSphere Replication Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
29 April 2020