IBM Support

JR58954: CHOOSE THE MINIMUM RESTART POSITION AND THE MINIMUM COMMIT+CURRENT INDEPENDENTLY FOR GROUP START

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • choose the minimum restart position and the minimum
    commit+current independently for group start
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    *                                                              *
    * For IDR/CDC  IDR/CDC 11.4.x:                                 *
    * This issue may affect you if you use IDR/CDC 11.4.0.0-5058   *
    * for all LUW engines or lower.                                *
    *                                                              *
    * For IDR/CDC 11.3.x:                                          *
    * This issue may affect you if you use IDR/CDC 11.3.3.3-78 for *
    * all LUW engines or lower.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * CHOOSE THE MINIMUM RESTART POSITION AND THE MINIMUM COMMIT + *
    * CURRENT INDEPENDENTLY FOR GROUP START                        *
    *                                                              *
    * More details:                                                *
    * When a subscription starts and the shared scrape staging     *
    * store is empty, we need to determine the bookmark to use as  *
    * the begin bookmark for the staging store.                    *
    *                                                              *
    * Method in IDR/CDC product (internal) does the following:     *
    *                                                              *
    * Determine the subscription bookmark that should be used for  *
    * starting the log parser when the change log does not exist   *
    * yet. Called when a subscription asks if it can use shared    *
    * scrape.                                                      *
    * Product will iterate through all subscriptions that are      *
    * currently running.                                           *
    * These subscriptions could be running a describe, stand alone *
    * refresh, or mirroring.                                       *
    * Product will exclude any that are not mirroring.             *
    * Product will use the earliest bookmark of all subscriptions  *
    * that are just starting mirroring.                            *
    * This is so they can all use shared scrape.                   *
    * If product just pick the first one that makes it to shared   *
    * scrape, then any subscriptions whose bookmark is earlier     *
    * will not be able to use shared scrape.                       *
    *                                                              *
    * Product determine the "earliest bookmark" based on           *
    * commit+current position.                                     *
    * Product do not consider the restart position.                *
    * Product assume the bookmark with the earliest commit+current *
    * position will also have the earliest restart position.       *
    * It is possible that one subscription has the earliest        *
    * commit+current position but another has the earliest restart *
    * position.                                                    *
    * Product should compute the earliest restart position from    *
    * all subscriptions starting, and then compute the earliest    *
    * commit+current position from all subscriptions starting, and *
    * then create a new bookmark that is the combination of the    *
    * two.                                                         *
    * In most cases, this bookmark will be the same as one of the  *
    * subscription bookmarks but may not be.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • For IDR/CDC 11.4.x:
    Upgrading to IDR/CDC 11.4.0.0-5059 for all LUW engines or newer
    resolves the issue.
    
    For IDR/CDC 11.3.x:
    Upgrading to IDR/CDC 11.3.3.3-80 for all LUW engines or newer
    resolves the issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR58954

  • Reported component name

    IS DATA REPLICA

  • Reported component ID

    5725E3000

  • Reported release

    B33

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-22

  • Closed date

    2020-04-24

  • Last modified date

    2020-04-24

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

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

Fix information

  • Fixed component name

    IS DATA REPLICA

  • Fixed component ID

    5725E3000

Applicable component levels

  • RB33 PSY

       UP

  • RB40 PSY

       UP

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

Document Information

Modified date:
11 June 2020