A fix is available
APAR status
Closed as program error.
Error description
The active log can fill, if db2reorg activity is stuck in LOCKWAIT,during table reorganisation and other server processes and client sessions continue causing active log space to be used. The consequence of this, is that, it can fill to 100% and DB2 will stop. db2diag.log will report similar to; 2012-04-24-12.59.57.462000+000 E6540760F604 LEVEL: Error PID : 5080 TID : 4020 PROC : db2syscs.exe INSTANCE: SERVER1 NODE : 000 DB : TSMDB1 APPHDL : 0-40973 APPID: *LOCAL.SERVER1.120425024328 AUTHID : X-SVC-TSMDB EDUID : 4020 EDUNAME: db2agent (TSMDB1) FUNCTION: DB2 UDB, data protection services, sqlpgResSpace, probe:2860 MESSAGE : ADM1823E The active log is full and is held by application handle "36105..". Terminate this application by COMMIT, ROLLBACK or FORCE APPLICATION. 2012-04-24-12.59.57.478000+000 I6541366F564 LEVEL: Error PID : 5080 TID : 4020 PROC : db2syscs.exe INSTANCE: SERVER1 NODE : 000 DB : TSMDB1 APPHDL : 0-40973 APPID: *LOCAL.SERVER1.120425024328 AUTHID : X-SVC-TSMDB EDUID : 4020 EDUNAME: db2agent (TSMDB1) FUNCTION: DB2 UDB, data protection services, sqlpWriteLR, probe:6680 MESSAGE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE "Log File has reached its saturation point" DIA8309C Log file was full. Customer/L2 Diagnostics: If the db2reorg is in a LOCKWAIT state, and stays in that state for an hour, you are probably experiencing this APAR. Method to check this is; 1) db2 connect to tsmdb1 2) See if db2reorg is stuck in LOCKWAIT by issuing the following command: db2 "select agent_id from sysibmadm.applications where appl_name='db2reorg' and appl_status='LOCKWAIT' " If the reorganization is in LOCKWAIT, a row will be returned from the SELECT like the following: AGENT_ID -------------------- 53643 Note that the AGENT_ID number will probably be different on your system. If you issue this select periodically over a period of an hour, and it remains in LOCKWAIT and the returned AGENT_ID is the same, you are experiencing the APAR. Tivoli Storage Manager Versions Affected: All Tivoli Storage Manager Server Versions: 6.2 and 6.3 Initial Impact: Medium Additional Keywords: TSM zz62 zz63 81005 reorg db2reog activelog filling full
Local fix
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.10, 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.
Temporary fix
Comments
APAR Information
APAR number
IC83725
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
63W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-05-24
Closed date
2013-02-11
Last modified date
2013-02-11
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
[{"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":"63W"}]
Document Information
Modified date:
19 September 2021