IT06018: ESXI PROBE FAILS WITH BTAVM2207E AND BTAVM2017E

APAR status

• Closed as program error.

Error description

• The following errors are found in the ESX Probe logs
  (device/log/db2admin.Probe_HYPERVISOR_xxxx_probe_hypervisor.PROC
  ESS_PROBE_HYPERVISOR.xxxxx.log):
  '''''''''''''
  2014-11-06 08:58:11.766-0600 BTAVM2207E Calculation of the
  summary data for the hypervisor ftwvmesxp025.rails.rwy.bnsf.com
  failed.
  2014-11-06 08:59:07.135-0600 BTAVM2017E Probe of the hypervisor
  ftwvmesxp025.rails.rwy.bnsf.com failed.
  '''''''''''''
  The trace files traceTPCDeviceServer.log indicate a
  SqlIntegrityConstraintViolationException when T_RES_CLUSTER is
  updated:
  '''''''''''''''''
  2014-11-06 08:58:10.674-0600 Entry   executeUpdate
  com.ibm.db2.jcc.am.ko@b39150f5, update T_RES_CLUSTER set
  DOMAIN_ID=?, IP_ADDRESS=?, CLUSTER_TYPE=?, DOMAIN_NAME=?,
  DISCOVERED_TIME=?, CLUSTER_NAME=?, CLUSTER_UID=? where
  CLUSTER_UID=?  Process Processor (Thread-522)
  2014-11-06 08:58:10.674-0600 Encountered an exception while
  trying to update row in database.  Update SQL was: update
  T_RES_CLUSTER set DOMAIN_ID=?, IP_ADDRESS=?, CLUSTER_TYPE=?,
  DOMAIN_NAME=?, DISCOVERED_TIME=?, CLUSTER_NAME=?, CLUSTER_UID=?
  where CLUSTER_UID=?
  and values were: {Column: CLUSTER_ID, Data Type: 4=122541098,
  Column: IP_ADDRESS, Data Type: 12= , Column: DOMAIN_ID, Data
  Type: 4=-1, Column: DISCOVERED_TIME, Data Type: 93=2014-11-06
  08:58:10.674, Column: CLUSTER_UID, Data Type:
  12=domain-c1402+122541080,
  Column: CLUSTER_TYPE, Data Type: 5=52, Column: DOMAIN_NAME, Data
  Type: 12= , Column: CLUSTER_NAME, Data Type: 12=FTW-WIN-01}
    com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException:
  DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505,
  SQLERRMC=3;TPC.T_RES_CLUSTER, DRIVER=3.65.77
     at com.ibm.db2.jcc.am.cd.a(cd.java:694)
  ...................
  '''''''''''''''''
  The root cause is that the cluster_uid is not a unique primary
  key.
  In particular, the DB shows that
  CLUSTER_UID=domain-c1402+122541080 is related to
  CLUSTER_NAME=FTW-WIN-02
  but in the log above shows CLUSTER_UID = domain-c1402+122541080
  is related to CLUSTER_NAME = FTW-WIN-01.
  The fix proposes to build the cluster UID using vCenter IP
  instead of data source id, the cluster UID will look like
  "domain-c345+9.11.66.134" ensuring uniqueness regardless of data
  source.
  

Local fix

• Contact support.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * TPC 5.2.x users with hypervisor probes                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fix maintenance when available.                        *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is targeted for the following maintenance
  package:
  
  
  | refresh pack | 5.2-TIV-TPC-RP0004
  
  http://www-01.ibm.com/support/docview.wss?&uid=swg21320822
  
  The target dates for future refresh packs or fix packs do not
  represent a formal commitment by IBM. The dates are subject to
  change without notice.
  

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:

Modules/Macros

• DATA
  

Fix information

• Fixed component name

  TPC

• Fixed component ID

  5608TPC00

Applicable component levels

• R522 PSY

     UP