IBM Support

InfoSphere Data Replication for Db2 for z/OS v11.4.0 updates

Fix Readme


Abstract

PTFs available for InfoSphere Data Replication for Db2 for z/OS v11.4.0 APARs

Content


PTF for APAR PH45910 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (June 2022)

PTF for APAR PH45910 fixes the following issues:

1) In Q Replication environment when unique indexes are created with include clause, Q Apply should exclude those columns for its check for unique dependencies.
2) Q Capture is not respecting the setting of SEND_RI_COLUMN_VALUES
3) Replicating data with CHAR to VARCHAR column mapping requires users to define column sql expressions for it. This may cause performance degradation due to overhead of pre-evaluating sql expressions if those columns are part of the replication key.
4) F jobname, status show details should show NMI socket and connection information or INSERT INTO !ASH.IBMQREP_APPLYCMD (CMD_TEXT) VALUES ('STATUS SHOW DETAILS'); should show NMI socket and connection information
5) Wrong column delimiter generated in MQ messages in Finnish DB2 subsystem

ASNCLP: not updated
Samples: not updated
Function Level: 1140.103

You can get more information and download the fix at https://www.ibm.com/support/pages/apar/PH45910.


PTF for APAR PH45229 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (April 2022)

PTF for APAR PH45229 fixes the following issues:

1) NUM_LOBXML_READ counter in IBMQREP_CAPQMON might be incorrect in some cases

ASNCLP has been updated from v1157 s2203231306.
Samples: ASNCLPB ASNCLPEV
ASNCLPB and ASNCLPEV samples have been modified to reflect support for Java 8.
The updated ASNCLP is compiled with Java 8 and requires Java 8 to run.
Function Level: 1140.103
This PTF refreshes all product files and has no pre-requisites.

You can get more information and download the fix at https://www.ibm.com/support/pages/apar/PH45229.


PTF for APAR PH44950 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (March 2022)

PTF for APAR PH44950 fixes the following issues:

1) Adding support for source KEY UPDATES can be split into a DELETE (which updates the original row) and an INSERT with the new values at CCD target
2) Adding support for all source UPDATES to be split into a DELETE/ INSERT for Non Condensed CCD) and key updates to be split into delete/insert for condensed
3) Q Replication does not support the CCD IBMSNAP_AUTHID column with lengths greater than VARCHAR(30).
4) Print capparm REINIT_ON_OUTORDER_LOG and change default to Y

Samples: not updated
Function Level: 1140.103

You can get more information and download the fix at https://www.ibm.com/support/pages/apar/PH44950.


PTF for APAR PH43905 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (March 2022)

PTF for APAR PH43905 fixes the following issues:

1) Need to add DROPTAB_ACTION support for SQL Capture. The same parameter is already supported by Q Capture.
2) A multi column ALTER TABLE..ALTER COLUMN..SET DATATYPE CHAR(...) that modifies multiple char columns to a length value of a larger size fails with multiple ASN7621E error messages in Apply when attempting to replicate the alters at the target.
3) ASNCATM incorrectly handles MQ_BYTES in CAPQMON and APPLYMON.
4) Need to analyze performance issues related to Capture's handling of XML columns
5) add counters for search_condition evaluation
6) Capture sends a corrupted transaction message: the first row may show an invalid sub_id.
7) Capture failed -206 when inserting to IBMQREP_CAPMON table
8) Update z/OS create control table samples with new columns

ASNCLP: not updated
Samples: ASNCATM ASNCTLZD ASNQCTLZ ASNVSQL
Function Level: 1140.103

You can get more information and download the fix at https://www.ibm.com/support/pages/apar/PH43905.


PTF for APAR PH43143 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (February 2022)

PTF for APAR PH43143 fixes the following issues:

1) Q Capture failed due to missing toolkit libraries.
2) ASN7173W should be written to console
3) Q capture encountered a free cell error and hang.
4) Negative value for trans_processed in IBMQREP_CAPMON after stopq/startq

ASNCLP: not updated
Samples: not updated
Function Level: 1140.103

You can get more information and download the fix at https://www.ibm.com/support/pages/apar/PH43143.


PTF for APAR PH42189 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (December 2021)

PTF for APAR PH42189 fixes the following issues:

1) Diagnostic message is printed incorrectly
2) QCapture ASN0569E error SIGSEGV

ASNCLP: not updated
Samples: not updated
Function Level: 1140.103

You can get more information and download the fix at https://www.ibm.com/support/pages/apar/PH42189.


PTF for APAR PH41040 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (November 2021)

PTF for APAR PH41040 fixes the following issues:

1) Q Capture abended when decoding COMMENT statement
2) Q Capture support of Db2 z/OS IFI306 filter by partition range
3) Q Capture looping when q is full and using parallel mq thread
4) SQL Apply should retry using DELETE when TRUNCATE target table fails with sqlcode -150

ASNCLP: not updated
Samples: not updated
Function Level: 1140.103

You can get more information and download the fix at https://www.ibm.com/support/pages/apar/PH41040.


PTF for APAR PH40710 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (September 2021)

PTF for APAR PH40710 fixes the following issues:

1) CURRENT_LOG_TIME shows invalid timestamp
2) Q Apply memory leak of NMI related monitoring metrics structures when processing disconnect from NMI client.
3) ignore HS invocation parameter for Q/SQL Capture
4) SQL Apply missing updates for event based subscription

ASNCLP: not updated
Samples: not updated
Function Level: 1140.103

You can get more information and download the fix at https://www.ibm.com/support/pages/apar/PH40710.


PTF for APAR PH39026 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (September 2021)

PTF for APAR PH39026 fixes the following issues:

1) ASNCATM does not handle new columns in IBMQREP_SRC_COLS and IBMQREP_CAPPARMS and indexes in the IBMQREP_DELAYIN AUXILIARY tables.
2) SQL Apply uses global variable SYSIBMADM.REPLICATION_OVERRIDE
3) SQL Capture retention limit pruning failed
4) CD/UOW rows are not pruned correctly
5) The command to ALTER a column of type CHAR to size 255 was failing and instead modifying to 254.
6) Db2 V13 EDITPROC support
7) SQL Apply failed in updateAny scenario
8) For the Q capture server control table IBMQREP_CAPMON, In 10.2.1 version, the MAX_TRANS_SIZE is integer data type, In 11.4.0 version, this column data type was changed to BIGINT, When one value stores this column in v11.4.0, The asnmon Not suited to its needs.
9) Customers are not warned if they make changes to target tables that affect unique indexes.
10) Customers would only get an error stating "subID mismatch" without any kind of diagnostic information to help them understand the cause of this error.
11) Q Capture reports `SQL0206N` when inserting into `IBMQREP_CAPMON`.
12) Invalid data in XML message from EP for Db2 table with float data

ASNCLP: not updated
Samples: not updated
Function Level: 1140.103

You can get more information and download the fix at https://www.ibm.com/support/pages/apar/PH39026.


PTF for APAR PH38468 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (July 2021)

PTF for APAR PH38468 fixes the following issues:

1) Q Capture messages to diagnose log reading in Db2 proxy mode

ASNCLP: not updated
Samples: not updated
Function Level: 1140.103

You can get more information and download the fix at https://www.ibm.com/support/pages/apar/PH38468.


PTF for APAR PH36439 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (June 2021)

PTF for APAR PH36439 fixes the following issues:

1) When customer got email alerts they need to open each email to see the detail information to see for which DB/SCHEMA/CONDITION name the warning message occurs.
2) SQL Apply high CPU consumption in ASNAISO after migration to DB2 V12
3) Add CAPTUREUPTO as Q Capture startup parameter

ASNCLP: updated from db2_v111m4fp7 s2106251900
Samples: not updated
Function Level: 1140.103

You can get more information and download the fix at https://www.ibm.com/support/pages/apar/PH36439.


PTF for APAR PH34805 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (April 2021)

PTF for APAR PH34805 fixes the following issues:

1) Q Event Publisher the table name in the delimited message header is incorrect.
2) When a Db2 clone table is dropped, Capture incorrectly identifies the base table as being dropped.
3) Capture should not display message ASN7137W message for subscriptions that have LOB_SEND_OPTION=I
4) The capture job log may grow too rapidly due to ASN7328I messages.
5) A new schema message was sent when the REINIT was issued to loading state subscription.

ASNCLP: not updated
Samples: not updated
Function Level: 1140.103

You can get more information and download the fix at https://www.ibm.com/support/pages/apar/PH34805.


PTF for APAR PH34515 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (February 2021)

PTF for APAR PH34515 fixes the following issues:

1) Capture misses the updates to the clone
2) Capture sends corrupted message when replicating same source table to multiple targets in multiple send queues. Example table T1 going to table T2, T3 and T4 in SENDQ1 and T1 going to TGT2, TGT3 and TGT4 in SENDQ2.

ASNCLP: not updated
Samples: not updated
Function Level: 1140.103

You can get more information and download the fix at https://www.ibm.com/support/pages/apar/PH34515.


PTF for APAR PH33099 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (February 2021)

PTF for APAR PH33099 fixes the following issues:

1) Q Apply ignores STOP commands in TERM=N case after Apply encountering an error
2) Q Apply does not terminate when running in synchronized mode (MCG) with TERM=Y even when update to IBMQREP_MCGSYNC table fails due to DB2 termination
3) Q Apply always calls SYSPROC.SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY stored procedure which prevents supporting replication of non-temporal source to temporal target.
4) unexpected results when using event based scheduling
5) Suspension of monitor for zos doesn't work correctly.
6) SQL Apply failed in ASNLOAD with SQLCODE -104

ASNCLP: updated from db2_v111m4fp6 s2102031900
Samples: not updated
Function Level: 1140.103

You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH33099.


PTF for APAR PH31335 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (December 2020)

PTF for APAR PH31335 fixes the following issues:

1) SQL Replication does not support target database in 'RREPL' mode
2) Q Capture stops when encountering dictionary error and LOGRD_ERROR_ACTION=E is specified.

ASNCLP: updated from db2_v111m4fp6 n2012091900
Samples: not updated
Function Level: 1140.103

You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH31335.


PTF for APAR PH29264 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (October 2020)

PTF for APAR PH29264 fixes the following issues:

1) Q Capture needs to support Db2 ALTER TABLESPACE MOVE TABLE
2) SQL Apply high CPU consumption in ASNAISO after migration to DB2 V12
3) warmstart proxyMode Q capture failed if remote Db is not available and ON_SOURCE_DB_UNAVAIL is R
4) Capture always checks the Db2 catalog to determine if the table is altered and needs to be REORG when activating a subscription.
5) inconsistent timestamp for Qrep EP
6) When Capture starts it might take couple of minutes to initialize and the CURRENT_LOG_TIME will display 1900-01-01-00.00.00.000000 (zero), which can not be fixed in engine. ASNMON generates alerts when it reads this value. What this customer wants is for ASNMON to realize this issue and not send the alerts until CURRENT_LOG_TIME goes to a non zero value.
7) Q Apply may fail to resolve duplicate -803 errors for non-condensed CCD target after Q Capture is restarted from older LSN point

ASNCLP: not updated
Samples: ASNCLPB
ASNCTLZD
ASNQ1140
ASNQCTLZ
ASNVSQL
Function Level: 1140.103

You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH29264.


PTF for APAR PH28162 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (August 2020)

PTF for APAR PH28162 fixes the following issues:

1) Apply receives sqlcode -551 on a Truncate operation when replicating data from z/OS to non z/OS target in a SQL Replication configuration.
2) When you create or alter a publication with delimited messages by using the ASNCLP command-line program in Event Publishing, the ASNCLP program incorrectly allows you to specify a BEFORE VALUES option of N (no before values are sent). Before values must be sent for delimited messages, so the only valid option for BEFORE VALUES is Y (yes).

ASNCLP: updated from db2_v111m4fp6 n2008201900
Samples: not updated
Function Level: 1140.103

You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH28162.


PTF for APAR PH25794 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (June 2020)

PTF for APAR PH25794 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) Capture is causing contention over DSNDB01.SPT01
4) Q Capture issued message ASN7181E incorrectly
5) The current_log_time in IBMQREP_CAPMON table is 1900-01-01-00.00.00.000000

ASNCLP: not updated
Samples: not updated
Function Level: 1140.103

You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH25794.


PTF for APAR PH23855 for IBM InfoSphere Data Replication for Db2 for z/OS v11.4.0 (Q and SQL Replication) is available (April 2020)

PTF for APAR PH23855 fixes the following issues:

1) Too many ASN0635I messages in the job log.
2) Replication tasks issued a SELECT from SYSIBM.SYSLEVELUPDATES table to check the DB2 level information. If the user did not have the right authority, the SQL statement returned SQLCODE -551. Subsequently the replication tasks also failed.
3) Dropping a source table for an active subscription caused erroneous behavior for Q Capture.
4) Q Capture displays ASN0725W plus diagnostic data and continues executing after its log reader detects out of order log records.

ASNCLP: updated from db2_v111m4fp6 s2004231900
Samples: updated ASNQ1140, ASNQCTLZ
Function Level: 1140.103

You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH23855.


PTF for APAR PH20050 for IBM InfoSphere Data Replication for DB2 for z/OS v11.4.0 (Q and SQL Replication) is available (February 2020)

PTF for APAR PH20050 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.
2) Q Capture delimited EP does not prefix negative decimal column values with a minus sign if the source table CCSID is 37 or 500 and the IBMQREP_SENDQUEUES MESSAGE_CODEPAGE is the same as the source table CCSID.
3) Q Capture delimited EP does not include the day for a TIMESTAMP WITH TIME ZONE column value if the day is December 31.
4) Q Capture running in proxy mode saves the SYSIBM.SYSTABLES schema in its version tables as version 0. Q Capture is unable to decode a Db2 V12 Function level 502 or higher SYSIBM.SYSTABLES log records using version 0 schema information.
5) SQL Apply should perform TRUNCATE of target table before fullrefresh if its DATA CAPTURE CHANGES attribute is not set

ASNCLP: updated from db2_v111m4fp6 n2002110100
Samples: updated ASNQCTLZ
Function Level: 1140.103

You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH20050.


PTF for APAR PH16629 for IBM InfoSphere Data Replication for DB2 for z/OS v11.4.0 (Q and SQL Replication) is available (November 2019)

PTF for APAR PH16629 fixes the following issues:

1) Information about the DB2 environment like z/OS V12 function level and data sharing is not recorded in replication log messages.
2) Q Apply gets sql error -311 when it restarts and reloads the sub with state='T' from IBMQREP_TARGETS
3) Q Capture will recognize a new signal that allows users to redefine the replication key.
4) Q apply reports sql error -199 when replicating add column DDL of special temporal columns
5) Q Apply Agent may not provide proper diagnostics when it reports unexpected non-SQL errors encountered when applying row changes to target. Without information on the exact Q Subscription, source row LSN or MQ MSGID of the problem row change, user cannot determine the cause of the error or steps to rectify it.
6) A Q Capture send queue has a counter that indicates the number of active subscriptions that write messages to the send queue.  The counter does not get incremented correctly if all subscriptions that use the send queue are inactive when Q Capture warmstarts.
7) Q Capture does not rebuild the publication search condition after it detects that a publication source table was altered to drop a column.
8) Q Capture builds delimited messages in CCSID 1208 if the source table CCSID is EBCDIC and uses character conversion services to convert source table data from CCSID 1208 to the EBCDIC CCSID specified in the IBMQREP_SENDQUEUES MESSAGE_CODEPAGE.
ASNCLP: updated from db2_v105fp11 s191020
Samples: updated ASNCTLZD, ASNQ1140
Function Level: 1140.103

You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH16629.


PTF for APAR PH13496 for IBM InfoSphere Data Replication for DB2 for z/OS v11.4.0 (Q and SQL Replication) is available (August 2019)

PTF for APAR PH13496 fixes the following issues:

1) 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.
2) The user cannot identify the table row being reworked.
3) SQL / Rep remote bind job modified to include ASNMONITOR package
4) Capture always checks the Db2 catalog (prior to Db2 v12) to determine if the table is altered and needs to be REORG when activating a subscription.
5) The results are unpredictable when starting Capture using the timestamp option with a non data-sharing system.
ASNCLP: updated from db2_v105fp11 s190723
Samples: updated ASNBNDDR
Function Level: 1140.100

You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH13496.


PTF for APAR PH08369 for IBM InfoSphere Data Replication for DB2 for z/OS v11.4.0 (Q and SQL Replication) is available (May 2019)

PTF for APAR PH08369 fixes the following issues:

1) Q Capture REINIT of an active subscription issues ASN7341W and does not send a schema message to Q Apply.
2) Q Capture issues ASN7138W each time it initializes a delimited subscription that has a IBMQREP_SENDQUEUES message_codepage that is not 1208.
3) Q Apply ASN7224I message displays an incorrect commit timestamp because Q Capture sent Q Apply an incorrect commit timestamp in a notification message.
4) Q Capture made an MQINQ call to return the number of messages on a queue and the call failed.
5) Q Capture prune positioned DELETE statements are invalidated.
6) 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.
7) 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.
8) The user cannot identify the UTILID used in ASNLOAD for a specific SQL Apply instance.
9) 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: updated ASNQ1140, ASNQCTLZ, ASNV1140, ASNVMON
Function Level: 1140.100

You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH08369.


PTF for APAR PH06478 for IBM InfoSphere Data Replication for DB2 for z/OS v11.4.0 (Q and SQL Replication) is available (January 2019)

PTF for APAR PH06478 fixes the following issues:

1) Capture gets SQLCODE -180 when it inserts timestamp values into the CAPMON CURRENT_LOG_TIME and LAST_EOL_TIME columns if the Db2 subsystem LRSN Delta is non-zero.
2) SQL Capture hangs reading 974 Meg transaction.
3) 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.
4) Capture cannot find the version of a table in the IBMQREP_TABVERSION table.
ASNCLP: not updated
Samples: not updated
Function Level: 1140.100

You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH06478.


PTF for APAR PH02537 for IBM InfoSphere Data Replication for DB2 for z/OS v11.4.0 (Q and SQL Replication) is available (November 2018)

PTF for APAR PH02537 fixes the following issues:

1) Q Capture hangs in GETMAIN after it overlays the first byte of a heap free element.
2) 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.
3) 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.
4) The Q Capture XML format message cmitTime attribute value does not display microseconds if the value for microseconds is zero.
5) Q Capture XML format messages display invalid FLOAT data type values if the FLOAT data type value is zero.
6) 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'.
ASNCLP: not updated
Samples: updated ASNQ1140, ASNQCTLZ, ASNV1140
Function Level: 1140.100

You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PH02537.


PTF for APAR PI99238 for IBM InfoSphere Data Replication for DB2 for z/OS v11.4.0 (Q and SQL Replication) is available (September 2018)

PTF for APAR PI99238 fixes the following issues:

1) Q Capture running in proxy mode using proxy Db2 12 displays Db2 reason code X'00E60870'.
2) 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).
3) 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.
4) Capture cannot advance its restart LSN while it processes a global transaction that does not commit or rollback.
5) 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'
6) The Q Apply load function calls the Db2 SYSPROC.DSNUTILS stored procedure to run Db2 utilities (LOAD, CHECK DATA, REPAIR).
7) 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.
8) 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.
9) 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_v105fp11 n180819
Samples: updated ASNQ1140, ASNQCTLZ, ASNV1140
Function Level: 1140.100

PTF for APAR PI99238 also contains new function.  Here are links to the "Function level 1400.100 (activation enabled by APAR PI99238)" documentation.

https://www.ibm.com/support/knowledgecenter/SSTRGZ_11.4.0/com.ibm.swg.im.iis.repl.qmig.doc/topics/iiyrqmigcdovu.dita
https://www.ibm.com/support/knowledgecenter/SSTRGZ_11.4.0/com.ibm.swg.im.iis.repl.qmig.doc/topics/iiyrqmigacvitate.dita
https://www.ibm.com/support/knowledgecenter/SSTRGZ_11.4.0/com.ibm.swg.im.iis.db.repl.utilities.doc/topics/iiyrqmigasncatm.dita
https://www.ibm.com/support/knowledgecenter/SSTRGZ_11.4.0/com.ibm.swg.im.iis.prod.repl.rel.info.doc/topics/iiyprwnfunclevels.dita
https://www.ibm.com/support/knowledgecenter/SSTRGZ_11.4.0/com.ibm.swg.im.iis.prod.repl.rel.info.doc/topics/iiyprwn11.4-pi99238.dita

You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PI99238.


PTF for APAR PI97455 for IBM InfoSphere Data Replication for DB2 for z/OS v11.4.0 (Q and SQL Replication) is available (June 2018)

PTF for APAR PI97455 fixes the following issues:

1) Q Apply using subscription by partitions may not detect or report target conflicts when rows are missing from target and an update on source causes that row to move across partitions.  This may result in target data divergence without any EXCEPTIONS reported or rows staged in DELAYIN 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=swg1PI97455.


PTF for APAR PI94529 for IBM InfoSphere Data Replication for DB2 for z/OS v11.4.0 (Q and SQL Replication) is available (May 2018)

PTF for APAR PI94529 fixes the following issues:

1) Customer asked to provide both the LSN and the timestamp of the oldest transaction actually applied.
2) 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.
3) Q Apply may experience high CPU usage and performance degradation when processing FUNC_LEVEL_MSG messages sent by Q Capture during program restart or when Send Queues are stopped and restarted.
4) Q Capture abends with S0C4 at PostFixElement::compareString() + 0000073C after it processes a STARTQ or REINIT command.
5) SQL Apply / ASNLOAD failed with SORTKEYS error
6) ASNTDIFF error when code page of the primary key is 1208
7) IBMQREP_CAPMON NUM_LOGREAD_ERRORS column is not initialized.
8) 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 spilled data set and the row is not the first row of the transaction.
9) Q Capture activates subscriptions that are defined with change conditions only if the database code page HEX value for the '$' character is x'5B'.
ASNCLP: updated from db2_v105fp11 n180421
Samples: ASNCATM, ASNQ1021, ASNQ1140, ASNQCTLZ, ASNV1140

You can get more information and download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PI94529.


PTF for APAR PI90304 for IBM InfoSphere Data Replication for DB2 for z/OS V11.4.0 (Q and SQL Replication) is available (February 2018)

PTF for APAR PI90304 fixes the following issues:

1) IBMSNAP_ALERTS and IBMSNAP_CONDITIONS tables from char(18) to varchar(20) in defect 1066771. But monitor still writes columns as char.
2) Capture attached to DB2 V12.1.501 CM displays ASN0589I messages when it decodes DB2 V11 NFM SYSIBM.SYSCOLUMNS log records.
ASNCLP: not updated
Samples: ASNCATM, ASNQ1140, ASNQBNDL, ASNQCTLZ, ASNV1140

You can download the fix at http://www-01.ibm.com/support/docview.wss?uid=swg1PI90304.


[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTRGZ","label":"InfoSphere Data Replication"},"Component":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF051","label":"Linux on IBM Z Systems"},{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 June 2022

UID

ibm11099455