IV12849: ZERO BYTE HDR FILE NOT HANDLED CORRECTLY FOR HISTORICAL COLLECTION

IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)

APAR status

• Closed as program error.

Error description

• When the hdr file used for historical collection at the TEMS or
  TEMA is
  zero bytes then then historical collection fails to recover from
  this
  and shuts down historical collection for the table being
  collected.  The
  code should be able to determine this condition and recover.
  
  
  
   RECREATE INSTRUCTIONS:
  
  Make a zero byte *.hdr file for any historical collection table
  and the
  start collection for that table.  The UADVISOR will start and
  then
  shutdown based on the zero byte file.  The code should treat
  this as no
  file exists and create a new hdr file and overwrite the zero
  byte hdr
  file.
  

Local fix

• Erase the zero byte file and restart the historical collection.
  

Problem summary

• Historical collection fails to start if the header file (.hdr)
  is zero bytes.
  
  
  The header file used on the monitoring server and monitoring
  agent for historical collection is currently not tested for zero
  bytes, and therefore, historical collection fails to start. A
  zero byte header file can occur if the process is terminated in
  the middle of the header creation or if the krarloff historical
  short-term offload program is used while historical collection
  is enabled. The zero byte header file also causes display of
  data on the portal to fail.
  

Problem conclusion

• The agent framework now tests for a zero byte header file and
  recreates the header file based on the historical table name.
  This change is required for the historical collection service
  and historical reporting.
  
  The fix for this APAR is contained in the following maintenance
  packages:
    | fix pack | 6.2.2-TIV-ITM-FP0009
    | fix pack | 6.2.3-TIV-ITM-FP0002
  

Temporary fix

• Locate header files with the ".hdr" file extension in
  platform-specific directories:
  
      On the monitoring agent,
          ITM_HOME\TMAITM6\logs\History\<product-code> (Windows)
          ITM_HOME/<architecture>/<product-code>/hist (UNIX/Linux)
          Example: /opt/IBM/ITM/aix523/t6/hist (UNIX/Linux)
      On the monitoring server,
          ITM_HOME\CMS (Windows)
          ITM_HOME/tables/<tems-name> (UNIX/Linux)
          Example: /opt/IBM/ITM/tables/mytems
  
  Delete the zero byte header files, and restart the historical
  collection. Alternatively, recycle the affected monitoring
  server or monitoring agent.
  

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

  TEMA

• Fixed component ID

  5724C04TE

Applicable component levels

• R622 PSY

     UP