IV45838: OBJECTSERVER CONNECTION DOES NOT RECOVER FROM BUSY PERIOD IF SELFMONITORING (DATASOURCE MONITORING) IS ENABLED

6.1.0-TIV-BSM-FP0004-zlinux
6.1.0-TIV-BSM-FP0004-windows
6.1.0-TIV-BSM-FP0004-solaris
6.1.0-TIV-BSM-FP0004-linux
6.1.0-TIV-BSM-FP0004-aix
6.1.0-TIV-NCI-FP0004-zlinux
6.1.0-TIV-NCI-FP0004-windows
6.1.0-TIV-NCI-FP0004-solaris
6.1.0-TIV-NCI-FP0004-aix
6.1.0-TIV-NCI-FP0004-linux
6.1.1-TIV-BSM-FP0004-windows
6.1.1-TIV-BSM-FP0004-zlinux
6.1.1-TIV-BSM-FP0004-solaris
6.1.1-TIV-BSM-FP0004-linux
6.1.1-TIV-BSM-FP0004-aix
6.1.1-TIV-NCI-FP0004-windows
6.1.1-TIV-NCI-FP0004-zlinux
6.1.1-TIV-NCI-FP0004-solaris
6.1.1-TIV-NCI-FP0004-aix
6.1.1-TIV-NCI-FP0004-linux
6.1.0-TIV-NCI-FP0003-zlinux
6.1.0-TIV-NCI-FP0003-windows
6.1.0-TIV-NCI-FP0003-solaris
6.1.0-TIV-NCI-FP0003-linux
6.1.0-TIV-NCI-FP0003-aix
6.1.0-TIV-BSM-FP0003-solaris
6.1.0-TIV-BSM-FP0003-aix
6.1.0-TIV-BSM-FP0003-zlinux
6.1.0-TIV-BSM-FP0003-windows
6.1.0-TIV-BSM-FP0003-linux
5.1.1-TIV-NCI-FP0003-Linux
5.1.1-TIV-NCI-FP0003-HPUX
5.1.1-TIV-NCI-FP0003-win
5.1.1-TIV-NCI-FP0003-Solaris
5.1.1-TIV-NCI-FP0003-Linuxs390
5.1.1-TIV-NCI-FP0003-aix
6.1.1-TIV-BSM-FP0003-aix
6.1.1-TIV-NCI-FP0003-zlinux
6.1.1-TIV-NCI-FP0003-windows
6.1.1-TIV-NCI-FP0003-solaris
6.1.1-TIV-NCI-FP0003-linux
6.1.1-TIV-NCI-FP0003-aix
6.1.1-TIV-BSM-FP0003-zlinux
6.1.1-TIV-BSM-FP0003-windows
6.1.1-TIV-BSM-FP0003-solaris
6.1.1-TIV-BSM-FP0003-linux
6.1.1-TIV-BSM-FP0002-windows
6.1.1-TIV-BSM-FP0002-zlinux
6.1.1-TIV-BSM-FP0002-solaris
6.1.1-TIV-BSM-FP0002-aix
6.1.1-TIV-BSM-FP0002-linux
6.1.1-TIV-NCI-FP0002_zlinux
6.1.1-TIV-NCI-FP0002_windows
6.1.1-TIV-NCI-FP0002_solaris
6.1.1-TIV-NCI-FP0002_linux
6.1.1-TIV-NCI-FP0002_aix
IBM Tivoli Business Service Manager V6.1.1 Fix Pack 1(6.1.1-TIV-BSM-FP0001)
IBM Tivoli Business Service Manager V6.1.0 Fix Pack 2(6.1.0-TIV-BSM-FP0002)
IBM Tivoli Netcool/Impact V6.1.0 Fix Pack 2(6.1.0-TIV-NCI-FP0002)
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 2 (6.1.1-TIV-NCI-FP0002)
IBM Tivoli Business Service Manager V6.1.1 Fix Pack 3(6.1.1-TIV-BSM-FP0003)
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 3 (6.1.1-TIV-NCI-FP0003)
IBM Tivoli Netcool/Impact V5.1.1 Fix Pack 3 (5.1.1-TIV-NCI-FP0003)
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 4 (6.1.1-TIV-NCI-FP0004)
IBM Tivoli Business Service Manager V6.1.1 Fix Pack 4(6.1.1-TIV-BSM-FP0004)
IBM Tivoli Netcool/Impact V6.1.0 Fix Pack 4(6.1.0-TIV-NCI-FP0004)
IBM Tivoli Business Service Manager V6.1.0 Fix Pack 4(6.1.0-TIV-BSM-FP0004)
IBM Tivoli Netcool/Impact V6.1.0 Fix Pack 4(6.1.0-TIV-NCI-FP0004)
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 5 (6.1.1-TIV-NCI-FP0005)
IBM Tivoli Business Service Manager V6.1.1 Fix Pack 5(6.1.1-TIV-BSM-FP0005)

APAR status

• Closed as program error.

Error description

• The connection to an ObjectServer becomes unresponsive as the
  tables lock up for some reason - ObjectServer failover and
  gateway locking the tables during synchronisation - when this
  is complete the Impact EventReader > ObjectServer connection
  does not come back when SelfMonitoring DataSource monitoring is
  enabled (Impact 6.1.0 and 6.1.1).
  
  In Impact 5.1.1 this has been observed too, but for the whole
  of the SelfMonitoring Service (not just DataSource monitoring).
  

Local fix

• Disable SelfMonitoring DataSource monitoring (Impact 6).
  Disable SelfMonitoring (Impact 5.1.1).
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL Impact 5.1.1, 6.1 and 6.1.1 Users                        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * OBJECTSERVER CONNECTION DOES NOT RECOVER FROM BUSY PERIOD IF *
  * SELFMONITORING (DATASOURCE MONITORING) IS ENABLED            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * NONE                                                         *
  ****************************************************************
  If a customer is monitoring an object server datasource and this
  is the same datasource where the event reader is sending the
  events, sometimes when the object server is busy or unavailable,
  impact is not able to connect to it when it becomes available
  and the event reader is not able to send events.
  

Problem conclusion

• The issue was that when data source monitoring was sending a
  status event, it would sometimes get stuck in a loop. The fix
  should prevent data source monitoring from getting stuck in a
  loop. The fix for this APAR is contained in the following
  maintenance package:| Fix pack | 5.1.1-TIV-NCI-FP0003 | Fix Pack
  | 6.1.0-TIV-NCI-FP0002
  

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

  NETCOOL/IMPACT

• Fixed component ID

  5724O59IS

Applicable component levels

• R610 PSY

     UP