IV31937: DATA PROVIDER CORES ON ODM ERROR

IBM Tivoli Monitoring 6.2.3 Fix Pack 3 (6.2.3-TIV-ITM-FP0003)

APAR status

• Closed as program error.

Error description

• This is a sysroute of APAR IV29791.  In the UNIX OS Agent 6.2.3
  FP1, the agent might crash with the following lines in the log
  file:
  
  (5069DDA4.011B-1:dkstats.c,1787,"get_cu_adptr") Error in
  get_cu_adptr():
  odm_get_list(): CFG_ODM_ACCESS.
  (5069DDA4.011C-1:dkstats.c,1788,"get_cu_adptr") Error :
  CFG_ODM_ACCESS.
  (5069DDA4.011D-1:stacktrace.cpp,101,"exit_with_notification")
  FATAL
  ERROR: Fatal error (11) detected.  Shutdown initiated.
  
  -------------------------------------------------------------
  
  The original error description for the AIX Premium agent is
  here:
  
  The aixDataProvider-61 process might core dump after receiving
  an ODM error.  The
  <hostname>_px_aixDataProvider-61_<timestamp>_01.log might have
  one of these two messages:
  
  ------------------------------------
  dkstats.c,1928,"get_cu_adptr") Error in get_cu_adptr():
                                 odm_get_list(): CFG_ODM_ACCESS.
  dkstats.c,1929,"get_cu_adptr") Error : CFG_ODM_ACCESS.
  dkstats.c,1936,"get_cu_adptr") Exit: 0xFFFFFFFF
  dkstats.c,1485,"reset_tbl") Active RAS1 Classes: EVERYT EVERYE
  EVERYU
  dkstats.c,1485,"reset_tbl") Entry
  ------------------------------------
  
  or (and this might occur on systems that have disks that do
  not store information in the ODM):
  
  ------------------------------------
  CP8: goto loop1
  iost_dkcnt: 43, last_dkstat[iost_dkcnt].diskname: [[,
  dkstat[iost_dkcnt].diskname: 0<88>^?
  ======System configuration has changed=========
  ...
  dkstats.c,2658,"updt_adptr_withpaths") Entry
  dkstats.c,2679,"updt_adptr_withpaths") Error in
  updt_adptr_withpaths():
                  odm_get_list(): 0519-100 libodm: Cannot open the
  object
                  class collection file.
                  Check path name and permissions.
  ------------------------------------
  
  The core dump generates the following stack trace:
  
  reset_tbl() at 0x10021808
  resetclean() at 0x1002198c
  reset() at 0x1002ad0c
  get_diskstats() at 0x1003207c
  adp_get_diskstats(0x2ff21804) at 0x10006ec0
  dt_CollectDiskData(0x309e94b0, 0x308e1d48) at 0x100388a8
  dt_CollectData(0x309e94b0, 0x308e1d48) at 0x1003d134
  itmTranslator(0x0) at 0x1003debc
  main(0x1, 0x2ff21b5c) at 0x100077d0
  
  RECREATE INSTRUCTIONS: None.
  

Local fix

Problem summary

• Data provider cores on AIX Object Data Manager (ODM) error.
  
  The aixDataProvider-61 process might core dump after receiving
  an ODM error.  The
  <hostname>_px_aixDataProvider-61_<timestamp>_01.log might have
  one of these two messages:
  ------------------------------------
  dkstats.c,1928,"get_cu_adptr") Error in get_cu_adptr():
  odm_get_list(): CFG_ODM_ACCESS.  dkstats.c,1929,"get_cu_adptr")
  Error : CFG_ODM_ACCESS.
  dkstats.c,1936,"get_cu_adptr") Exit: 0xFFFFFFFF
  dkstats.c,1485,"reset_tbl") Active RAS1 Classes: EVERYT EVERYE
  EVERYU                    dkstats.c,1485,"reset_tbl") Entry
  ------------------------------------
  
  or (and this might occur on systems that have disks that do not
  store information in the ODM):
  
  ------------------------------------
  CP8: goto loop1
  iost_dkcnt: 43, last_dkstat[iost_dkcnt].diskname:
  [[,dkstat[iost_dkcnt].diskname:0<88>^?
  ======System configuration has changed=========
  ...
  dkstats.c,2658,"updt_adptr_withpaths") Entry
  dkstats.c,2679,"updt_adptr_withpaths") Error in
  updt_adptr_withpaths():
                  odm_get_list(): 0519-100 libodm: Cannot open the
  object class collection file.
                  Check path name and permissions.
  ------------------------------------
  
  The core dump generates the following stack trace:
  
  reset_tbl() at 0x10021808
  resetclean() at 0x1002198c
  reset() at 0x1002ad0c
  get_diskstats() at 0x1003207c
  adp_get_diskstats(0x2ff21804) at 0x10006ec0
  dt_CollectDiskData(0x309e94b0, 0x308e1d48) at 0x100388a8
  dt_CollectData(0x309e94b0, 0x308e1d48) at 0x1003d134
  itmTranslator(0x0) at 0x1003debc
  main(0x1, 0x2ff21b5c) at 0x100077d0
  

Problem conclusion

• Code has been changed in order to manage ODM errors.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | fix pack | 6.2.3-TIV-ITM-FP0003
  

Temporary fix

Comments

APAR Information

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

  IV29791

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

Fix information

• Fixed component name

  ITM AGENT UNIX

• Fixed component ID

  5724C040U

Applicable component levels

• R623 PSY

     UP