A fix is available
APAR status
Closed as unreproducible in next release.
Error description
Q Capture activates subscriptions that are defined with change conditions only if the database code page HEX value for the '$' character is x'5B'.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: 1- Q Apply with CCD targets when source Q * * Capture uses TRANS_BATCH_INFO = Y and * * TRANS_BATCH_SZ > 1 settings. * * 2- All Q Capture customers who use change * * conditions. * * 3- SQL Apply users * * 4- SMA5 SOMPO JAPAN * * 5- All Q Capture customers who use change * * conditions. * * 6- All Capture customers. * **************************************************************** * PROBLEM DESCRIPTION: 1- Q Apply may encounter spurious SQL * * errors like SQL0804N or SQL0302N while * * applying row changes for a CCD target * * in a Monster transaction sent by Q * * Capture started with settings * * TRANS_BATCH_INFO=Y and TRANS_BATCH_SZ * * > 1. * * 2- Q Capture abends with S0C4 at * * PostFixElement::compareString() + * * 0000073C after it processes a STARTQ * * or REINIT command. * * 3- SQL Apply / ASNLOAD failed with * * SORTKEYS error * * 4- ASNTDIFF error when code page of * * the primary key is 1208 * * 5- Q Capture activates subscriptions * * that are defined with change * * conditions only if the database code * * page HEX value for the '$' character * * is x'5B'. * * 6- Capture loses data when it * * replicates a rollback to a savepoint * * if the savepoint is the LRSN/RBA of a * * spilled row in the first spill data * * set and the row is not the first row * * of the transaction. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1- Q Apply monster transaction processing does not correctly handle batched transaction info sent by Q Capture started with TRANS_BATCH_INFO=Y and TRANS_BATCH_SZ > 1. This may lead Q Apply to use bad values for audit columns of a CCD target table leading to spurious SQLerrors such as -804 or -302. 2- Capture abends if it uses a change condition variable attribute that it has initialized. 3- When SQL Apply performs a fullrefresh using ASNLOAD exit and the sortKeysTotal value exceeds 2147483648 (2**31), DB2 utility will fail with INVALID OPERAND FOR KEYWORD 'SORTKEYS' because of buffer overflow. 4- ASNTDIFF goes through unnecessary code path when code page of primary key is 1208, which causes a sql error -330 5- Q Capture displays 'ASN7033E, An invalid search condition was detected for publication or Q subscription <subscription name>', if a change condition variable does not start with HEX value x'5B'. 6- Capture should read the first spill data set when it replicates a rollback to a savepoint if the savepoint is the LRSN/RBA of a spilled row in the first spill data set and the row is not the first row of the transaction.
Problem conclusion
Temporary fix
Comments
1- Q Apply monster processing is fixed to use correct batched transaction information when populating CCD audit columns. 2- Q Capture has been changed to initialize all change condition variable attributes. 3- Changed the attribute of the variable NUM_ROWS to long long. This will ensure the result from calculation for sortKeysTotal is in the correct attribute. 4- With this fix, ASNTDIFF will not go through the code path that causes sql error -330 5- Q Capture has been changed to use database code page information to parse subscription change conditions. 6- Capture will read the first spill data set when it replicates a rollback to a savepoint if the savepoint is the LRSN/RBA of a spilled row in the first spill data set and the row is not the first row of the transaction. Note: ASNCLP has been updated from db2_v105fp10 n180414.
APAR Information
APAR number
PI95748
Reported component name
WS REPLICATION
Reported component ID
5655L8800
Reported release
A21
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-03-26
Closed date
2018-04-19
Last modified date
2018-06-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI55340 UI55341 UI55342 UI55343
Modules/Macros
ASNACMD ASNADMSP ASNAPPLY ASNCAP ASNCCMD ASNCLPAP ASNCLPCL ASNCLPCM ASNCLPCO ASNCLPMS ASNCLPQA ASNLOAD ASNMCMD ASNMON ASNQACMD ASNQAPP ASNQBRWZ ASNQCAP ASNQCCMD ASNQDEP ASNQEXRP ASNQMFMT ASNQXFMT ASNQ1021 ASNRBASE ASNTDIFF ASNTDSP ASNTRC ASN2BASE
Fix information
Fixed component name
WS REPLICATION
Fixed component ID
5655L8800
Applicable component levels
RA21 PSY UI55340
UP18/05/02 P F805
RA24 PSY UI55341
UP18/05/02 P F805
RA25 PSY UI55342
UP18/05/02 P F805
RA26 PSY UI55343
UP18/05/02 P F805
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":"A21","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
04 June 2018