IC60975: EXTENDING THE TRANSACTION LOG FOR TSM SERVER DOES NOT UPDATE THE NUM_LOG_SPAN CONFIGURATION PARAMETER IN DB2.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The default log size of 2GB allows 4 log volumes for the
    transaction log. When the server database is first formatted,
    TSM sets NUM_LOG_SPAN to 90% of this size (3 volumes).  When the
    transaction log is increased in the dsmserv.opt file, the
    NUM_LOG_SPAN is not updated to represent 90% of the new log size
    in DB2.
    The NUM_LOG_SPAN setting is used by TSM to manage how much of
    the active log a transaction can span.  By limiting a
    transaction in this fashion, the TSM server is taking proactive
    steps to prevent a server out of log situation which may result
    in the server terminating.  The NUM_LOG_SPAN setting allows the
    transaction to be identified and cancelled while there is still
    available active log space remaining.  Even with this setting,
    there may still be cases that the transaction on the server will
    drive the head of the active log forward faster then the
    offending transaction can be aborted and rolled back.
    If the server crashes as a result of server out of log space,
    the db2diag.log will show:
    MESSAGE : ADM1541W  Application "dsmserv" with application
    handle
    "0-9683" and application id "*LOCAL.tsminst1.090415040019"
    executing under authentication id "TSMINST1" has been forced off
    of the database for violating database configuration parameter
    NUM_LOG_SPAN (current value "3"). The unit of work will be
    rolled back.
    
    In this example, the "(current value "3")" relates to the fact
    that when this server was formatted (installed), the active log
    size was 2 GB which results in a NUM_LOG_SPAN value of 3.  If
    the server had been formatted using a different active log size,
    then the value displayed would have been something other than
    "3".
    
    Additional Keywords: zz61
    

Local fix

  • The work around is to manually calculate 90% of the log size and
    update the db2 database to correctly set NUM_LOG_SPAN.
    Calculate correct value of NUM_LOG_SPAN
    Each log size is fixed at 512MB.
    1. Take the new value of activelogsize in dsmserv.opt in and
    divide that by 512MB. This value is the total number of log
    volumes reflected in db2 value LOGPRIMARY.
    2. Multiple LOGPRIMARY by 90%. This value should be reflected in
    NUM_LOG_SPAN.
    (alternate method involving slightly less arithmetic)
    Calculate correct value of NUM_LOG_SPAN
    1. Use the following db2 command to determine the number of log
    volumes used:
       db2 get db cfg for TSMDB1
    2. Multiply the value for the LOGPRIMARY parameter by 90%.  This
    value should be reflected in NUM_LOG_SPAN.
    Update NUM_LOG_SPAN by issuing the following db2 command:
    db2 update db cfg for TSMDB1 using NUM_LOG_SPAN <newValue>
    You may need to restart the TSM server, which will restart the
    db2 database as well.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Tivoli Storage Manager server       *
    *                 V6.1.0.0 or V6.1.1.0.                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: See ERROR Description.                  *
    ****************************************************************
    * RECOMMENDATION: Apply the level containing this fix when     *
    *                 available. This problem is currently         *
    *                 projected to be fixed in level 6.1.2.        *
    *                 Note that this is subject to change          *
    *                 at the discretion of IBM.                    *
    ****************************************************************
    *
    

Problem conclusion

  • The issue has been corrected.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC60975

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    61L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-04-29

  • Closed date

    2009-05-07

  • Last modified date

    2009-09-04

  • 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

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61L PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Storage Manager

Software version:

61L

Reference #:

IC60975

Modified date:

2009-09-04

Translate my page

Machine Translation

Content navigation