This guide walks through diagnosing OceanBase tenant memory exhaustion by tracing error codes, extracting TRACE_IDs, analyzing OBServer logs, querying virtual tables for memory allocation details, and applying a version upgrade to resolve the underlying memory leak.
The article explains how an unexpected MySQL index interaction with a BIT column and implicit type conversion caused a production outage, details the investigation steps, presents the problematic SQL and table schema, and offers a quick fix by removing the offending index.
This article details a MySQL 8.0.35 crash caused by an InnoDB assertion that a VARCHAR length exceeds 65,535 bytes, explains the error‑log and core‑dump analysis, shows how to reproduce the bug, and notes its resolution in MySQL 8.0.35.
The article explains how incorrectly placed double‑quotation marks in MySQL UPDATE statements change the intended string assignment into a boolean comparison that evaluates to 0, leading to all affected rows being updated with zero values, and shows how to detect and avoid this pitfall.
A production MySQL server suffered CPU overload and half‑hour alerts because a high‑volume query skipped a crucial composite index field, leading to full‑table scans; the post explains the root cause, the temporary index fix, the left‑most index principle, code validation oversights, and lessons learned.
A developer’s production update accidentally set every row’s source_name to 0 because misplaced double‑quotation marks altered the SQL semantics, and the article explains how MySQL interprets such malformed statements and how to recover the data.
