IT27787: SERVER MIGHT CRASH DUE TO ACTIVE LOG FILES NOT CLEARED PROPERLY

8.1.6.200-IBM-SPSRV-WindowsX64
8.1.6.200-IBM-SPSRV-Linuxx86_64
8.1.6.200-IBM-SPSRV-Linuxs390x
8.1.6.200-IBM-SPSRV-Linuxppc64le
8.1.6.200-IBM-SPSRV-AIX
8.1.7.000-IBM-SPSRV-Linuxppc64le
8.1.7.000-IBM-SPCMS-WindowsX64
8.1.7.000-IBM-SPCMS-WindowsI32
8.1.7.000-IBM-SPCMS-Linuxx86_64
8.1.7.000-IBM-SPOC-WindowsX64
8.1.7.000-IBM-SPOC-Linuxx86_64
8.1.7.000-IBM-SPOC-Linuxs390x
8.1.7.000-IBM-SPOC-LinuxPPC64le
8.1.7.000-IBM-SPOC-AIX
8.1.7.000-IBM-SPSRV-WindowsX64
8.1.7.000-IBM-SPSRV-Linuxx86_64
8.1.7.000-IBM-SPSRV-Linuxs390x
8.1.7.000-IBM-SPSRV-AIX
IBM Spectrum Protect Server V8.1 Fix Pack 7 (V8.1.7) Downloads
IBM Spectrum Protect Server V8.1.6.X interim fix downloads

APAR status

• Closed as program error.

Error description

• A Spectrum Protect server at 8.1.6.0 code level might crash
  due to active log files not being cleared properly, this can
  lead to a "disk full" condition and server stops.
  
  To verify you are exposed to the subject APAR you can use the
  following command to identify the first active log file in use:
  db2 get db cfg" | grep "First active"
  First active log file = S0536493.LOG
  
  If in the active log directory you find active log files that
  are older than the first active log file and if your server is
  at 8.1.6 code level the APAR is confirmed.
  
  ls -l *
  
  total 192542056
  drwxr-x---    2 tutsmg25 tsm             256 Jan 10 01:02
  LOGSTREAM0000
  -rw-------    1 tutsmg25 tsm       536879104 Oct 16 2017
  S0166157.LOG
  -rw-------    1 tutsmg25 tsm       318722048 Dec 08 00:10
  S0507460.LOG
  ..
  -rw-------    1 tutsmg25 tsm       223731712 Jan 08 00:20
  S0534711.LOG
  -rw-------    1 tutsmg25 tsm       211304448 Jan 08 10:12
  S0534908.LOG
  -rw-------    1 tutsmg25 tsm       536879104 Jan 10 10:00
  S0536493.LOG <= First active log file
  -rw-------    1 tutsmg25 tsm       536879104 Jan 10 10:03
  S0536494.LOG
  -rw-------    1 tutsmg25 tsm       536879104 Jan 10 10:05
  S0536495.LOG
  -rw-------    1 tutsmg25 tsm       536879104 Jan 10 04:00
  S0536496.LOG
  
  This symptom is caused by an exposure to the following DB2 APAR:
  IT25556: DB2 ACTIVE LOGS NOT BEING REMOVED FROM ACTIVE LOG
  DIRECTORY WHENNO LONGER NEEDED.
  http://www-01.ibm.com/support/docview.wss?crawler=1&uid=swg1IT25
  556
  
  | MDVREGR 8.1.6.0-TIV_5698MSV |
  
    IBM Spectrum Protect Versions Affected: 8.1.6.0  on AIX
    Initial Impact: Medium
    Additional Keywords: TS001765748 DB2
  

Local fix

• Monitor the active log directory and periodically clean up from
  unused active log files or set the
  DB2_USE_BUFFERED_READ_FOR_ACTIVE_LOG registry variable to NO.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IBM Spectrum Protect server users.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in levels 8.1.6.200 and 8.1.7. Note    *
  * that this is subject to change at the discretion of IBM.     *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  Affected platforms for reported release:  AIX, Linux, and
  Windows.
  Platforms fixed:  AIX, Linux, and Windows.
  

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

• R81A PSY

     UP

• R81L PSY

     UP

• R81W PSY

     UP