IT33809: HYPERVISOR PROBE POST PROCESSING MAY FAIL WITH EXCEPTIONS.

APAR status

• Closed as program error.

Error description

• Hypervisor Panel overview screen Probe status and Last
  Successful Probe fields do not always reflect the status of the
  actual probe run results.
  
  This is caused by Hypervisor probe
  post processing failures
  follows:
  
  com.ibm.db2.jcc.am.SqlException:
  [jcc][t4][10120][10898][4.19.49] Invalid operation: result set
  has been closed.
  ERRORCODE=-4470, SQLSTATE=null
  The hypervisor
  probe logs contain similar errors:
  data/log/<user_id>.Probe_HYPE
  RVISOR_20190424_152746167.0420_probe_hypervisor.01011822.log
  202
  0-06-17 14:39:02.455+0200 STS0146E: Last prepared SELECT SQL
  statement:
  select model_name from t_res_model where model_id =
  ?
  com.ibm.db2.jcc.am.SqlException:
  [jcc][t4][10120][10898][4.19.49]
  Invalid operation: result set
  has been closed
  . ERRORCODE=-4470, SQLSTATE=null
   at
  com.ibm.db2.jcc.am.kd.a(Unknown Source)
   at
  com.ibm.db2.jcc.am.kd.a(Unknown Source)
   at
  com.ibm.db2.jcc.am.kd.a(Unknown Source)
   at
  com.ibm.db2.jcc.am.ResultSet.checkForClosedResultSet(Unknown
  Source)
   at com.ibm.db2.jcc.am.ResultSet.nextX(Unknown Source)
  
  at com.ibm.db2.jcc.am.ResultSet.next(Unknown Source)
   at com.ibm
  .tpc.infrastructure.database.JDBCWrapperResultSet.next(JDBCWrapp
  erResultSet.java:464)
   at com.ibm.tpc.infrastructure.database.DB
  ResultSet.next(DBResultSet.java:17)
   at com.tivoli.itsrm.reposit
  ory.RepositoryAccessor.nextResult(RepositoryAccessor.java:267)
  
  at com.tivoli.itsrm.repository.RepositoryAccessor.nextResult(Rep
  ositoryAccessor.java:262)
   at com.tivoli.itsrm.repository.TResVe
  ndorModel.getModelName(TResVendorModel.java:535)
   at com.tivoli.
  itsrm.TStorm.repository.TResDevice.getDevice(TResDevice.java:388
  )
   at com.tivoli.itsrm.TStorm.repository.TResDevice.getDevByCmp(
  TResDevice.java:277)
   at com.tivoli.itsrm.TStorm.server.svp.Hype
  rvisorProbeAlerter.getHypervisorsData(HypervisorProbeAlerter.jav
  a:266)
   at com.tivoli.itsrm.TStorm.server.svp.HypervisorProbeAle
  rter.getAfterProbeData(HypervisorProbeAlerter.java:119)
   at com.
  tivoli.itsrm.TStorm.server.svp.ExecProbeHypervisor.probeAll(Exec
  ProbeHypervisor.java:279)
   at com.tivoli.itsrm.TStorm.server.svp
  .ExecProbeHypervisor.doProbe(ExecProbeHypervisor.java:164)
  2020-
  06-17 14:39:02.455+0200 SRV0451E: Error calling device server
  {0} service.
   com.tivoli.itsrm.common.GeneralSQLException:
  SRV0081E
  2020-06-17 14:41:04.546+0200 GEN0400E: Probe completed
  with
  errors.
  ____________________________________________________
  DB2
  Version used for Server: N/A
  The defect is against component:
  Hypervisors
  Server/Manager build/release (TPC): v.5.3.7
  Agent
  build/release (TPC):
  Server/Manager (OS):
  Agent(OS):
  
  ____________________________________________________
  Problem
  as described by customer: Probe results not in sync with WEB UI
  status.
  Initial customer impact (low/med/high): med
  

Local fix

• TBD
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Control users monitoring large ESX hypervisors  *
  * where probes takes several hours                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The ESX hypervisor probe results are not in sync with what's *
  * displayed in the web GUI status.                             *
  *                                                              *
  * Hypervisor Panel overview screen showing the probe status    *
  * and Last Successful Probe fields do not always reflect the   *
  * status of the actual probe run results.                      *
  *                                                              *
  * This is caused by Hypervisor probe post processing failures. *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fix maintenance when available                         *
  ****************************************************************
  The fix was not to keep unnecessary a database connection
  open for too long. Release it before long-running tasks and
  obtain a new one afterward.
  

Problem conclusion

• The fix for this APAR is targeted for the following release:
  
  IBM Spectrum Control 5.4.1   [ 5.4.1-IBM-SC ]
  
  ( release target 4Q 2020 / November )
  
  http://www.ibm.com/support/docview.wss?&uid=swg21320822
  
  The target dates for future releases 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:

Fix information

• Fixed component name

  TPC ADVANCED

• Fixed component ID

  5608TPCA0

Applicable component levels