Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps (http://ibm.biz/Data-and-AI-Roadmaps) - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at https://hybridcloudunit-internal.ideas.aha.io/


Status Under review
Workspace Db2 for z/OS
Created by Guest
Created on Nov 30, 2022

Return information about a failed Lock-Escalation to the application

When a Lock-Escalation occurs it is documented by message DSNI031I (Lock Escalation has occurred) in the Db2-Master-Adressspace. But when a Lock-Escalation fails there is no documentation for this, instead it comes to a Timeout or Deadlock from a lock-change-request with Resource-Type 00000210 (Partition) and Resource-Name is the Tablespace-Partition that looks like this:


01.34.22 S0103665 DSNT375I <DBR2 PLAN=DISTSERV WITH 492

492 CORRELATION-ID=db2jcc_appli

492 CONNECTION-ID=SERVER

492 LUW-ID=G4EF5B19.MC1C.DC7B58B5C42B=57458

492

492 THREAD-INFO=Q100494:OSPE_LOCALHOST_6:421_Q100107:aspm.REORG_DATA:STAT

492 IC:259376357:*:<::4.239.91.25.22776.DC7B568542C9>

492 IS DEADLOCKED WITH PLAN=GK000421 WITH

492 CORRELATION-ID=POOLP98W0007

492 CONNECTION-ID=PRCICD0Z

492 LUW-ID=DESIKVE0.PRDBR300.DC7B58C47F53=23017

492 THREAD-INFO=Q100002:*:*:POOLP98W:STATIC:259466942:*:*

492 ON MEMBER DBR3

01.34.22 S0103665 DSNT501I <DBR2 DSNILMCL RESOURCE UNAVAILABLE 493

493 CORRELATION-ID=db2jcc_appli

493 CONNECTION-ID=SERVER

493 LUW-ID=G4EF5B19.MC1C.DC7B58B5C42B=57458

493 REASON 00C90088

493 TYPE 00000210

493 NAME MK400421.TSMK4000.00000001


The SQL ends with SQL-Code -911/-913 (Timeout or Deadlock), which means for many developers that they have a concurrency-problem with other applications, but they don’t see that the reason for this problem comes from too many changes within a single unit of work which leads to a lock-escalation. In the case above the application gets:


DSNT408I SQLCODE = -913, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY

DEADLOCK OR TIMEOUT. REASON CODE 00C90088, TYPE OF RESOURCE

00000210, AND RESOURCE NAME MK400421.TSMK4000.00000001

DSNT418I SQLSTATE = 57033 SQLSTATE RETURN CODE

DSNT415I SQLERRP = DSNXRRC SQL PROCEDURE DETECTING ERROR

DSNT416I SQLERRD = 112 13172746 13172872 13226962 -975040510

536870912 SQL DIAGNOSTIC INFORMATION

DSNT416I SQLERRD = X'00000070' X'00C9000A' X'00C90088' X'00C9D3D2'

X'C5E21002' X'20000000' SQL DIAGNOSTIC INFORMATION


Suggestion: In case of an unsuccessful Lock-Escalation please return an SQL-Code -904, instead of -911/-913, with a Reason-Code that shows that this is a failed Lock-Escalation and return the Tablespace-Name in the message-text.

Alternativly if you don't want to change the SQL-Code, please return a Reason-Code that shows the failed Lock-Escalation.


Needed By Not sure -- Just thought it was cool