IBM Support

Q Replication and SQL Replication APARs in DB2 for Linux, UNIX, and Windows V9.7 Fix Pack 9

Preventive Service Planning


Abstract

The following fixes for Q Replication and SQL Replication are included in DB2 for Linux, UNIX, and Windows V9.7 Fix Pack 9.

Content

JR48860: Q & SQL REPLICATION ADMIN FIXES FOR DB2 LUW V97FP9

  • JR47804: RC GENERATES CREATE INDEX STATEMENT ON AN EXISTING FEDERATED TARGET TABLE WHEN THE SAID INDEX ALREADY EXISTS
  • JR47869: SQL REPLICATION: TIMESTAMP SCALE OF ZERO NOT RESPECTED IN THE CD TABLE DDL
  • JR48182: CHANGING SPILLQ IN THE QSUB PROPERTIES RESETS THE EARLIER COLUMN SELECTION AND MAPPING IN THE CREATE QSUB WIZARD FOR FED TARGETS
  • JR48367: CREATE QSUB FAILS WITH ASN2100E IF THE SOURCE TABLE HAS A DECIMAL COLUMN WITH DEFAULT VALUES
  • JR48617: QREP V9.7 MIGRATION SCRIPTS INCORRECTLY CHANGE THE LOB_TOO_BIG_ACTION AND XML_TOO_BIG_ACTION COLUMNS TO NULLABLE
  • JR48738: TOLERATE ARCH_LEVEL '1001' AND COMPATIBILITY '0907'
  • JR48739: REGISTER PANEL HAS A NULLPOINTEREXCEPTION WHEN CCD_OWNER IS AN EMPTY STRING INSTEAD OF NULL
  • JR48740: UNI Z/OS => LUW COLUMN PROBLEM WHEN DEFINED WITH GENERATED BY DEFAULT FOR EACH ROW ON UPDATE AS ROW CHANGE TIMESTAMP
  • JR48741: WRONG ASN.IBMSNAP_APPPARMS SLEEP VALUE WHEN CHANGING THE SAVED PARMS
  • JR48742: Q APPLY CONTROL IBMQREP_TRG_COLS TABLE, COLUMN MAPPING_TYPE SHOULD BE CREATED WITH DEFAULT 'R'
  • JR48866: REPLICATION CENTER DISPLAYS IBMQREP_CAPPARMS AND IBMQREP_APPLYPARMS VALUES INCORRECTLY FOR ARCH_LEVEL 100Z

JR48861: Q & SQL REPLICATION ENGINE FIXES FOR DB2 LUW V97FP9
  • JR45710: 0 VALUES FOR LATENCY COUNTERS ARE REPORTED IN IBMQREP_APPLYMON EVEN WHEN ROWS_APPLIED > 0
  • JR45968: Q CAPTURE FOR ORACLE DOES NOT STOP ON DATABASE SHUTDOWN IMMEDIATE
  • JR46978: QAPPLY GETS SIGSEGV FOR SUBSCRIPTIONS WITH SEPARATE LOBS (LOB_SEND_OPTION=S) REQUIRING DATA CONVERSION
  • JR47462: ASNTRC ON SUN CORE DUMPS WITH A BUS ERROR TRYING TO FORMAT A TRACE FILE
  • JR47783: ASN0589I MESSAGE IS CRYPTIC
  • JR48030: THE LOGRDBUFSZ PARAMETER IS NOT BEING RECOGNIZED BY CAPTURE. LOGREUSE IS BEING TRUNCATED INSTEAD.
  • JR48137: QAPPLY DUMPS DUE TO THE PROCESSING OF PEER-TO-PEER DELETE CONFLICTS
  • JR48618: CAPTURE COMES DOWN WITHOUT AN ERROR MESSAGE WHEN USER SPECIFIES AN INCORRECT CAPTURE_SCHEMA
  • JR48619: CAPTURE HITS A SQL1024N ERROR ON SHUTDOWN
  • JR48622: ADD ASNPWD PASSWORD FILE MIGRATION FUNCTION THAT WILL READ A DES ENCRYPTED PASSWORD FILE AND RE-ENCRYPT THAT PASSWORD WITH AES
  • JR48642: SQL APPLY DOES NOT DETECT CONFLICTS CORRECTLY IN UPDATE ANYWHERE SETUP WHEN ONE SIDE OF THE SERVERS IS DB2 ISERIES
  • JR48643: SQL APPLY REPORTS SQLCODE -204 FROM DB2 ISERIES SOURCE SERVER WHEN APPLY IS STARTED WITH A NON-ISERIES CONTROL SERVER
  • JR48644: Q APPLY CPU CONSUMPTION INCREASES UNEXPECTEDLY WHEN PARAMETER APPLYDELAY IS ON
  • JR48645: ASNLOAD FAILS WITH ASN1053 RC=110 WHEN CROSS LOADER ATTEMPTS TO LOAD FROM A NICKNAME SOURCE
  • JR48686: Q APPLY ON ZLINUX MAY NOT CORRECTLY EXTRACT BIGINT COLUMN DATA VALUES WHEN ENDIAN CONVERSION IS REQUIRED
  • JR48687: ADDITIONS TO Q APPLY SHOULD BE ABLE TO GRACEFULLY COME DOWN IF FEDERATED TARGET GETS CONNECTION ERROR
  • JR48688: ASN7512E RC 5 OBSERVED WHEN ACTIVATING A SUBSCRIPTION HAVING EXPRESSION COLUMNS
  • JR48695: Q APPLY DOES NOT RETRY FOR TRIGGER FAILURE DUE TO DEADLOCKS
  • JR48867: QAPPLY USING MQ CLIENT ON WIN64 IS UNABLE TO START OR USE ASNQMFMT
  • JR48869: SQL APPLY FAILS WITH ASN1053E DURING EXECUTION OF ASNLOAD

[{"Product":{"code":"SSTRGZ","label":"InfoSphere Data Replication"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Misc","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"},{"code":"PF027","label":"Solaris"}],"Version":"9.7.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21660333