Resolving DB2 SQLCODE -911 (Reason 00C90088 / Deadlock) and -904 Resource Unavailable
DB2 SQLCODE -911 indicates your unit of work was rolled back due to a deadlock (Reason 00C90088) or lock timeout (Reason 00C9008E). SQLCODE -904 indicates an unavailable resource (tablespace locked, thread limit exceeded). Discover root causes and concurrency tuning.
1 Incident Symptoms: What Triggers Resolving DB2 SQLCODE -911 (Reason 00C90088 / Deadlock) and -904 Resource Unavailable?
2 Technical Root Cause & Architecture Mechanics
3 Step-by-Step Diagnostic & Code Resolution
Diagnostic Reference Matrix
| Attribute | Diagnostic Specification |
|---|---|
| Target Subsystem | IBM z/OS 2.4 - 3.1 • DB2 SQL & Performance |
| Error Signature | DB2, SQLCODE -911, SQLCODE -904 |
| Resolution SLA | < 15 Minutes via Verified StackMF Runbook |
| Technical Reviewer | Anshu, Chief Technology Architect • StackMF Architecture Pod |
Architectural Prevention & Performance Tuning Checklist
- Bind all read-heavy queries with `CONCURRENTACCESSRESOLUTION(USECURRENTLYCOMMITTED)` to eliminate reader-writer contention.
- Always update tables in a uniform alphabetical and key order across all application components.
- Tune DSNZPARM `IRLMRWT` (Resource Wait Time) and `DEADLOK` sweep frequencies appropriately.
- Ensure batch programs commit every 500 to 2,000 updates to release row/page locks.
? Frequently Asked Questions
What is the root cause of Resolving DB2 SQLCODE -911 (Reason 00C90088 / Deadlock) and -904 Resource Unavailable? ↓
How do you resolve Resolving DB2 SQLCODE -911 (Reason 00C90088 / Deadlock) and -904 Resource Unavailable in production? ↓
How can teams prevent Resolving DB2 SQLCODE -911 (Reason 00C90088 / Deadlock) and -904 Resource Unavailable in enterprise pipelines? ↓
Recommended Technical Runbooks
DB2 z/OS Query Optimization: Converting Stage 2 (Residual) into Stage 1 (Indexable) Predicates
How Outdated RUNSTATS Cause Catastrophic Tablespace Scans in DB2 for z/OS
Preventing DB2 Lock Escalation: Tuning LOCKSIZE, Isolation Levels, and SKIP LOCKED DATA
Authoritative Reference Documentation
Official IBM manuals, Redbooks, and vendor technical advisories:
This diagnostic runbook is published by StackMF Technologies LLP for educational and architectural reference only. All code snippets, JCL, and procedures are provided "AS IS" without warranty of any kind. Always test changes thoroughly in non-production sysplex environments prior to production rollout.
IBM, z/OS, CICS, Db2, IMS, RACF, and IDz are registered trademarks of International Business Machines Corporation. Broadcom, CA-7, and Endevor are trademarks of Broadcom Inc. All other trademarks belong to their respective owners and are referenced under the Nominative Fair Use Doctrine (US Lanham Act 15 U.S.C. ยง 1125 / Section 30 of the Indian Trade Marks Act, 1999) solely for technology compatibility and diagnostic identification. StackMF Technologies LLP is an independent consulting entity not affiliated with or endorsed by these vendors. View Full Legal & IP Policy →
Struggling with Critical Mainframe Incidents or Vendor Renewal Pressure?
StackMF deploys certified Senior Mainframe Engineers fluent in both z/OS legacy internals (COBOL, DB2, CICS, VSAM, CA-7, Endevor) and modern cloud stacks (React, Kafka, AWS, Git). Onboard dedicated pods in 48 hours or cut Broadcom licensing by 60%.