IBM Support

IC98469: UNEXPECTED SUB_ENTITY AND SCHEDULE_NAME ASSOCIATION IN SUMMARY_EXTENDED TABLE FOR VM BACKUPS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • The SUMMARY_EXTENDED table might have unexpected SUB_ENTITY and
    SCHEDULE_NAME associations when multiple schedules for VM
    backups are defined to start at the same time.
    The activity log and scheduler logs will report successful
    completion and correct statistics, only the SUMMARY_EXTENDED
    table is affected.
    VMware and Hyper-V scheduled backups are affected.
    This impacts all monitoring tools using this table.
    
    Example :
    
    Three schedules are defined to backup three different VM guests
    to all start at 13:25 :
    
    schedule  VM guest
    --------  --------
    sched1    dummy1
    sched2    dummy2
    sched3    dummy3
    
    Upon completion, the following might be seen :
    
    select START_TIME, ENTITY, SUB_ENTITY, SCHEDULE_NAME from
    summary_extended where upper(schedule_name) like 'SCHED%' order
    by start_time desc
    
    
       START_TIME: 2013-12-01 13:25:58.000000
           ENTITY: 6.4_VC1_DC1_POL_DM1
       SUB_ENTITY: dummy3
    SCHEDULE_NAME: SCHED3
    
       START_TIME: 2013-12-01 13:25:41.000000
           ENTITY: 6.4_VC1_DC1_POL_DM1
       SUB_ENTITY: dummy2
    SCHEDULE_NAME: SCHED1
    
       START_TIME: 2013-12-01 13:25:18.000000
           ENTITY: 6.4_VC1_DC1_POL_DM1
       SUB_ENTITY: dummy1
    SCHEDULE_NAME: SCHED1
    
    The unexpected output is :
    
       SUB_ENTITY: dummy2
    SCHEDULE_NAME: SCHED1
    
    while we should see :
    
       SUB_ENTITY: dummy2
    SCHEDULE_NAME: SCHED2
    
    Tivoli Storage Manager Versions Affected:
    Tivoli Storage Manager server 6.3 and 7.1 and later on all
    platforms
    
    Initial Impact: Medium
    Additional Keywords: tsm zz64 vmware schedule summary report
    monitor unexpected backup VM
    

Local fix

  • Avoid defining schedules to start at the exact same time.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Tivoli Storage Manager server users.                     *
    ****************************************************************
    * 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, Solaris, Linux, and         *
    * Windows.                                                     *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IC98469

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    63W

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-12-23

  • Closed date

    2014-08-12

  • Last modified date

    2015-09-16

  • 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

    TSM SERVER

  • Fixed component ID

    5698ISMSV

Applicable component levels

  • R63W PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"63W","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
16 September 2015