JR61446: IIDR DB2LUW DISPLAY CORRECT PRIMARY INDEX INFORMATION WITH CHCCLP QUERIES

APAR status

• Closed as program error.

Error description

• If primary key is defined implicitly with the table
  creation,primary index is appearing as "NO" when we query with
  CHCCLP. Instead if primary key constraint is created as user
  defined the below logic may work.
  
  From DB2
  db2 => create table CDCEDM.BENCHECK1 (CUSTCD
  varchar(10),BENNAME varchar(10),BENACNO integer not
  null,BENBANK integer, primary key(BENACNO))
  DB20000I  The SQL command completed successfully.
  db2 => commit
  DB20000I  The SQL command completed successfully.
  
  ------------
  From CHCCLP
  Repl > connect server hostname 10.20.235.165 port 10111
  username <user> password <pwd>;
  Repl > connect datastore name CNPKTEST;
  Repl > list table indexes name CNPKTEST schema CDCEDM table
  BENCHECK1;
  
  Indexes for table CDCEDM.BENCHECK1.
  INDEX NAME                  PRIMARY INDEX    UNIQUE INDEX
  --------------------------- ---------------- ----------------
  SYSIBM.SQL190702110947870   No               Yes
  

Local fix

• No Local Fix.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * This issue affects you if you use CHCCLP to work with        *
  * subscriptions and table mappings.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * If primary key is defined implicitly with the table          *
  * creation, the primary index is appearing as ?NO? when you    *
  * query with CHCCLP.                                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IDR 11.4.0.2-5503 or newer for Db2.               *
  ****************************************************************
  

Problem conclusion

• Upgrading to IDR 11.4.0.2-5503 or newer for Db2 resolves the
  issue.
  

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:

Fix information

• Fixed component name

  IS CDC DB2 LUW

• Fixed component ID

  5725E30DL

Applicable component levels