PM74611: UPDATEINSTALLER FOR AD 7.1 FP2 IFIX11 NOT CREATE LEADER TABLE. NO ERR IN UPDATE LOG. UPDATE LOG NOT SEEM TO CREATE LEADER TABLE

7.1.0.3-TIV-ITCAMAD-IF0004: ITCAM for Application Diagnostics V7.1 FP3 IF4
7.1.0.3-TIV-ITCAMAD-IF0005: ITCAM for Application Diagnostics V7.1 FP3 IF5
7.1.0.3-TIV-ITCAMAD-IF0004: ITCAM for Application Diagnostics V7.1 FP3 IF6

APAR status

• Closed as program error.

Error description

• Problem Description:
  In the update logs, we found the following:
  
   Update installer version 7.1.0.2.11, build 20120316165631
   (Sep 26, 2012 4:22:12 PM), update,  An update file found
   7.1.0.2.11, 7.1.0.2-TIV-ITCAMAD_MS-IF0011.update
   (Sep 26, 2012 4:22:12 PM), update,  updates list: [7.1.0.1,
   7.1.0.1.1, 7.1.0.1.2, 7.1.0.1.3, 7.1.0.1.4, 7.1.0.2,
   7.1.0.2.11]
  
   As you can see above all the updates between 7.1.0.2 and
   7.1.0.2.11 are skipped. LEADER table update is in the 7.1.0.2.7
   according to update.xml
   This is clearly a problem in the update installer as it is not
   cumulative of all the previous ifixes for the current level.
  
   For the current ifix upgrade after the major fixpack, the
   update installer skips all the ifixes in between and jumps
   directly to the last one. For example, if you are using
   7.1.0.2.3 update installer it will skip all the ifixs from the
   last major fixpack (7.1.0.2) to the current ifix (7.1.0.2.3).
   i.e 7.1.0.2.1 and 7.1.0.2.2 is skipped as shows in Case A.
  
   In Case B, as you can see the last major fixpack was 7.1.0.3
   and update installer was 7.1.0.3. so it skipped everything in
   between.
  
  ----------------------------------------------------------------
  Case A:
  (Oct 3, 2012 6:16:18 PM), update,  An update file found
  7.1.0.2.3, 7.1.0.2-TIV-ITCAMAD_MS-IF0003.update
  (Oct 3, 2012 6:16:18 PM), update,  updates list: [7.1.0.1,
  7.1.0.1.1, 7.1.0.1.2, 7.1.0.1.3, 7.1.0.1.4, 7.1.0.2, 7.1.0.2.3]
  <- Skipped the 7.1.0.2.1 and 7.1.0.2.2
  
  Case B:
  (Oct 3, 2012 6:19:43 PM), update,  An update file found
  7.1.0.3.3, 7.1.0.3-TIV-ITCAMAD_MS-IF0003.update
  (Oct 3, 2012 6:19:43 PM), update,  updates list: [7.1.0.1,
  7.1.0.1.1, 7.1.0.1.2, 7.1.0.1.3, 7.1.0.1.4, 7.1.0.2, 7.1.0.2.1,
  7.1.0.2.2, 7.1.0.2.3, 7.1.0.2.5, 7.1.0.2.6, 7.1.0.2.7, 7.1.0.3,
  7.1.0.3.3] <- Skipped the 7.1.0.3.1, 7.1.0.3.2
  However, if you notice, it did not skip the updates in blue that
  was skipped in Case A)
  ----------------------------------------------------------------
  Case C:
  (Sep 26, 2012 4:34:36 PM), update,  An update file found
  7.1.0.2.7, 7.1.0.2-TIV-ITCAMAD_MS-IF0007.update
  (Sep 26, 2012 4:34:36 PM), update,  updates list: [7.1.0.1,
  7.1.0.1.1, 7.1.0.1.2, 7.1.0.1.3, 7.1.0.1.4, 7.1.0.2, 7.1.0.2.7]
  <- Skipped the  7.1.0.2.1, 7.1.0.2.2, 7.1.0.2.3, 7.1.0.2.5,
  7.1.0.2.6
  
  Case D:
  (Sep 26, 2012 4:27:19 PM), update,  An update file found
  7.1.0.3, 7.1.0-TIV-ITCAMAD_MS-FP0003.update
  (Sep 26, 2012 4:27:19 PM), update,  updates list: [7.1.0.1,
  7.1.0.1.1, 7.1.0.1.2, 7.1.0.1.3, 7.1.0.1.4, 7.1.0.2, 7.1.0.2.1,
  7.1.0.2.2, 7.1.0.2.3, 7.1.0.2.5, 7.1.0.2.6, 7.1.0.2.7, 7.1.0.3]
  <- This was FP3 so there was no ifix. But as you can see it did
  not skipped the updates in blue like it did in Case C:
  ----------------------------------------------------------------
  Approvals:
            L3 - KP
  

Local fix

• Local Fix/Workaround:
  
  Create a LEADER table manually, then restart Managing Server and
  VE WAS server.
  
  Oracle:
  create table LEADER( KERNEL_HOST varchar(100) not
  null,KERNEL_PORT number not null,DATE_CREATED date not null,
  DATE_UPDATED date not null)
  
  DB2:
  create table LEADER(KERNEL_HOST varchar(100) not
  null,KERNEL_PORT integer not null,DATE_CREATED timestamp not
  null, DATE_UPDATED timestamp not null)
  

Problem summary

• USERS AFFECTED: Customers who has applied ITCAM verison 7102
  Ifix10 and 7102 Ifix11
  
  PROBLEM DESCRIPTION: LEADER table in the octigate schema is not
  created and lots of exceptions are seen in the kernel logs
  
  RECOMMENDATION: Create the LEADER table manually
  
  PROBLEM CONCLUSION: Update installer code was only applying
  updates from the fixpack and before. But for the current fixpack
  it was skipping all the interim fixes and was applying only the
  last one. Fixed the code in the update installer to check for
  all the interim fix level until the recent ifix.
  
  The fix for this APAR is included in 7.1.0.3 Ifix4
  

Problem conclusion

• Update installer code was only applying
  updates from the fixpack and before. But for the current fixpack
  it was skipping all the interim fixes and was applying only the
  last one. Fixed the code in the update installer to check for
  all the interim fix level until the recent ifix.
  
  The fix for this APAR is included in 7.1.0.3 Ifix4
  

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

  TCAM AD MAN SER

• Fixed component ID

  5724Y92MS

Applicable component levels

• R710 PSN

     UP