Fix Readme
Abstract
PTFs available for InfoSphere Data Replication for Db2 for z/OS v10.2.1 APARs
Content
PTF for APAR PH24517 for IBM InfoSphere Data Replication for Db2 for z/OS v10.2.1 (Q and SQL Replication) is available (June 2020)
PTF for APAR PH24517 fixes the following issues:
1) Capture ZOS retries MQCMIT, MQPUT and MQBACK when the first call returns error code, which causes message lost, as the second call may return OK
2) SQL Apply ASNLOAD UID does not conform with underscore character
3) During STOPQ or program stop, Q Apply browser and Prune thread may race to clean IBMQREP_DONEMSG entries and attempt to delete the same MQ message from RECVQ. If they encounter MQ rollback or fail to commit the deleted MQ message then it may cause incorrect deletion and consequently a reapply of an already applied MQ message on subsequent STARTQ or program restart.
4) ASNMAIL does not support multiple e-mail addresses recipients in one time. ASNMON does not support multiple e-mail addresses recipients for MONITOR_ERRORS.
5) Capture always checks the Db2 catalog to determine if the table is altered and needs to be REORG when activating a subscription.
6) The results are unpredictable when starting Capture using the timestamp option with a non data-sharing system.
7) Important information about the DB2 environment is not recorded in the log messages.
8) Q apply reports sql error -199 when replicating add column DDL of special temporal columns
9) Q Apply may go over MEMORY_LIMIT and cause memory exhaustion if monster transaction only involves row changes for a deactivated Q subscription.
10) Q Apply may issue ASN7551E gap detection error message too early when there are inflight transactions and PARALLEL_SENDQS=Y.
11) SQL Apply should perform TRUNCATE of target table before fullrefresh if its DATA CAPTURE CHANGES attribute is not set
ASNCLP: updated from db2_v111m4fp6 n2005261900
Samples: not updated
You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH24517.
PTF for APAR PH11918 for IBM InfoSphere Data Replication for DB2 for z/OS v10.2.1 (Q and SQL Replication) is available (April 2020)
PTF for APAR PH11918 fixes the following issues:
1) Q Capture displays ASN0725W plus diagnostic data and continues executing after its log reader detects out of order log records.
ASNCLP: not updated
Samples: not updated
You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH11918.
PTF for APAR PH11468 for IBM InfoSphere Data Replication for DB2 for z/OS v10.2.1 (Q and SQL Replication) is available (May 2019)
PTF for APAR PH11468 fixes the following issues:
1) The user cannot identify the UTILID used in ASNLOAD for a specific SQL Apply instance.
2) Remove the fix in APAR PH04272 for the "SQL Capture hangs reading 974 Meg transaction" issue because it causes excessive spill files.
3) New function: three new parameters have been added to the Q Apply IBMQREP_APPLYPARMS table (WARNTXLATENCY, WARNTXEVTS, and WARNTXRESET). Q Apply will use these columns to make the browser thread perform checks on committed and in-flight transactions to identify the transactions that are causing Q Apply to exceed latency.
ASNCLP: updated from db2_v105fp11 s190414
Samples: not updated
You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH11468.
PTF for APAR PH08697 for IBM InfoSphere Data Replication for DB2 for z/OS v10.2.1 (Q and SQL Replication) is available (March 2019)
PTF for APAR PH08697 fixes the following issues:
1) The Capture log reader makes READS calls for IFCID 306 that include a request to convert returned log records to the format for the table space version in which the data was written, but does not display an error message if Db2 cannot convert the log records.
2) Currently Capture fails when change_condition tokens do not start with $. Customers with CCSID like 1146 were using x'5B' instead of $ as their CHANGE_CONDITION tokens. With a previous APAR PI95748, Capture was changed to only allow $ as the token and it will display 'ASN7033E, An invalid search cond was detected for publication or Q subscription <sub name>', if a change condition variable does not start with a value of $.
ASNCLP: not updated
Samples: not updatenot updated
You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH08697.
PTF for APAR PH07326 for IBM InfoSphere Data Replication for DB2 for z/OS v10.2.1 (Q and SQL Replication) is available (February 2019)
PTF for APAR PH07326 fixes the following issues:
1) In multi-uni configuration, dropping multiple columns followed by reorg of table may cause ASN7512E error in apply at same node when the drop column gets replicated round trip back from other node.
2) Q Capture REINIT of an active subscription issues ASN7341W and does not send a schema message to Q Apply.
3) Q Capture issues ASN7138W each time it initializes a delimited subscription that has a IBMQREP_SENDQUEUES message_codepage that is not 1208.
4) Q Capture should check if the any source table columns have field procedures when it processes a CAPSTART signal. Q Capture checks if the source tables have any field procedures at start or reinit time and keeps this information in memory. If a subscription for a source table with a field procedure is activated, it is handled as a table without field procedures until Q Capture is recycled or a REINIT is issued. This causes incorrect data to be replicated or published.
ASNCLP: not updated
Samples: not updated
You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH07326.
PTF for APAR PH04272 for IBM InfoSphere Data Replication for DB2 for z/OS v10.2.1 (Q and SQL Replication) is available (December 2018)
PTF for APAR PH04272 fixes the following issues:
1) Q Apply gets SQLCODE -803 when it replicates a DELETE operation from an archive-enabled table if it also replicates the associated archive table and the default for the Db2 SYSIBMADM.MOVE_TO_ARCHIVE built-in global variable is 'E' or 'Y'.
2) SQL Capture inserts commit information into the IBMSNAP_UOW table even if SQL Apply does not need to join the CD tables with the IBMSNAP_UOW table.
3) SQL Capture hangs reading 974 Meg transaction.
ASNCLP: not updated
Samples: not updated
You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH04272.
PTF for APAR PH02594 for IBM InfoSphere Data Replication for DB2 for z/OS v10.2.1 (Q and SQL Replication) is available (October 2018)
PTF for APAR PH02594 fixes the following issues:
1) The Q Capture NMI server sends active workload metrics messages to NMI clients. The Q Capture NMI server receives a SIGPIPE signal if it sends a message to an NMI client after the NMI client terminates.
2) Q Capture loops when it restarts a bidirectional subscription after it detects a Db2 LOAD operation for the source table if it uses Db2 data sharing and capture_load = R.
3) The Q Capture XML format message cmitTime attribute value does not display microseconds if the value for microseconds is zero.
4) Q Capture XML format messages display invalid FLOAT data type values if the FLOAT data type value is zero.
ASNCLP: not updated
Samples: not updated
You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH02594.
PTF for APAR PH01808 for IBM InfoSphere Data Replication for DB2 for z/OS v10.2.1 (Q and SQL Replication) is available (September 2018)
PTF for APAR PH01808 fixes the following issues:
1) Capture cannot find the version of a table in the IBMQREP_TABVERSION table.
ASNCLP: not updated
Samples: not updated
You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH01808.
PTF for APAR PH00518 for IBM InfoSphere Data Replication for DB2 for z/OS v10.2.1 (Q and SQL Replication) is available (August 2018)
PTF for APAR PH00518 fixes the following issues:
1) The SQL Apply ASNLOAD exit calls the Db2 SYSPROC.DSNUTILS stored procedure to run Db2 utilities (LOAD, REPAIR).
2) Q Apply activates a Q subscription after it attempts to load the target table and the load fails.
3) Q Apply agents interrupted for program stop may commit a partially applied transaction if it encounters a rare race condition in message logging shutdown logic and attempts to directly issue a ASN message into IBMQREP_APPLYTRACE table and commit.
ASNCLP: updated from db2_v105fp11 n180809
Samples: updated ASNBNDDR, ASNBNDSR, ASNCAP, ASNCTLZD, ASNVSQL
You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH00518.
PTF for APAR PI99590 for IBM InfoSphere Data Replication for DB2 for z/OS v10.2.1 (Q and SQL Replication) is available (July 2018)
PTF for APAR PI99590 fixes the following issues:
1) Q Apply may not correctly replicate UPDATE row operations for system temporal table having columns that use generated always expressions on special register values (like SESSION_USER).
2) Q Capture may fail to activate a subscription with a valid SEARCH_CONDITION and reports ASN7200E stating that the SEARCH_CONDITION is using $OPERATION variable even though it does not.
ASNCLP: not updated
Samples: not updated
You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PI99590.
PTF for APAR PI97046 for IBM InfoSphere Data Replication for DB2 for z/OS v10.2.1 (Q and SQL Replication) is available (June 2018)
PTF for APAR PI97046 fixes the following issues:
1) Capture cannot advance its restart LSN while it processes a global transaction that does not commit or rollback.
2) Q Replication cannot support system period temporal tables that contain generated expression columns. DB2 V12 APPCOMPAT503 now provides ability to replicate to such tables with new global variable SYSIBMADM.REPLICATE_OVERRIDE='Y'
3) The Q Apply load function calls the Db2 SYSPROC.DSNUTILS stored procedure to run Db2 utilities (LOAD, CHECK DATA, REPAIR).
4) Batch and online processing are often running at the same time for some customers. A COMMIT_COUNT value that works well for online processing does not work for batch processing.
5) The Q Capture IBMQREP_CAPMON MAX_TRANS_SIZE column value is invalid if the maximum transaction size is larger than 2,147,483,647 bytes.
6) Q Apply may try to read entire monster transaction into memory instead of limiting memory usage within MEMORY_LIMIT settings. This could lead to memory exhaustion with ASN0543E reported.
ASNCLP: updated from db2_v105fp10 s180615
Samples: updated ASNCLPB, ASNQ1021, ASNQBNDL, ASNQCTLZ, ASNV1021
You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PI97046
PTF for APAR PI95748 for IBM InfoSphere Data Replication for DB2 for z/OS v10.2.1 (Q and SQL Replication) is available (April 2018)
PTF for APAR PI95748 fixes the following issues:
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.
ASNCLP: updated from db2_v105fp10 n180414
Samples: updated ASNQ1021
You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PI95748.
PTF for APAR PI94406 for IBM InfoSphere Data Replication for DB2 for z/OS v10.2.1 (Q and SQL Replication) is available (March 2018)
PTF for APAR PI94406 fixes the following issues:
1) Q Apply may crash during STOP processing if browser is stuck in DONEMSG cleanup for a long time.
2) Q Apply should not report exceptions for DUPLICATE / -803 sqlcode conflicts for CCD subscriptions that are Condensed=Y, Complete=Y . Also, DELETE conflicts for row not found cannot be forced, so should be reported as exceptions even when REPORT_EXCEPTIONS=N.
3) Capture stops without displaying an error message if it cannot decode a SYSIBM.SYSTABLES log record.
4) Q Capture should support TRANS_BATCH_INFO parameter setting from IBMQREP_CAPPARMS table and not just from command-line.
5) Capture hangs replicating a large transaction after a DB2 ROLLBACK if it has spilled the transaction to one or more spill data sets.
ASNCLP: updated from db2_v105fp10 n180315
Samples: not updated
You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PI94406.
PTF for APAR PI91673 for IBM InfoSphere Data Replication for DB2 for z/OS V10.2.1 (Q and SQL Replication) is available (February 2018)
PTF for APAR PI91673 fixes the following issues:
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
ASNCLP: not updated
Samples: not updated
You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PI91673.
Related Information
Was this topic helpful?
Document Information
Modified date:
05 June 2020
UID
ibm11099461