SQL0911N SQL Origin: Data OSI layer 7 · Application Last updated 18 Nov 2026

Db2 SQL0911N: The current transaction has been rolled back because of a deadlock or timeout (reason code 68)

Db2 rolled the transaction back because it hit a lock timeout (68) or a deadlock (2).

Exact message you may see SQL0911N The current transaction has been rolled back because of a deadlock or timeoutSQLCODE=-911, SQLSTATE=40001DB2 deadlock or timeout reason code 68SQL0911N reason code "68"SQLCODE: -911
Seen on: Db2 SQL

Meaning

Read the reason code: 68 = lock timeout (LOCKTIMEOUT), 2 = deadlock. Retry the transaction, keep it short, access objects in a consistent order, add indexes to reduce locked rows, and consider currently committed semantics / isolation level changes.

Common causes

  • Long transaction holding locks (reason code 68)
  • Deadlock between two applications (reason code 2)
  • Missing index causing table scans
  • LOCKTIMEOUT too low
  • Uncommitted work in another session

⚡ Quick fix

  1. Retry on SQL0911N
  2. Keep transactions short and commit sooner
  3. Find the blocker with MON_GET_LOCKS / db2pd -locks

Detailed fix by platform

Shell

  1. sql
    db2 get db cfg | grep -i locktimeout
    db2pd -db SAMPLE -locks

How to diagnose

  1. Reason code — 2 or 68?
  2. Blocker — Which app?
  3. LOCKTIMEOUT — Value?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Data. Errors that are often confused with or caused by this one (click to open):

1205 — SQL Server Msg 1205: Transaction was deadlocked on lock resources and has been chosen as the deadlock victim (SQL)12051222 — SQL Server Msg 1222: Lock request time out period exceeded (SQL)1222Deadlock — Deadlock found when trying to get lock; try restarting transaction (SQL)Deadlockfirewall — VM or service unreachable: connection timed out — no VPC firewall rule allows the ingress (implied deny) (Google Cloud / Firebase)firewallLock wait timeout — Lock wait timeout exceeded; try restarting transaction (MySQL 1205) (SQL)Lock wait timeoutORA-00060 — ORA-00060: deadlock detected while waiting for resource (SQL)ORA-00060ORA-12170 — ORA-12170: TNS:Connect timeout occurred (SQL)ORA-12170SQL0204N — Db2 SQL0204N: "SCHEMA.TABLE" is an undefined name (SQLSTATE 42704) (SQL)SQL0204NSQL0911N

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.