IC93987: (IC72213) BACKUP DB PROCESSING CAN FAIL WITH ANR2968E SQLCODE -2033 SQLERR MC 19.

IBM Tivoli Storage Manager V6.3 Fix Pack 5 (6.3.5.000) Server Downloads

APAR status

• Closed as program error.

Error description

• The problem in the APAR IC72213 was fixed in Tivoli Storage
  Manager server 6.1 and 6.2.
  However, the problem remains in Tivoli Storage Manager server
  6.3.
  This APAR is to address the problem described in the APAR
  IC72213 which was:
  
  The Tivoli Storage Manager server's BACKUP DB processing can
  fail with the following errors:
  
  ANR2968E Database backup terminated. DB2 sqlcode: -2033.
           DB2 sqlerrmc: 19. (SESSION: 30, PROCESS: 33)
  ANR0985I Process 33 for DATABASE BACKUP running in the
           BACKGROUND completed with completion state FAILURE at
           09:32:20 AM. (SESSION: 30, PROCESS: 33)
  
  These errors can only happen if the $$_TSMDBMGR_$$ node name has
  been mistakenly used with a normal backup archive client.
  
  This special node name is reserved for 6.X BACKUP DB operations
  and should only be used by the Server.
  If a mis-configured backup/archive client has mistakenly used
  this special node name, it can create an invalid filespace entry
  in the database.  This invalid filespace entry will cause BACKUP
  DB operations to fail with the above errors.
  
  It is important to note that if a backup/archive client uses
  this node name, no data will actually be sent to the Server, and
  the backup/archive operation will fail.
  Also, if a BACKUP DB operation has already successfully
  completed, this problem will not happen.
  
  Improvements will be made to prevent backup/archive clients from
  using this special node name.
  
  
  Tivoli Storage Manager Versions Affected: Tivoli Storage Manager
  server  6.3 for all platforms.
  
  
  Customer/L2 Diagnostics (If Applicable)
  If the above mentioned ANR2968E error is reported during BACKUP
  DB processing, with SQLCODE -2033 and SQLERRMC 19, issue the
  following select statement to learn more about the filespaces
  defined to the Server:
  
    tsm: SERVER1>select * from filespaces
  
  The special $$_TSMDBMGR_$$ filespace will always have a blank
  node name, similar to the following example of a "good"
  filespace entry:
  
          NODE_NAME:
     FILESPACE_NAME: /TSMDB1
       FILESPACE_ID: 888
     FILESPACE_TYPE: API:DB2/LINUXX8664
           CAPACITY: 34971.10
           PCT_UTIL: 100.00
       BACKUP_START:
         BACKUP_END:
    DELETE_OCCURRED:
  UNICODE_FILESPACE: NO
  FILESPACE_HEXNAME: 2F54534D444231
  
  An example of a "bad" filespace entry would be similar
  to the following:
  
          NODE_NAME:
     FILESPACE_NAME: /tmp
       FILESPACE_ID: 888
     FILESPACE_TYPE: EXT3
           CAPACITY: 4961.71
           PCT_UTIL: 34.13
       BACKUP_START:
         BACKUP_END:
    DELETE_OCCURRED:
  UNICODE_FILESPACE: NO
  FILESPACE_HEXNAME: 2F746D70
  
  Make special note of the FILESPACE_NAME and FILESPACE_TYPE,
  which is not valid for BACKUP DB operations.
  
  
  Initial Impact: Low
  
  
  Additional Keywords: zz63 IC72213 $$_TSMDBMGR_$$ ANR2968E
  SQLERRMC 19
  

Local fix

• The invalid filespace can be deleted manually through DB2 to
  resolve this issue.
  It is important confirm that no BACKUP DB operations have been
  successfully run on the affected server prior to completing
  these steps.
  Do not issue the following commands on a server that has
  successfully backed up the database previously.
  
  1. Login as the instance user.
  2. Issue the following command to connect to the database:
        db2 connect to tsmdb1
  3. Issue the following command to delete file "bad" filespace.
        db2 "delete from tsmdb1.filespaces where
             NODEID=1 and FSID=888"
  
  NOTE: the NODEID will always be 1, and the FSID will always be
  888 for the $$_TSMDBMGR_$$ node and filespace.
  

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

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

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP