IBM Support

Q Replication and SQL Replication APARs in DB2 for Linux, UNIX, and Windows V10.1 Fix Pack 4

Preventive Service Planning


Abstract

The following fixes for Q Replication and SQL Replication are included in DB2 for Linux, UNIX, and Windows V10.1 Fix Pack 4.

Content

JR50089: Q and SQL REPLICATION ADMIN FIXES FOR DB2 V10.1 FP4

  • JR48126 : "SELECT SOURCE TABLES" DIALOG, WHEN CRITERIA CHANGE, THE DEFAULT BUTTON SHOULD BE "RETRIEVE"
  • JR48697 : RC PUBLICATION WIZARD SHOULD ALLOW COLUMN SUBSETTING
  • JR48784 : FOR UNI_REMOTE.PDF, BE ABLE TO TURN OFF AUTO MQ OBJECT NAME GENERATION
  • JR48910 : IBMQREP_SENDQUEUES.HEARTBEAT_INTERVAL UNITS CHANGE FROM SECONDS TO MILLISECONDS SHOULD BE REFECTED IN QUEUE MAP PROPERTIES
  • JR48912 : ASNCLP PROGRAM DOES NOT SUBSCRIBE HISTORY TABLE IN A BIDIRECTIONAL CONFIGURATION ON Z/OS
  • JR48986 : CREATING PEER-TO-PEER Q SUBSCRIPTION FROM REPLICATION CENTER FAILS WITH SQL0423N IF THE SOURCE TABLE HAS IDENTITY COLUMN
  • JR49027 : ASNCLP PROGRAM SETS CHANGED_COLS_ONLY TO N FOR CONFLICT ACTIONS D, S OR Q
  • JR49080 : ASNCLP PROGRAM AND REPLICATION CENTER UNABLE TO REGISTER TABLES WITH MORE THAN 500 COLUMNS
  • JR49081 : REPLICATION CENTER INCORRECTLY DISPLAYS SOME Q SUBSCRIPTION PROPERTIES
  • JR49121 : REQUIRED COLUMNS NOT ADDED WHEN MIGRATING FROM V9.5 TO V10.1 FOR FEDERATED TARGETS
  • JR49410 : SQL REPLICATION V10.1 MIGRATION SCRIPT DOES NOT WORK FOR TYPE 9 CCD TARGETS
  • JR49411 : ASNCLP PROGRAM CREATES INCORRECT REPLICATION KEY FOR NONCONDENSED CCD TARGETS WITH NO PRIMARY KEY
  • JR49412 : REPLICATION CENTER ERROR MESSAGES NOT VISIBLE
  • JR49501 : REPLICATION CENTER GENERATES INCORRECT SCRIPT FOR SOME BIDIRECTIONAL Q SUBSCRIPTIONS
  • JR49571 : REPLICATION CENTER PREVENTS ADDING MULTIPLE REMOTE SERVERS WITH SAME FEDERATED SERVER ALIAS
  • JR49716 : SQL REPLICATION: TIMESTAMP SCALE OF ZERO NOT RESPECTED IN THE CD TABLE DDL
  • JR49719 : CHANGING SPILLQ IN THE QSUB PROPERTIES RESETS THE EARLIER COLUMN SELECTION AND MAPPING IN THE CREATE QSUB WIZARD FOR FED TARGETS
  • JR49732 : CREATE QSUB FAILS WITH ASN2100E IF THE SOURCE TABLE HAS A DECIMAL COLUMN WITH DEFAULT VALUES
  • JR49760 : REPLICATION TOOLS COMPARING INCORRECTLY
  • JR50393: REPLICATION TOOLS UNABLE TO MAP CHARACTER LITERALS IN EXPRESSIONS WITH VARCHAR2 COLUMNS AND NATIVE ORACLE TARGETS


JR50088: Q and SQL REPLICATION ENGINE FIXES FOR DB2 V10.1 FP4
  • JR47639 : ASNLOAD TERMINATES ABNORMALLY WHEN THE SQL STATEMENT FOR EXPORT/LOAD IS LONGER THAN 32K
  • JR47695 : RI ERROR WHEN QAPPLY ATTEMPTS TO PUT BACK THE RI SINCE THE CORRESPONDING PARENT IS NOT THERE IN THE TARGET
  • JR47716 : SQL APPLY STOPS AFTER HITTING -530 ERROR WHEN COMMIT_COUNT IS NOT NULL
  • JR47910 : CREATE TABLE DDL DID NOT REPLICATE TO ALL QUEUE MAPS
  • JR48097 : THE ASNCCMD STATUS COMMAND DOES NOT SHOW THE STATUS OF THE TRANSACTION READER THREAD
  • JR48181 : Q APPLY INCORRECTLY INTERPRETS 'REASON CODE' FIELD IN SCHEMA MSG FROM OLDER COMPATIBILITY MESSAGES
  • JR48247 : Q CAPTURE FOR ORACLE DOES NOT STOP ON DATABASE SHUTDOWN IMMEDIATE
  • JR48384 : PUBLISHED TRANSACTION FOR GLOBAL TRANSACTION IN DPF ENVIRONMENT SHOWS INVALID OR UNINITIALIZED COMMIT TIMESTAMPS
  • JR48736 : ORACLE CAPTURE INCORRECT DECODING OF CHAR COLUMNS WITH CHAR SEMANTICS
  • JR48737 : ORACLE CAPTURE EXPERIENCES MEMORY CORRUPTION WHEN READING ALL_INDEXES
  • JR49059 : INCORRECT INITIALIZATION OF DECIMAL FLOATING POINT ENVIRONMENT MAY CAUSE DB2 CRASH
  • JR49060 : SQL0461 IS ISSUED WHEN RUNNING Q CAPTURE REMOTELY TO A DB2 V9.5 DATABASE
  • JR49079 : CAPTURE PROGRAMS DO NOT DELETE SPILL FILES AFTER ENCOUNTERING ERRORS WHILE WRITING TO THE FILES
  • JR49208 : ADD ASNPWD PASSWORD FILE MIGRATION FUNCTION THAT WILL READ A DES ENCRYPTED PASSWORD FILE AND RE-ENCRYPT THAT PASSWORD WITH AES
  • JR49429 : BIDIRECTIONAL Q SUBSCRIPTIONS GENERATED AFTER DDL OPERATION FAIL TO ACTIVATE
  • JR49538 : Q SUBSCRIPTION MIGHT NOT START BECAUSE OF SPILL QUEUE ISSUE DURING LOAD
  • JR49741 : ASNTRC ON SUN CORE DUMPS WITH A BUS ERROR TRYING TO FORMAT A TRACE FILE
  • JR49757 : QAPPLY DUMPS DUE TO THE PROCESSING OF PEER-TO-PEER DELETE CONFLICTS
  • JR49937 : CUSTOMERS WHO MIGRATE TO Q REPLICATION IN DB2 V10.1 FP3 MIGHT ENCOUNTER SQL -206 ERROR FOR IBMQREP_EXCEPTIONS
  • JR49939 : Q APPLY GENERATES INCORRECT IBMSNAP_LOGMARKER VALUE IN CCD TARGET TABLES WHEN LOGMARKERTZ=LOCAL IS SET
  • JR50420: NATIVE ORACLE APPLY FAILS WHEN PRUNING OR DURING SPILL CLEANUP
  • JR51786: VERY SMALL CHANCE OF OUT-OF-ORDER TRANSACTIONS IN Q REPLICATION (HIPER)

[{"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":"10.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21672721