A fix is available
APAR status
Closed as program error.
Error description
Customer was running a stored procedure and after a period of time, they started receiving S04E abends with reasons codes like RC00E20015 and RC00E20016 indicating a storage constraint. Customer took console dumps and they were inspected and found to have large sections of memory allocated which had eyecatchers of SPCT throughout. An SPCT control block tracks a stored procedure, and there is only supposed to be one of these blocks for every stored procedure. However, during investigation, we found a leak where these control blocks were not being freed. Keywords: DB2STGLK/K
Local fix
When calling a stored procedure, use the fully qualified schema name of the stored procedure to avoid this storage leak.
Problem summary
**************************************************************** * USERS AFFECTED: ALL DB2 810, DB2 9 and DB2 10 for z/OS users * * of CALL statement. * **************************************************************** * PROBLEM DESCRIPTION: Memory leak of a DB2 internal * * structure could occur for CALL * * statements when the CALL statement is * * CALL unqualified procedure name. * **************************************************************** * RECOMMENDATION: * **************************************************************** Memory leak of a DB2 internal structure could occur for a CALL statement when the CALL statement is CALL unqualified procedure name. For this issue to manifest itself, more than one stored procedure with the same name under different schemas must exist. The following scenario illustrates how one could recreate the memory leak . 1.Stored procedures USR01.STP1 and USR02.STP1 created. 2.USRT001 is granted execute auth for USR02.STP1. 3.USRT001 running the SQL SET CURRENT PATH = USR01,USR02; and followed by CALL STP1; (with USRT001) will cause internal structure for USR01.STP1 to be orphaned.
Problem conclusion
DB2 is updated to handle the CALL unqualified procedure name statement correctly to avoid the memory leak. Additional Keywords: SQLCALL SQLSP SQLSTOREDPROC
Temporary fix
Comments
APAR Information
APAR number
PM67049
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-06-18
Closed date
2012-08-06
Last modified date
2012-09-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK80881 UK80882 UK80883
Modules/Macros
DSNXOSTP
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RA10 PSY UK80881
UP12/08/22 P F208
R810 PSY UK80882
UP12/08/22 P F208
R910 PSY UK80883
UP12/08/22 P F208
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
05 September 2012