IC72333: SELECT FROM EVENTS TABLE RETURNS EVENTS WITH UNCERTAIN STATUS.

APAR status

• Closed as fixed if next.

Error description

• The Tivoli Storage Manager server reports events with
  Uncertain status when using the Administration Center or
  using the "select * from events" administrative command.
  Likewise the TEP Schedule workspace will report an "Unknown"
  value for the Schedule Status. The TEP Schedule workspace issues
  the following select command to query schedule events :
  
  select a.SCHEDULE_NAME, a.NODE_NAME, a.SCHEDULED_START,
  a.ACTUAL_START,  a.STATUS, a.RESULT, a.REASON, a.DOMAIN_NAME,
  b.NODETYPE from EVENTS as a, NODES as b where
  (LENGTH(a.domain_name) IS NOT NULL and
  a.NODE_NAME = b.NODE_NAME) or (a.NODE_NAME = b.NODE_NAME and
  a.NODE_NAME IS NULL and LENGTH(a.domain_name) IS NULL)
  
  The above select command may report events with Uncertain status
  (or Unknown in TEP). For example :
  
    SCHEDULE_NAME: TEST
        NODE_NAME: TESTNODE
  SCHEDULED_START: 2010-08-26 16:39:31.000000
     ACTUAL_START:
           STATUS: Uncertain
           RESULT:
           REASON:
      DOMAIN_NAME: STANDARD
         NODETYPE: CLIENT
  
  Customer/L2 Diagnostics:
  The TSM server will return events based on the schedule start
  time of the oldest event recorded in the table. A schedule
  event associated to a schedule defined with an "indefinite"
  duration will be recorded in the table with a deadline set to
  "2069-10-11-00.00.00.000000".  For example :
  
  NODEID     : 123
  DOMAINNAME : UNIX_DOM
  SCHEDNAME  : INCREMENTAL_DAILY
  SCHEDSTART : 2009-09-15-20.00.00.000000
  ACTSTART   : 2009-09-15-20.11.32.000000
  COMPLETED  : 2009-09-15-22.37.04.000000
  DEADLINE   : 2069-10-11-00.00.00.000000
  STATE      : 32
  RESULT     : 0
  
  This record will not get deleted until the deadline timestamp
  has elapsed. In this example, the select command would return
  all schedule events starting from "2009-09-15-20.00.00.000000".
  Because of the "Event Record Retention Period", some events
  may no longer exist and their associated status would then be
  reported as Uncertain (or Unknown in TEP).
  
  Verify the schedule_event table for the event with the longest
  oldest deadline. For example :
  
  For UNIX and Linux servers, logon with the TSM server instance
  and run the following commands :
  db2 connect to tsmdb1
  db2 set schema tsmdb1
  db2 "select * from schedule_event order by deadline desc"
  
  For Windows servers, logon with the userid that starts the
  TSM server service and start a Windows command prompt and enter
  the following commands :
  db2cmd
  set db2instance=server1  (specify the appropriate instance name)
  db2 connect to tsmdb1
  db2 set schema tsmdb1
  db2 "select * from schedule_event order by deadline desc"
  
  Verify the SCHEDSTART field of the first entry returned by the
  above select command. The timestamp of the SCHEDSTART field
  determines how far back the TSM select command returns
  events for schedules.
  
  TSM Versions Affected:
  Tivoli Storage Manager server V6.1 and V6.2 on all platforms
  
  Additional Keywords:
  zz61 zz62 sched query portal 1452154
  

Local fix

• Contact TSM support to delete the entries manually.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users      *
  *                 of the SELECT command on EVENTS table.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This problem is projected to be fixed in a future version
  of the Tivoli Storage Manager server.
  Note that this is subject to change at the discretion of IBM.
  Affected platforms:  AIX, HP-UX, Sun Solaris, Linux,
  and Windows.
  

Problem conclusion

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

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61L PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP