JR35056: REPLICATION ADMIN FIXES FOR DB2 LUW V9.1 FP9

DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

APAR status

• Closed as program error.

Error description

• V91FP9 Admin Fixes
  

Local fix

• V91 FP9 Admin Fixes
  

Problem summary

• Defect: wsdbu00612234
  User Affected: Q Replication users
  Problem Description: The ASNCLP command "validate WSMQ
  ENVIRONMENT FOR CAPTURE SCHEMA;" failed
  Problem Summary: Both the ASNCLP and Replication Center fail
  running the validation
  Problem Conclusion: Validate of MQ queues on the capture control
  servers now occur properly.
  
  Defect: wsdbu00614467
  User Affected: SQL Replication users
  Problem Description: Unable to create capture control tables in
  oracle federation database using Replication Center
  Problem Summary: User tried to create capture control tables in
  federated Oracle and experiences "SQL0204N  "NET8 object:
  Unknown" is an undefined name."
  Problem Conclusion: User can now create capture control tables
  in federated Oracle.
  
  Defect: wsdbu00550745
  User Affected: SQL Replication users for RC and ASNCLP
  Problem Description: The prune set row was being dropped at the
  time of dropping a member and the query that was used to check
  if there are other members in the set is causing an error.
  Problem Summary: Checking for members in the set and dropping
  the row from pruneset table is causing SQL error.
  Problem Conclusion: Moved the delete pruneset row to drop set
  time and so there is no need to check if there are any more
  members in the set as at drop set time all members are also
  dropped.
  
  Defect: wsdbu00568963
  User Affected: Q Replication users using ASNCLP
  Problem Description: System.out.println statements are showing
  up while creating Q Apply control tables.
  Problem Summary: Println statements were left out in the code.
  Problem Conclusion: Removed the println statements.
  
  Defect: wsdbu00611464
  User Affected: Q Replication users using teradata targets.
  Problem Description: The problem surfaces after switching to the
  JCC driver.  JCC driver does not accept line terminator \n for
  sql statements issued against teradata targets in set passthru
  mode.  The problem is only specific to teradata targets.
  Problem Summary: Problem is specific to teradata targets where
  an SQL error is issued while processing sql statements with line
  terminator in set passthru mode.
  Problem Conclusion: Removed all the line terminators before
  processing the sql statements and it resolved the problem.
  
  Defect: wsdbu00613631
  User Affected: Q Replication users that have dbclob data types.
  Problem Description: The stored procedure that is used to check
  if the database supports dbclob datatypes does not work properly
  and due to this dbclob data type is not supported for the
  database although it has to be suppored.
  Problem Summary: dbclob data type is not enabled for the
  database although it should be.
  Problem Conclusion: Changed the check to just query the table
  sysibm.sysdata types to check if the database supports dbclob
  data type instead of relying on the stored procedure.
  
  Defect: wsdbu00623932
  User Affected: SQL Replication users using federated sources
  Problem Description: SQL script cannot be executed properly in
  RC as the commit statement was removed as part of change for the
  JCC drive.
  Problem Summary: Encountering SQL error while running create
  control tables for federated sources.
  Problem Conclusion: Explicitly added a commit statement for the
  SQL executed in RC.
  
  Defect: wsdbu00614467
  User Affected: SQL Replication users using federated sources
  Problem Description: At the time of creating control tables, the
  query to check for the existence of a table is failing as the
  SQLCODE that is used to check if the table exists is not the
  same for JCC and legacy drivers.
  Problem Summary: Encountering SQL error while checking is a
  table exists while creating control tables for federated
  sources.
  Problem Conclusion: Added the SQLCODE that is checked by the
  legacy driver also as an acceptable code..
  
  Defect: wsdbu00352339
  User Affected: Q Replication users using bidi and p2p
  subscriptions
  Problem Description: The logic to check for the number of
  indexes on z/OS tables in not correct if the table has a primary
  key.  APIs count the unique index created for the primary key
  also as an index and this is resulting in an error with index
  mismatches while creating bidi and p2p subscriptions between
  z/OS and LUW.
  Problem Summary: Index mismatches error while creating bidi and
  p2p subscriptions between z/OS and LUW.
  Problem Conclusion: Corrected the logic to get the number of
  indexes on z/OS and not count the primary key index.
  
  Defect: wsdbu00242533
  User Affected: SQL Replication users using federated sources,
  Problem Description: COMMIT statement is explicitly issued while
  creating control tables for federated sources and this is not
  acceptable when JCC driver is used.
  Problem Summary: Explicit commit statement should be removed
  from the scripts to create control tables for federated sources
  Problem Conclusion: Removed the COMMIT statements and a commit
  of the sql statements was done on the connection itself rather
  than a static commit..
  

Problem conclusion

• Fixed all these defects
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  JR35895 IC67081 IC67085 IC67445

Fix information

• Fixed component name

  WS Q-REPLIC LUW

• Fixed component ID

  5724N9801

Applicable component levels

• R910 PSY

     UP