IBM Support

PM70987: SQLCODE803 FROM QAPPLY CAN RESULT FROM QCAPTURE INCORRECTLY PROCESSING A GLOBAL TRANSACTION.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Qapply can issue sql0803n because qcapture incorrectly processed
    a global transaction causing qapply to process the rows out of
    sequence.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: 1- capture                                   *
    *                 2- Q Apply                                   *
    *                 3- capture                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1- -803 or transactions applied out of  *
    *                      order                                   *
    *                      2- Q Apply should report additional     *
    *                      source side information like row        *
    *                      intentseq, jobname and plan name in     *
    *                      the diagnostic log when following any   *
    *                      conflict_action / error_action since    *
    *                      such information is missing in          *
    *                      Exceptions table.                       *
    *                      3- SQL -310 when inserting in CD table  *
    *                      after a DECIMAL NOT NULL was added to   *
    *                      the CD table.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1- In a high volume scenario with global transactions, a small
    transaction that occurs after the global transaction may be
    replicated before the global transaction. This is due to the
    commit log record handling and how db2 releases locks on the
    first commit log record of the global transaction.
    2-  Customers require additional source side information like
    row intentseq, jobname and plan name to be reported in Q Apply
    diagnostic log when conflicts or sql errors are encountered
    when applying replicated rows. Such information is not
    currently available in IBMQREP_EXCEPTIONS table.
    3- Capture does not populate the default value for the DECIMAL
    NOT NULL properly when inserting into the CD table.
    

Problem conclusion

  • 1- Capture will preserve the order of transactions with respect
    to global transactions.
    2- Q Apply will report row intentseq, job name and plan name in
    the diagnostic log for any conflict / sql error reported in
    Exceptions table.
    3- Capture will properly insert the DB2 default for a DECIMAL
    NOT NULL in the CD table.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM70987

  • Reported component name

    WS REPLICATION

  • Reported component ID

    5655L8800

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-08-15

  • Closed date

    2012-09-07

  • Last modified date

    2012-10-01

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

    PM70033

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

    UK81624 UK81625 UK81626 UK81627

Modules/Macros

  •    ASNACMD  ASNADMSP ASNAPPLY ASNCAP   ASNCCMD
    ASNCDINS ASNMCMD  ASNMIG8  ASNMON   ASNMONIT ASNPLXFY ASNQACMD
    ASNQAPP  ASNQAROW ASNQCAP  ASNQCCMD 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 UK81624

       UP12/09/18 P F209

  • RA11 PSY UK81625

       UP12/09/19 P F209

  • RA12 PSY UK81626

       UP12/09/18 P F209

  • RA13 PSY UK81627

       UP12/09/18 P F209

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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
01 October 2012