Fixes are available
APAR status
Closed as program error.
Error description
Reclamation fails with: ANR0106E afutil.c(4283): Unexpected error 2 fetching row in table "AF.Segments". ANR9999D_1933450837 AfGetBitfileSegVolList(afutil.c:4284) Thread<234>: Row not found for bitfile 6054976. ANR9999D Thread<234> issued message 9999 from: ANR9999D Thread<234> 0x0000000100012f94 StdPutText ANR9999D Thread<234> 0x0000000100013afc OutDiagToCons ANR9999D Thread<234> 0x000000010000edbc outDiagfExt ANR9999D Thread<234> 0x00000001003bb344 AfGetBitfileSegVolList ANR9999D Thread<234> 0x00000001009642f8 CheckSpannedBitfile ANR9999D Thread<234> 0x0000000100960d3c RclmOffsiteVols ANR9999D Thread<234> 0x00000001009600a8 AfRclmVolumeThread ANR9999D Thread<234> 0x0000000100009d68 StartThread ANR9999D_3803951579 AfGetNextContents(afqry.c:903) Thread<234>: Missing row for bitfile 6054976, readWrite(No). ANR9999D Thread<234> issued message 9999 from: ANR9999D Thread<234> 0x0000000100012f94 StdPutText ANR9999D Thread<234> 0x0000000100013afc OutDiagToCons ANR9999D Thread<234> 0x000000010000edbc outDiagfExt ANR9999D Thread<234> 0x00000001006a1bb4 AfGetNextContents ANR9999D Thread<234> 0x0000000100964efc EndOffsiteRclm ANR9999D Thread<234> 0x0000000100960e44 RclmOffsiteVols ANR9999D Thread<234> 0x00000001009600a8 AfRclmVolumeThread ANR9999D Thread<234> 0x0000000100009d68 StartThread Move Data fails with: ANR9999D_3143370830 AfGetNextContents(afqry.c:899) Thread<31677>: Missing row for bitfile 0.6054976, readWrite(No). ANR9999D Thread<31677> issued message 9999 from: ANR9999D Thread<31677> 0x0000000100012d50 StdPutText ANR9999D Thread<31677> 0x000000010001387c OutDiagToCons ANR9999D Thread<31677> 0x000000010000ebdc outDiagfExt ANR9999D Thread<31677> 0x000000010051281c AfGetNextContents ANR9999D Thread<31677> 0x0000000100645d0c AfMoveData ANR9999D Thread<31677> 0x00000001002020b8 bfMoveData ANR9999D Thread<31677> 0x00000001005426b8 AdmMoveData ANR9999D Thread<31677> 0x0000000100175520 AdmCommandLocal ANR9999D Thread<31677> 0x0000000100173b8c admCommand ANR9999D Thread<31677> 0x000000010017ae60 RunScript ANR9999D Thread<31677> 0x0000000100171834 DoRunScript ANR9999D Thread<31677> 0x0000000100175520 AdmCommandLocal ANR9999D Thread<31677> 0x0000000100173b8c admCommand ANR9999D Thread<31677> 0x000000010017ae60 RunScript ANR9999D Thread<31677> 0x0000000100171834 DoRunScript ANR9999D Thread<31677> 0x0000000100175520 AdmCommandLocal ANR9999D Thread<31677> 0x0000000100173b8c admCommand ANR9999D Thread<31677> 0x00000001005f42b8 SmExecScheduledCommand ANR9999D Thread<31677> 0x00000001005f3f78 smScheduledConsoleSession ANR9999D Thread<31677> 0x00000001005f35b0 CsRunCmdThread ANR9999D Thread<31677> 0x0000000100009bb4 StartThread ANR2209W Volume vol_name contains no data. Customer/L2 Diagnostics: Get the following on the failing bitfile (Above message examples are bitfile: 6054976) show bfo 6054976 show invo 6054976 show aggr 0 6054976 All show commands return: Bitfile Object NOT found. Or Bitfile 6054976 is not an aggregate. From AIX, login as the instance owner and do: db2 connect to tsmdb1 db2 set schema tsmdb1 db2 "select * from TSMDB1.af_vol_segments where bfid=6054976" > avsg.txt db2 "select * from TSMDB1.af_segments where bfid=6054976" > afsg.txt db2 "select * from TSMDB1.AF_Bitfiles where bfid=6054976" > afbf.txt Example of output: avsg.txt: VOLID START OFFSET POOLID SRVID BFID SEGNUM SEGSIZE ----------- ----------- ----------- ----------- ----------- -------------------- ----------- -------------------- 552 1 0 -1 0 6054976 1 7288298 1 record(s) selected. afsg.txt POOLID SRVID BFID SEGNUM VOLID START OFFSET SEGSIZE ----------- ----------- -------------------- ----------- ----------- ----------- ----------- -------------------- -1 0 6054976 1 552 1 0 7288298 1 record(s) selected. afbf.txt SRVID BFID POOLID CK1 CK2 FORMAT SIZE NUMSEGS LASTRTRV FLAGS ----------- -------------------- ----------- ----------- ----------- ----------- -------------------- ----------- -------------------------- ------ 0 record(s) selected. Initial Impact: Medium Additional Keywords: TSM
Local fix
Contact support to assist in deleting the orphaned object. Get to fixing level when available. Update STGPool RECLAIMPRocess=1 So new orphans are not created
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 5.5.6, 6.1.4, and 6.2.1. * * Note that this is subject to change at the * * discretion of IBM. * **************************************************************** See ERROR DESCRIPTION.
Problem conclusion
The described problem has been resolved.
Temporary fix
Comments
APAR Information
APAR number
IC68245
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-04-28
Closed date
2010-05-18
Last modified date
2011-05-09
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
[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"61A"}]
Document Information
Modified date:
16 September 2021