APAR status
Closed as unreproducible.
Error description
The TSM 6.1.0 server can crash after running normally for some period of time. The time period can vary, depending on load, from days to possibly weeks. The cause is that the TSM database is attempting to exceed the system limitation for maximum number of semaphore arrays, message queues, or application support layer heap. - The problem is that a system memory resource is not being released as appropriate. - TSM Versions Affected: TSM 6.1.0 servers on all platforms - Customer/L2 Diagnostics: Upon restart of the TSM server after the crash, the activity log may have these messages: - ANR0171I dbieval.c(779): Error detected on 0:12, database in evaluation mode. ANR0169E An unexpected error has occurred and the TSM server is stopping. ANR0162W Supplemental database diagnostic information: -1:57049:-1225 ([IBM][CLI Driver] SQL1225N The request failed because an operating system process, thread, or swap space limit was reached. SQLSTATE=57049 - This ANR9999D message may also occur: ANR9999D_3831306406 ReportSQLDiagInfo(dbieval.c:1157) Thread<50>: Missing sqlState=58005, sqlCode=-902 from table. Returning rc = 2158. - This message occurred on an HP-UX system with the problem: ANR0163E dbieval.c(816): Database insufficient memory detected on 0:2255. ANR0162W Supplemental database diagnostic information: -1:57011:-1221 ([IBM][CLI Driver] SQL1221N The Application Support Layer heap cannot be allocated. SQLSTATE=57011). - Messages may vary, but will indicate that a system resource limit has been reached. - If required, TSM support can provide additional diagnostics to help determine if this problem exists. - Note that the TSM server may crash with similar messages due to misconfiguration or a configuration which is not sufficient for it's workload. This type of crash would not be solved by the fix for this apar. - Initial Impact: High - Additional Keywords: MSGANR0162W MSGANR9999D MSGANR0169E MSGANR0163E zz61 tsm61 crash abend restart 52005
Local fix
Restart the TSM server periodically. Restarting the TSM server after the crash will resume normal operation, no other action is necessary. Install fixing maintenance when available.
Problem summary
**************************************************************** * USERS AFFECTED: Users of Tivoli Storage Manager server V6.1. * **************************************************************** * PROBLEM DESCRIPTION: See ERROR Description. * **************************************************************** * RECOMMENDATION: * **************************************************************** Apply the level containing this fix. This problem is fixed in level 6.1.1.0.
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
IC61067
Reported component name
TSM CLIENT
Reported component ID
5698ISMCL
Reported release
61L
Status
CLOSED UR5
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-07
Closed date
2009-05-19
Last modified date
2009-05-19
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"61L","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
19 May 2009