A fix is available
APAR status
Closed as program error.
Error description
When trans_batch_sz>1, Q replication uses wrong COMMITSEQ value for transactions to CCD tables.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: 1- trans_batch_sz Users * * 2- All Capture customers * * 3- trans_batch_sz Users * **************************************************************** * PROBLEM DESCRIPTION: 1- In data sharing environment if * * trans_batch_sz>1 and * * LOGMARKERTZ=LOCAL, sometimes on target * * side LOGMARKER is 1 or 2 seconds less * * than COMMITSEQ for a CCD table. * * 2- Capture attached to DB2 V12.1.501 * * CM displays ASN0589I messages when it * * decodes DB2 V11 NFM SYSIBM.SYSCOLUMNS * * log records. * * 3- when trans_batch_sz>1, Q * * replication uses wrong COMMITSEQ value * * for transactions to CCD tables * **************************************************************** * RECOMMENDATION: * **************************************************************** 1- When capture publishes transmsg with trans_batch_sz>1, capture should send local commit time of last transaction of the transmsg. However capture sends local commit time of first transaction of the transmsg. It causes the inconsistency of COMMITSEQ and LOGMARKER in data sharing environment. 2- DB2 V12 migration writes DB2 V11 NFM SYSCOLUMNS log records. Capture attached to DB2 V12.1.501 CM cannot decode the DB2 V11 NFM SYSIBM.SYSCOLUMNS log records. 3- when trans_batch_sz>1, Q capture groups multiple transactions into one transaction message. However, one transaction message can only send commitLSN, auth id, auth token, plan name and uow id of one transaction. So capture only sends the set of the last transaction.
Problem conclusion
1- With this fix, capture sends local commit time of last transaction. 2- Capture attached to DB2 V12.1.501 CM is fixed to decode DB2 V11 NFM SYSIBM.SYSCOLUMNS log records. 3- With this fix, in transaction message, information of each transaction is added after the first row of the transaction, so that Q apply can decode them and use the correct commitseq of each transaction. ASNCLP was not updated.
Temporary fix
Comments
APAR Information
APAR number
PI91673
Reported component name
WS REPLICATION
Reported component ID
5655L8800
Reported release
A21
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-12-18
Closed date
2018-02-22
Last modified date
2018-04-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI54022 UI54023 UI54024 UI54025
Modules/Macros
ASNAAPP ASNACMD ASNADMSP ASNAPPLY ASNCAP ASNCCMD ASNMCMD ASNMON ASNQACMD ASNQAPP ASNQCAP ASNQCCMD ASNQDEP ASNQEXRP ASNQMFMT ASNQSPIL ASNQXFMT ASNRBASE ASNTDIFF ASNTDSP ASNTRC ASN2BASE
Fix information
Fixed component name
WS REPLICATION
Fixed component ID
5655L8800
Applicable component levels
RA21 PSY UI54022
UP18/03/02 P F803
RA24 PSY UI54023
UP18/03/02 P F803
RA25 PSY UI54024
UP18/03/02 P F803
RA26 PSY UI54025
UP18/03/02 P F803
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:
03 April 2018