IZ99464: DURING DB2 HADR FAILOVER WITH TN 5.6, FIELDS THAT ARE OF STATUS "NOT LOGGED" ARE NOT REPLICATED

APAR status

• Closed as suggestion for future release.

Error description

• The database schema for leap includes fields of
  type BLOB that specify 'NOT LOGGED'. Fields that
  are NOT LOGGED are not replicated during HADR
  failover. Therefore the schema must not include
  that specification of HADR is to be used.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• The $NCHOME/etc/precisiontn/sql/db2/leap_schema.sql script
  (which is used to create the NCIM database) sets the 'NOT
  LOGGED' attribute for all BLOB columns for the following tables:
  
  select substr(tabname,1,24) TABNAME,substr(colname,1,10)
  COLUMN,logged from SYSCAT.COLUMNS where logged='N'
  
  TABNAME                  COLUMN     LOGGED
  ------------------------ ---------- ------
  SCHEDULE                 ARG        N
  ROLE                     CUSTOMDATA N
  USERENTRY                CUSTOMDATA N
  NETWORKELEMENTDETAILS    DEFASSOCS  N
  NETWORKELEMENTDETAILS    CUSTOMDATA N
  ASSOCIATIONDETAILS       CUSTOMDATA N
  ALARM                    SOURCE     N
  ALARM                    ADDITIONAL N
  ALARM                    CUSTOMDATA N
  LOGGER                   WRITEFILTE N
  TOPOGROUP                CUSTOMDATA N
  TOPOTEXTANNOTATION       CUSTOMDATA N
  TOPOGROUPMEMBER          CUSTOMDATA N
  RACK                     CUSTOMDATA N
  SHELF                    CUSTOMDATA N
  CARD                     CUSTOMDATA N
  PORT                     CUSTOMDATA N
  PHYSICALTP               CUSTOMDATA N
  CONNECTIONTP             CUSTOMDATA N
  PROFILE                  CUSTOMDATA N
  PROFILETEMPLATE          CUSTOMDATA N
  PROTECTIONGROUP          CUSTOMDATA N
  TOPOLOGICALCONNECTION    CUSTOMDATA N
  CROSSCONNECT             CUSTOMDATA N
  SUBNETWORKCONNECTION     CUSTOMDATA N
  PERFSCHEDULE             CUSTOMDATA N
  OWNER                    CUSTOMDATA N
  
  
  The NOT LOGGED parameter prevents the BLOB columns from being
  replicated during a HADR failover. After the failover, the BLOB
  columns will contain a null value instead of the original
  correct value. This causes the 'Default Association cannot be
  null' error that is seen when PTN recovers from the failover and
  tries to starts up unsuccessfully.
  
  In order to support IBM DB2 HADR failover, the NCIM database
  tables listed above must be created with the BLOB columns set to
  'LOGGED'. Below is an example,
  
  Original:
  CREATE TABLE NETWORKELEMENTDETAILS(
      id VARCHAR(36) NOT NULL PRIMARY KEY,
      entityId INTEGER,
      domainMgrId INTEGER NOT NULL,
      name VARCHAR(256) NOT NULL  UNIQUE,
      neTypeName VARCHAR(128),
      owner VARCHAR(36),
      reqQSize INTEGER NOT NULL,
      reqTimeout INTEGER NOT NULL,
      flags INTEGER NOT NULL,
      defAssocs BLOB NOT LOGGED NOT NULL,
      tid VARCHAR(256) NOT NULL,
      customData BLOB NOT LOGGED NOT NULL
  );
  
  
  Corrected:
  CREATE TABLE NETWORKELEMENTDETAILS(
      id VARCHAR(36) NOT NULL PRIMARY KEY,
      entityId INTEGER,
      domainMgrId INTEGER NOT NULL,
      name VARCHAR(256) NOT NULL  UNIQUE,
      neTypeName VARCHAR(128),
      owner VARCHAR(36),
      reqQSize INTEGER NOT NULL,
      reqTimeout INTEGER NOT NULL,
      flags INTEGER NOT NULL,
      defAssocs BLOB LOGGED NOT NULL,
      tid VARCHAR(256) NOT NULL,
      customData BLOB LOGGED NOT NULL
  );
  
  
  The changes must be done for all the tables listed above.
  

APAR Information

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

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

Fix information

Applicable component levels