IBM Support

IC99259: CHANGES TO THE ACTIVELOGSIZE MIGHT NOT BE HONORED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible.

Error description

  • After a fresh installation of the Tivoli Storage Manager server
    or after server V 5.5 upgrade, changes to the ACTIVELOGSIZE
    might not get picked up during the first server start and the
    value will not be picked up afterwards until a change is made
    again.
    
    As an example, for a new server installation this results in the
    server running with the default logsize of 16GB:
    Recreate scenario (for fresh install):
    - configure filesystem for active log with 20GB of space
    - in dsmserv.opt specify
      ACTIVELOGSIZE 20000
    - upon server initialization QUERY LOG will show
    Total Space(MB)      Used Space(MB)      Free Space(MB)
    ---------------     ---------------     ---------------
             20,000               3,703              16,297
    
    From "db2 get db cfg"
     Log file size (4KB)                         (LOGFILSIZ) =
    131072
     Number of primary log files                (LOGPRIMARY) = 32
    
    (LOGFILSIZ * 4096KB = 512MB)
    
      Tivoli Storage Manager Versions Affected: all V6.3
      Initial Impact: Low
      Additional Keywords: ZZ63 TSM LOGFILESIZE dsmicfgx  dsmupgdx
    dsmserv format
    

Local fix

  • Either
    - stop the server,  remove the logattr.chk file from the
      instance directory and restart the server
    or
    - update the dsmserv.opt ACTIVELOGSIZE and restart the server
      (two restarts required to adjust to the original value)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Tivoli Storage Manager server users.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: See error description.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This problem only exists in the 6.1, 6.2 and 6.3 releases of
    the Tivoli Storage Manger server but will not be fixed in
    those releases.  This problem does not exist i
    n the 7.1 release which is the latest release of the Tivoli
    Storage Manager server.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IC99259

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    63A

  • Status

    CLOSED UR3

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-02-10

  • Closed date

    2014-04-14

  • Last modified date

    2014-04-14

  • 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

[{"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":"63A","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
14 April 2014