IT03191: AUTOMATED DB BACKUP NOT BEING TRIGGERED EVEN THOUGH "ARCHLOGUSEDTHRESHOLD" HAS BEEN EXCEEDED

APAR status

• Closed as program error.

Error description

• In Tivoli Storage Manager server version 7.1.x  the
  "ARCHLOGUSEDTHRESHOLD" option is recursively processing the
  "ARCHLOGDirectory" location to determine if the threshold has
  been exceeded and thus a database backup is required.
  
  This is not correct behavior because there will only be archive
  log files under:
  
  ARCHLOGDirectory/<DB2 instance name>
  
  For example on UNIX and Linux platforms, if using
  ARCHLOGDirectory /home/tsminst1/archlog
  
  it will be
  /home/tsminst1/archlog/tsminst1
  
  
  In the above example, there might be a problem if the user
  running the Tivoli Storage Manager server does not have the
  permission to open directories underneath
  "/home/tsminst1/archlog/", for e.g.
  
  "/home/tsminst1/archlog/lost+found"
  
  However, as the log files will only be written to the directory
  defined as the ARCHLOGDirectory/<DB2 instance name>, there is no
  requirement to access the additional directory objects.
  The symptom might be seen on Windows platform, too, as Windows
  file systems may have a special directory "System Volume
  Information" similar to "lost+found" on  UNIX.
  
  No error is seen in the activity log.
  
  The indicator is that space usage of archlogdirectory location
  has exceeded ARCHLOGUSEDTHRESHOLD
  percentage setting, when reviewing "q log f=d".
  
  
  
  
  
  Tivoli Storage Manager versions affected:
  Server 7.1 on all platforms
  
  
  
  Initial Impact: Medium
  
  
  
  Additional Keywords:
  zz71 backup db database archive log space usage percentage
  

Local fix

• Regularly run manual or scheduled database backups.
  

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 level 7.1.1. Note that this is      *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  

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

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R71L PSY

     UP

• R71A PSY

     UP

• R71H PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP