APAR status
Closed as program error.
Error description
When reorg is running it is possible for the server to deadlock and exhibit hang behavior (client backup, migration, reclamation, etc. activity does not progress) while waiting for transactions to end in order to finish the reorg. Platforms affected: TSM 6.1, 6.2, 6.3 Initial Impact: Medium
Local fix
The likelihood of experiencing this failure can be minimized by utlizing the information in APAR IC81015 to avoid reorganization of tables and indices when they do not require it and scheduling reorganization to run when server operations which require high levels of database activity are not running at the same time. If this hang condition occurs, it can be resolved by canceling the reorg process as follows: 1. Determine the application ID of the reorganization process, by issuing the following commands in a DB2 Command Line Processor window: A. db2 connect to tsmdb1 B. db2 get snapshot for all applications >application.out 2. Examine the application.out file and find the "Most recent operation" entry like this: Most recent operation = Reorganize If that line isn't there, look for an entry like this: Application name = db2reorg 3. Scroll backwards until finding the "Application handle" entry. It will look like something like this: Application handle = NNNNN (where NNNNN is the actual application handle) Ensure that the correct application handle is found. 4. Issue the following command in the DB2 Command Line Processor Window substituting in the actual application handle in for NNNNN: db2 "force application (NNNNN)" 5. Because the nature of the command being canceled and that the DB2 FORCE APPLICATION command is asynchronous, it might take up to 30 minutes for the process to be canceled. 6. To verify that it has been canceled, issue steps 1b and 2 again. If there is no "Most recent operation" of type Reorganize message displayed, it has been canceled.
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.2.6, 6.3.3.100, and 6.3.4. * * Note * * that this is subject to change at the * * discretion of IBM. * * * * * * * **************************************************************** *
Problem conclusion
This problem was fixed. Affected platforms: AIX, HP-UX, Solaris, Linux and Windows. This new message is introduced with this APAR: ANR1880W Server transaction canceled because of a conflicting lock on table <tableName>.
Temporary fix
Comments
APAR Information
APAR number
IC81261
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
62W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-02-07
Closed date
2013-05-28
Last modified date
2013-05-28
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
R62A PSY
UP
R62H PSY
UP
R62L PSY
UP
R62S PSY
UP
R62W PSY
UP
R63A PSY
UP
R63H PSY
UP
R63L PSY
UP
R63S PSY
UP
R63W 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":"62W","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
28 May 2013