IV80618: SEEDING AN RTEMS CAUSES THE SQL TO BE PROCESSED AT THE HUB

IBM Tivoli Monitoring 6.3.0 Fix Pack 7 (6.3.0-TIV-ITM-FP0007)

APAR status

• Closed as program error.

Error description

• Seeding the RTEMS caused the sql seeding to be performed at the
  HUB and the rest of the seeding actions to be performed at the
  RTEMS. When the sql seeding is performed, any situations that
  are updated are restarted. Performing the sql seeding at the HUB
   caused the MS_OFFLINE situation (and others) to restart.
  Restarting the MS_OFFLINE situation caused it to reprocess the
  2000+ agents that were already off-line and send alerts for each
   one of them.
  
  
  RECREATE INSTRUCTIONS:
  1) Install a Unix/Linux HUB TEMS and at least one Unix/Linux
  RTEMS from 6.23 on different systems.
  2) Perform seeding during the installation steps.
  3) Upgrade the HUB and RTEMS to 6.23 FP5.
  4) Save a copy of seed.sh calling it seed.6235.sh in each
  installation.
  5) Upgrade the HUB and RTEMS to 6.30 FP6
  6) Install the TEPS from 6.30 FP6.
  7) Connect some agents to the RTEMS
  8) Connect some agents to the HUB. Connect more agent types, or
  different agent types than those connected to the RTEMS.
  9) Install TEMS, TEPS, TEPW application support for all of the
  connected agents.
  10) Use tacmd login to login to the HUB.
  11) Use tacmd listsystems to list the agents connected and
  verify all HUB connected agents and the RTEMS and all RTEMS
  connected agents  are reporting to the HUB.
  12) Start the TEPS and TEP client.
  13) Distribute all situations for all connected agents.
  14) Create the file /tmp/querySITDB.sql with the following
  content:
  /* Report on O4SRV.SITDB */
  SELECT RULENAME, PREDICATE FROM O4SRV.SITDB ;
  15) Copy /tmp/querySITDB.sql to
  $CANDLEHOME/tables/cicatrsq/SQLLIB
  16) On The HUB TEMS system, run seed.sh and seed.6235.sh using
  querySITDB.sql
  17) Verify that the output from seed.sh and seed.6235.sh is the
  same.
  18) On The RTEMS system, run seed.sh and seed.6235.sh using
  querySITDB.sql
  19) Verify that the output from seed.sh and seed.6235.sh is
  different.
  20) Verify that the output from seed.sh on the HUB TEMS system
  is the same as the output from seed.sh on the RTEMS system.
  

Local fix

Problem summary

• Performing TEMS seeding on a Remote TEMS causes the sql to be
  processed at the HUB TEMS instead, restarting the MS_OFFLINE
  situation causing new alerts for numerous known off-line
  systems.
  

Problem conclusion

• The code was changed to process the sql on the Remote TEMS so
  that situations at the HUB TEMS will not be restarted.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.3.0-TIV-ITM-FP0007
  

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

  OMEG DIST INSTA

• Fixed component ID

  5608A41CI

Applicable component levels