My Oracle Support Banner

How To Interpret "LATEST DETECTED DEADLOCK" Section In "SHOW ENGINE INNODB STATUS" (Doc ID 2967129.1)

Last updated on AUGUST 24, 2023

Applies to:

MySQL Server - Version 5.5 and later
Information in this document applies to any platform.

Goal

This document describes how to interpret the content of LATEST DETECTED DEADLOCK section in SHOW ENGINE INNODB STATUS command output. A deadlock is a common problem which can happen on various relational database management systems. So does it on InnoDB. The LATEST DETECTED DEADLOCK section in SHOW ENGINE INNODB STATUS command is useful when investigating deadlocks. However, the section is a bit difficult to interpret, and understand. It is necessary to interpret the content of LATEST DETECTED DEADLOCK section in SHOW ENGINE INNODB STATUS command correctly to investigate deadlocks.
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 Example Output
 Steps To Repeat The Example
 Details Of Each Part Of LATEST DETECTED DEADLOCK Section
 Timestamp
 Transaction Metadata
 Locks Held By The Transaction
 Locks The Transaction Is Waiting For
 InnoDB's Decision
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.