LI73595: SUPPORT OF NONCANONICAL HOSTNAME ON THE 2ND COULUMN OF DB2NODES.CFG FOR DB2IUPDT COMMAND

DB2 Version 9.5 Fix Pack 3b for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4  for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• While  running  db2iupdt  it's  returning,
  'DBI1167E DPF instance cannot be updated from non instance
  owning nodes.\n'
  
  In the debug  output  it's  showing the reason of failure is the
  output of hostname command and the 2nd column of db2nodes.cfg
  are not matching.
  
  --------------------------------------------------
  ++ awk '{print $2}'
  + owning_host=<hostname-from-db2nodes.cfg>
  + '[' <output-of-hostname-command> '!=' <hostname-from-db2nodes.
  cfg >']'
  ---------------------------------------------------
  
  DB2 supports canonical hostnames at the 2nd column of
  db2nodes.cfg  for various reasons.  However, many existing
  customers are using noncanonical names over the time without
  problems.  Hence,  it's decided to support noncanonical name in
  the 2nd column of db2nodes.cfg  to help db2iupdt  to succeed.
  
  This is applicable only for the UNIX platforms including Linux
  

Local fix

• Chnage the 2nd coulumn of  db2nodes.cfg to canonical hostname
  which is the output of hostname command. After db2iupdt is
  completed the name could be changed back.
  

Problem summary

• Users affected : Users using non-canonical host name in 2nd
  column of  db2nodes.cfg
  
  Problem Description: Please see  PMR text
  
  Problem Summary: The fix will allow non-canonical host name
  in the db2nodes.cfg for db2iupdt to be successful. However,
  it's suggested to use canonical hostname if possible.
  

Problem conclusion

• First fixed in DB2 UDB Version 9.5, FixPak 3
  CQ defect#wsdbu00351764
  

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

  DB2 UDE ESE LIN

• Fixed component ID

  5765F4104

Applicable component levels

• R950 PSY

     UP