Fixes are available
APAR status
Closed as program error.
Error description
The STMM is the first application to connect to the database. STMM is incorrectly being shown as the oldest active transaction. The actual application which is the oldest active transaction is not shown. If you find the db2stmm holding the oldest transaction. you probably hit this APAR. snippet of db snapshot: ------------------------------------------ Appl id holding the oldest transaction = 21 Log to be redone for recovery (Bytes) = 4944153561 Log accounted for by dirty pages (Bytes) = 4944153561 the appl id holding the oldest transaction always the 21 from the snapshot of applications Application handle = 21 Application status = Connect Completed Status change time = 10/26/2008 15:06:53.080647 Application code page = 819 Application country/region code = 0 DUOW correlation token = *LOCAL.DB2.081026190653 Application name = db2stmm Application ID = *LOCAL.DB2.081026190653 Sequence number = 00001 TP Monitor client user ID = TP Monitor client workstation name = TP Monitor client application name = TP Monitor client accounting string = Connection request start timestamp = 10/26/2008 15:06:53.079996 Connect request completion timestamp = 10/26/2008 15:06:53.080646 Application idle time = 1 day 15 hours 29 minutes 9 seconds ----------------------------------------------------------
Local fix
No known work around
Problem summary
The STMM is the first application to connect to the database. STMM is incorrectly being shown as the oldest active transaction. The actual application which is the oldest active transaction is not shown. If you find the db2stmm holding the oldest transaction. you probably hit this APAR. snippet of db snapshot: ------------------------------------------ Appl id holding the oldest transaction = 21 Log to be redone for recovery (Bytes) = 4944153561 Log accounted for by dirty pages (Bytes) = 4944153561 the appl id holding the oldest transaction always the 21 from the snapshot of applications Application handle = 21 Application status = Connect Completed Status change time = 10/26/2008 15:06:53.080647 Application code page = 819 Application country/region code = 0 DUOW correlation token = *LOCAL.DB2.081026190653 Application name = db2stmm Application ID = *LOCAL.DB2.081026190653 Sequence number = 00001 TP Monitor client user ID = TP Monitor client workstation name = TP Monitor client application name = TP Monitor client accounting string = Connection request start timestamp = 10/26/2008 15:06:53.079996 Connect request completion timestamp = 10/26/2008 15:06:53.080646 Application idle time = 1 day 15 hours 29 minutes 9 seconds ----------------------------------------------------------
Problem conclusion
This APAR is first fixed on the DB2 v9.1Fixpak10
Temporary fix
Comments
APAR Information
APAR number
LI74141
Reported component name
DB2 EDE LINUX
Reported component ID
5724N7604
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-01-22
Closed date
2011-06-14
Last modified date
2011-06-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
LI74142
Fix information
Fixed component name
DB2 EDE LINUX
Fixed component ID
5724N7604
Applicable component levels
R910 PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
17 October 2021