IT02910: DB2 HISTORY FILE DOES NOT GET PRUNED WHEN USING DEFAULT SERVER 7.1 BACKUP DATABASE CONFIGURATION

APAR status

• Closed as program error.

Error description

• Following successful backup of the 7.1 server's database, the
  DB2 History file does not get pruned. and
  DB2 diagnostic log shows  "SQL2062N" and "ADM8507N" rc 137
  errors.
  
  Example of the error sequence in db2diag.X.log is:
  
  2014-04-28-01.17.28.383406+240 E17211801A554        LEVEL: Error
  PID     : 22872106             TID : 25441          PROC :
  db2sysc 0
  INSTANCE: tsminst1             NODE : 000           DB   :
  TSMDB1
  APPHDL  : 0-40619              APPID:
  *LOCAL.tsminst1.140427204031
  AUTHID  : TSMINST1             HOSTNAME: host_name
  EDUID   : 25441                EDUNAME: db2agent (TSMDB1) 0
  FUNCTION: DB2 UDB, database utilities,
  sqluhPruneHistoryDeleteFile,
  probe:1641
  MESSAGE : ADM8507N  Unable to delete the backup image with
  timestamp
            "20140427060020".
  
  2014-04-28-01.17.34.377075+240 E17212356A371        LEVEL: Error
  PID     : 16973914             TID : 1              PROC :
  db2vend
  INSTANCE: tsminst1             NODE : 000
  HOSTNAME: host_name
  EDUID   : 1
  FUNCTION: DB2 UDB, database utilities, sqluvdel, probe:1407
  DATA #1 : TSM RC, PD_DB2_TYPE_TSM_RC, 4 bytes
  TSM RC=0x00000089=137 -- see TSM API Reference for meaning.
  
  2014-04-28-01.17.34.378136+240 E17212728A980        LEVEL: Error
  PID     : 22872106             TID : 25441          PROC :
  db2sysc 0
  INSTANCE: tsminst1             NODE : 000           DB   :
  TSMDB1
  APPHDL  : 0-40619              APPID:
  *LOCAL.tsminst1.140427204031
  AUTHID  : TSMINST1             HOSTNAME: host_name
  EDUID   : 25441                EDUNAME: db2agent (TSMDB1) 0
  FUNCTION: DB2 UDB, database utilities, sqluhVendorDelete,
  probe:1373
  MESSAGE : SQL2062N  An error occurred while accessing media "".
  Reason
  code:
            "".
  DATA #1 : String, 32 bytes
  Error returned by vendor delete.
  DATA #2 : Vendor RC, PD_DB2_TYPE_VENDOR_RC, 4 bytes
  Vendor RC=0x0000001A=26 -- see DB2 API Guide for meaning.
  DATA #3 : Hexdump, 48 bytes
  0x0A000200240296F0 : 0000 0089 3134 3037 2031 3337 0000 0000
  ....
  1407 137....
  0x0A00020024029700 : 0000 0000 0000 0000 0000 0000 0000 0000
  ................
  0x0A00020024029710 : 0000 0000 0000 0000 0000 0000 0000 0000
  ................
  
  
  
  For server 6.x, the "BACKUP DB" configuration required
  administrators to configure the Tivoli Storage Manager API (that
  was used by DB2) to use the "passwordaccess generate"
  configuration and to use the dsmsutil utility to configure /
  save the password that was used for DB2.
  In server 7.1, "BACKUP DB" was changed so that the
  "passwordaccess generate" configuration was no longer needed.
  
  When the password HAS been generated (as it is when configured
  for backup in server 6.3.x or when the existing 7.1 server has
  been upgraded from  6.3.x), the Tivoli Storage Manager API logs
  do not show ANY "rc = 137" entries.
  When the password has NOT been generated (as when using the
  default configuration for a new 7.1 installation), the db2diag
  logs show messages "SQL2062N" and "ADM8507N" rc 137
  (Session rejected: Authentication failure) for the DB2 calls
  that do not contain the password. These messages are harmless
  and can be ignored.
  
  The growth in dthe b2 history file can cause "backup db" process
  to extend in duration.
  
  Tivoli Storage Manager versions affected:
  Server 7.1 on all platforms
  
  Initial Impact: Low
  
  Additional Keywords:
  zz71 tsm db backup database dbb history prune db2
  

Local fix

• A temporary solution for the growth in the DB2 History file is
  to use the DB2 "PRUNE HISTORY" command.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Tivoli Storage Manager Server 7.1.0 users of BACKUP DB   *
  * who do not have "passwordaccess generate" configured via a   *
  * previous release of Tivoli Storage Manager                   *
  ****************************************************************
  * 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                   *
  ****************************************************************
  The fix for this APAR prunes the DB2 history file, however it
  cannot prevent DB2 from logging the "SQL2062N" and "ADM8507N"
  errors in the db2diag.<n>.log file.
  The db2diag "SQL2062N" and "ADM8507N" messages are harmless and
  can be ignored.
  

Problem conclusion

• This problem was fixed.
  Affected platforms: AIX, HP-UX, Solaris, 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

• R71A PSY

     UP

• R71H PSY

     UP

• R71L PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP