APAR status
Closed as program error.
Error description
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. . Customer/L2 Diagnostics: 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: Medium. . Tivoli Storage Manager Versions Affected: All 6.1 and 6.2 Tivoli Storage Manager Servers. . Additional Keywords: ZZ61 ZZ62 TSM DB BACKUP DB SQL SQLC $$_TSMDBMGR_$$ BU BACK UP DATABASE DATA BASE MSGANR2968E MSGANR0985I .
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 levels 6.1.5 and 6.2.3. Note that this is * * * * subject to change at the discretion of IBM. * **************************************************************** *
Problem conclusion
This problem was fixed. Affected platforms: AIX, HP-UX, Sun Solaris, Linux and Windows.
Temporary fix
Comments
APAR Information
APAR number
IC72213
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
62L
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-10-26
Closed date
2010-12-20
Last modified date
2011-01-18
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
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"62L","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
18 January 2011