PM84879: Q CAPTURE ISSUE WITH COMPATIBILITY 0907

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Q Capture issue with compatibility 0907
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: 1- All                                       *
    *                 2- Q Capture                                 *
    *                 3- Capture                                   *
    *                 4- SQL Apply ASNLOAD sample                  *
    *                 5- no data                                   *
    *                 6- All Q Capture users                       *
    *                 7- SQL Capture, Q Capture                    *
    *                 8- Capture                                   *
    *                 9- Capture                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1- Users cannot start capture after     *
    *                      migration to V1001 archlevel.           *
    *                      2- Capture comes down unexpectedly      *
    *                      with compatability=0907 trying to put   *
    *                      a message on queue                      *
    *                      3- Capture missing data due to DB2 IFI  *
    *                      returning log records out of order.     *
    *                      4- ASNLOAD sample program fails to      *
    *                      connect to db2 v10                      *
    *                      5- no data                              *
    *                      6- The 'endscope + 1' optimization was  *
    *                      incorrectly applied to the very first   *
    *                      IFI call                                *
    *                      7- Capture overlays storage when it     *
    *                      reads spilled rows from a second spill  *
    *                      data set for a transaction.             *
    *                      8- ASN0192E and ASN7139E do not show    *
    *                      the version number                      *
    *                      9- ASN0621E error issued when we get    *
    *                      C9000A error from DB2                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1- Capture cannot read old restart message and LSN/MAXCMTSEQ
    command line parameters do not allow setting restart points per
    send queue.
    2- A field is not initialized and causes segmentation fault.
    3- In Datasharing log records may be returned by IFI out of
    order
    4- ASNLOAD sample program incorrectly checks db2 version and
    results in the connection failure
    5- no data
    6- The first log record Q Capture would process on startup was
    restartLSN + 1, which could mean a valid log record is skipped.
    7- Capture maintains a linked list of rows for each transaction
    it has built in memory.  Capture removes each row it spills
    from the linked list after it deletes the row.  Capture
    sometimes updates one linked list pointer incorrectly when it
    spills transaction rows to a second spill data set.
    8- The version number is helpful for diagnosis.
    9- Previously, a DB2 C9000A error only dealt with EDITPROC,
    that is no longer the case
    

Problem conclusion

  • 1- OVERRIDE_RESTARTQ-D will allow users to start capture after
    migration.
    2- Uninitialized field is fixed.
    3- Issue ASN0693 when we detect out of order log records.
    4- remove the incorrect db2 version check from the sample
    program
    5- no data
    6- The problem is resolved, Q Capture log processing will
    always resume at the correct LRSN
    7-  Capture will updates row linked list pointers correctly
    when it spills transaction rows to a second spill data set.
    8- New ASN0691E message is issued and includes version number.
    9- ASN005E will be issued when we see a C9000A error from DB2
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM84879

  • Reported component name

    WS REPLICATION

  • Reported component ID

    5655L8800

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-14

  • Closed date

    2013-05-02

  • Last modified date

    2013-06-04

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

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

    UK94013 UK94014 UK94015 UK94016

Modules/Macros

  • ASNAAPP  ASNACMD  ASNACMP  ASNADMSP ASNAFET
    ASNAISO  ASNAMAN  ASNAPPLY ASNAPRS  ASNAWPN  ASNCAP   ASNCCMD
    ASNCCPWK ASNCDINS ASNCTLZD ASNLOAD  ASNMCMD  ASNMIG8  ASNMON
    ASNPLXFY ASNPRUNE ASNQACMD ASNQAPP  ASNQAROW ASNQCAP  ASNQCCMD
    ASNQCTLZ ASNQDEP  ASNQEXRP ASNQMFMT ASNQMZ10 ASNQXFMT ASNQ1001
    ASNRBASE ASNSMZ10 ASNS1001 ASNTDIFF ASNTDSP  ASNTDSQL ASNTRC
    ASNUOW   ASN2BASE
    

Fix information

  • Fixed component name

    WS REPLICATION

  • Fixed component ID

    5655L8800

Applicable component levels

  • RA10 PSY UK94013

       UP13/05/10 P F305

  • RA11 PSY UK94014

       UP13/05/12 P F305

  • RA12 PSY UK94015

       UP13/05/10 P F305

  • RA13 PSY UK94016

       UP13/05/12 P F305

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.



Rate this page:

(0 users)Average rating

Document information


More support for:

InfoSphere Replication Server

Software version:

A10

Reference #:

PM84879

Modified date:

2013-06-04

Translate my page

Machine Translation

Content navigation