A fix is available
APAR status
Closed as program error.
Error description
Many threads were suspended due to a page latch on DSNDB06.SYSUSER, and -DIS THREAD command got following error. DSNT500I -D3P6 DSN9SCNP RESOURCE UNAVAILABLE REASON 00C20031 TYPE 00000300 NAME DSNDB06 .SYSUSER .X'0000000C' DSN9023I -D3P6 DSN9SCND '-DIS THD' ABNORMAL COMPLETION . A page latch on DSNDB06.SYSUSER page x'00000C' was left when a cancel happened in DSNIOST2 during create thread process.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: DB2 users. * **************************************************************** * PROBLEM DESCRIPTION: Page latch timeout, resulting in a * * "resource unavailable" with reason * * code RC00C20031. * **************************************************************** * RECOMMENDATION: * **************************************************************** Problem occurs after an agent is canceled or abended during agent initialization, while in the process of acquiring or releasing a page latch on a catalog or directory object. Page latches are normally cleaned up during begin-abort, but this is not driven for failures during allocation. The page in the buffer pool remains marked as latched, and for as long as it remains in the pool, any attempt to acquire an exclusive page latch on it will fail with RC00C20031.
Problem conclusion
The page rectify logic driven at commit or deallocate has been modified to handle page latches in the same manner as the begin- abort page latch rectify does. This will ensure that the page latch will be cleaned up for the case where begin-abort is not driven, even if the agent failed somewhere in the process of acquiring or releasing the latch.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PK59227
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2008-01-11
Closed date
2008-03-04
Last modified date
2008-04-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK34283 UK34284
Modules/Macros
DSNB1RTR
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
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:
01 April 2008