IBM Support

PH70625: Q Capture startup fails with ASN0552E due to SQLCODE -104. It will be a very rare situation for specific Db2 CCSID.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • IIDR/z PTF for March 2026
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: 1- all Q Capture users                       *
    *                 2- Customer those who are using              *
    *                 qrestartfile with override_restartq option   *
    *                 3- Users who want to identify the size of    *
    *                 spilled transactions.                        *
    *                 4- All SQL Capture users                     *
    *                 5- All Capture users                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1- Capture abend 0C4 when no SELECT     *
    *                      authority on tables with LOB/XML        *
    *                      columns                                 *
    *                      2- Refer the customer case              *
    *                      3- When capture spills a transaction,   *
    *                      if the current spill file size reaches  *
    *                      1GB, capture issues the ASN0673I        *
    *                      message, which includes the spill file  *
    *                      name, transaction ID, auth ID, auth     *
    *                      token and plan name, but it doesn't     *
    *                      include the transaction size.  The      *
    *                      total transaction size is helpful       *
    *                      because configuration changes might be  *
    *                      needed in order to replicate very       *
    *                      large transactions, for example, MQ     *
    *                      limits might need to be increased.      *
    *                      4- asncap issued too many ASN8999D      *
    *                      warning messages                        *
    *                      5- Q Capture startup fails with         *
    *                      ASN0552E due to SQLCODE -104.  It will  *
    *                      be a very rare situation for specific   *
    *                      Db2 CCSID. This was a regression        *
    *                      introduced in APAR PH69938              *
    ****************************************************************
    1- Q Capture abend 0C4 when the Capture ID does not have SELECT
    privilege on the source table with LOB/XML columns because the
    master sub has been removed after SELECT authority problem is
    first detected.
    2- QApply using wrong delete statement when there is a
    conflict_rule change
    3- Q Capture does not report a message with the transaction
    size when a transaction is spilled.
    4- The table was registered when the log begin record was
    processed in logRead(). But, due to a CAPSTOP signal, it was no
    longer registered. There are too many warning message like this
    "ASN8999D trans::insertTx: table[tid=65530,fid=32800] not
    registered"
    5- Capture issued a dynamic SQL statement with '!=' and the !
    is mistakenly swapped for Euro symbol based on the conversion
    table. As a result, Capture startup failed with SQLCODE -104.
    

Problem conclusion

  • 1- Q Capture is changed not to remove the master sub for
    rc=AsnRcWarnNoSelect after verifySelectForTable(). It will be
    removed only after the queue subscription has been deactivated.
    2- QApply should use the delete statement cache when there is a
    conflict_rule change.
    3- Total transaction size is now reported to the ASN0673I
    message, which is issued every 1GB of spilling.
    4- Capture is changed to print the message only if DEBUG=Y
    5- Changed to use '<>' operator instead of '!=' to avoid the
    conversion problem
    Note: ASNCLP has been updated from v1159 s2603291940.
    Function Level: 1140.103 and updated asnclp includes fix
    partition by sub
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH70625

  • Reported component name

    WS REPLICATION

  • Reported component ID

    5655L8800

  • Reported release

    B33

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2026-03-23

  • Closed date

    2026-04-01

  • Last modified date

    2026-04-04

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

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

    UO07376 UO07377 UO07378 UO07379

Modules/Macros

  • ASN2BASE ASN2SQLZ ASNACMD  ASNADMSP ASNAPPLY ASNCAP   ASNCATM
    ASNCCMD  ASNCLPAP ASNCLPCL ASNCLPCM ASNCLPCO ASNCLPMS ASNCLPQA
    ASNMCMD  ASNMON   ASNQACMD ASNQAPP  ASNQAROW ASNQCAP  ASNQCCMD
    ASNQDEP  ASNQEXRP ASNQMFMT ASNQXFMT ASNRBASE ASNSQLCZ ASNTDIFF
    ASNTDSP  ASNTRC
    

Fix information

  • Fixed component name

    WS REPLICATION

  • Fixed component ID

    5655L8800

Applicable component levels

  • RB33 PSY UO07376

       UP26/04/03 I 1000

  • RB34 PSY UO07377

       UP26/04/04 I 1000

  • RB35 PSY UO07378

       UP26/04/03 I 1000

  • RB36 PSY UO07379

       UP26/04/03 I 1000

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":"BU029","label":"Software"},"Product":{"code":"SSDP5R","label":"InfoSphere Replication Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B33"}]

Document Information

Modified date:
04 April 2026