JR29344: db2iclus.exe fails with exception in sqlo_cluster_addnode() -> sqlomcpi() when the machine name is not in the cluster.

DB2 Version 9.1 Fix Pack 7  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6   for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
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

• An exception occurs in sqlo_cluster_addnode() -> sqlomcpi()
  when trying to add a computer to the Microsoft Cluster (MSCS)
  with the /M option if the computer name matches one of the
  following conditions:
  
  (1) it is not one of the machines in the cluster or
  (2) it is 15 characters long or
  (3) both (1) and (2)
  
  For example,
  
    db2iclus ADD /i:DB2 /m:ABCDEFGHIJKLMNO /c:CLUSTER
  /u:domain\user1
  
  The error reported in the Windows Event Viewer and Dr. Watson
  would look something similar to the followig -
  
  1. Here's an example from the Windows Event viewer -
  
  * * * Error being returned in Event Viewer:
  
  Event Type: Error
  Event Source: Application Error
  Event Category: (100)
  Event ID: 1000
  Date:  5/19/2008
  Time:  2:25:28 PM
  User:  N/A
  Computer: ABCDEFGHIJKLMNO
  Description:
  Faulting application db2iclus.exe, version 9.1.300.257, faulting
  module db2sys.dll, version 9.1.300.257, fault address
  0x0004dd03.
  
  For more information, see Help and Support Center at
  http://go.microsoft.com/fwlink/events.asp.
  Data:
  0000: 41 70 70 6c 69 63 61 74   Applicat
  0008: 69 6f 6e 20 46 61 69 6c   ion Fail
  0010: 75 72 65 20 20 64 62 32   ure  db2
  0018: 69 63 6c 75 73 2e 65 78   iclus.ex
  0020: 65 20 39 2e 31 2e 33 30   e 9.1.30
  0028: 30 2e 32 35 37 20 69 6e   0.257 in
  0030: 20 64 62 32 73 79 73 2e    db2sys.
  0038: 64 6c 6c 20 39 2e 31 2e   dll 9.1.
  0040: 33 30 30 2e 32 35 37 20   300.257
  0048: 61 74 20 6f 66 66 73 65   at offse
  0050: 74 20 30 30 30 34 64 64   t 0004dd
  0058: 30 33                     03
  
  2. Here's an example from the "Dr. Watson" log -
  
  The application, D:\DataBase\IBM\SQLLIB\BIN\db2iclus.exe,
  generated an application error The error occurred on 05/19/2008
  @ 16:41:33.126 The exception generated was c0000005 at address
  6DABDD03 (DB2SYS!sqlomcpi)
  

Local fix

• To workaround this, try setting up a machine name with less than
  15 characters long.
  

Problem summary

• Users affected:
  Only Microsoft Cluster (MSCS) environment.
  
  Problem Description:
  If this APAR fix is not applied, users could experiencing an
  exception error as described in the "Error Description".
  
  Problem Summary: See "Error Description".
  

Problem conclusion

• First fixed in DB2 UDB Version 9.1, FixPak 6.
  

Temporary fix

• To workaround this, try setting up a machine name with less than
  15 characters long.
  

Comments

APAR Information

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

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

  JR29448 JR29449

Fix information

• Fixed component name

  DB2 UDB ESE WIN

• Fixed component ID

  5765F4101

Applicable component levels

• R910 PSY

     UP