IC71005: ARCHIVE LOG SIZE ESTIMATION TO TRIGGER A DATABASE BACKUP CAN BE REFINED.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The archive log size estimation used to decide when a database
    backup is needed can be refined. The current estimation just
    monitors the entire file system utilisation. When it reaches 80%
    a database backup is triggered to be able to reclaim space.
    This estimation could be adapted in case the file system is big.
    In that case, even if the file system reaches 80% (for example
    if the file system is filled by other data) there could still
    plenty of room for the archive logs.
    
    Another symptom would be that frequent database backups are
    triggered automatically. For example, if the archive log
    directory resides on a file system or drive that is 400GB in
    size, a database backup will be triggered if there is less than
    80GB of free space. Those repeated database backups may cause
    an excessive amount of scratch tapes to be used.
    
    Tivoli Storage Manager Versions Affected:6.x all platforms
    
    Initial Impact: Low
    Additional Keywords: archive log, dbbackup, database, trigger,
    automatic
    

Local fix

  • The recommendation is to use a dedicated file system for the
    archive logs.
    If this is not possible, add the following option to the server
    options file :
    ARCHLOGUSEDTHRESHOLD  XX
    The default value is :
    ARCHLOGUSEDTHRESHOLD  80
    In the the case where the file system has a large amount of free
    space, increase the value to prevent the trigger of frequent db
    backups.
    For example :
    ARCHLOGUSEDTHRESHOLD  90
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Tivoli Storage Manager server users.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available. This      *
    *                 problem is currently projected to be fixed   *
    *                 in levels 6.1.5, and 6.2.3 . Note that       *
    *                 this is subject to change at the             *
    *                 discretion of IBM.                           *
    ****************************************************************
    *
    

Problem conclusion

  • Affected platforms:  AIX, HP-UX, Sun Solaris, Linux, and
    Windows.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC71005

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    61W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-09-10

  • Closed date

    2010-11-30

  • Last modified date

    2010-12-10

  • 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

  • R62A PSY

       UP

  • R62H PSY

       UP

  • R62L PSY

       UP

  • R62S PSY

       UP

  • R62W PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager

Software version:

61W

Reference #:

IC71005

Modified date:

2010-12-10

Translate my page

Machine Translation

Content navigation