Direct links to fixes
APAR status
Closed as program error.
Error description
There is a small timing window when a Tivoli Storage Manager Server may crash after execution of QUERY PROCESS command against a process that has just started and still has the Process ID number equal to zero. The following errors maybe logged into the Server Activity Log some moments before the crash: for example: ANR9999D_3000086854 icQueryBackup(icback.c:668) Thread<504982>: Query backup process 205; does not match with the current backup DB process 0 Where the Query backup process matches the process id in the message that came right before this, that is: ANR2280I Full database backup started as process 205 while the current backup DB process is 0. The following core dump stack has been observed on AIX for this problem: PsAbortServer(??) at 0x100012b80 pkAbort(??) at 0x10000ba24 pkAcquireMutexTracked(??, ??, ??) at 0x100007208 procReportContext(??, ??, ??) at 0x100324ea0 OutDiagToCons(??, ??, ??, ??, ??) at 0x10001d8f4 outDiagfExt(0x3e, 0x0, 0x119116880, 0x101c88380, 0xcb, 0x0, 0x11933bd08,0x0) at 0x1000098c4 icQueryBackup(??, ??, ??, ??, ??) at 0x1006cebcc procQueryProcess(??, ??, ??, ??) at 0x100324230 AdmQueryProcess(??) at 0x100f35258 AdmCommandLocal(??, ??, ??, ??, ??) at 0x100355fd0 admCommand(??, ??, ??, ??, ??) at 0x100353f54 RunScript(??, ??, ??, ??) at 0x10035c600 DoRunScript(??) at 0x100351360 AdmCommandLocal(??, ??, ??, ??, ??) at 0x100355fd0 admCommand(??, ??, ??, ??, ??) at 0x100353f54 SmExecScheduledCommand(??) at 0x10088ebbc smScheduledConsoleSession(??) at 0x10088e880 CsRunCmdThread(??) at 0x10088ca2c StartThread(0x0) at 0x10000cadc Also the following error messages can be logged into the "dsmserv.err" file: ANR9999D Mutex acquire deadlock at process.c.1492: mutex for process.c.346 thread 504982 (tid 3c96) - mutex is owned by thread 504982 (tid 3c96) for process.c.1026, errno=45. ANR9999D Mutex acquisition failure, errno=45 from process.c.1492; thread 504982 (tid 3c96). ANR7838S Server operation terminated. This problem might happen for any Server process and will only occur in scenario when the Context Reporting is enabled ( default to ON and controlled by SET CONTEXTMESSAGING command) Tivoli Storage Manager Versions Affected: All supported versions of Tivoli Storage Manager Server Initial Impact: Medium Additional Keywords: TSM Server SP Spectrum Protect ANR9999D Mutex acquire deadlock "errno=45" ANR7838S ANR9999D_3000086854 "Q PROCESS" crash core dump
Local fix
Disable the Server Message Context Reporting by command "SET CONTEXTMESSAGING OFF"
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 7.1.5. 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.
Temporary fix
Comments
APAR Information
APAR number
IT11966
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
71A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-10-26
Closed date
2016-02-04
Last modified date
2016-02-04
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
[{"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.3"}]
Document Information
Modified date:
28 August 2023