// MySQL error reference

MySQL error 1114: The table is full

MySQL couldn't add rows to a table: the disk or tablespace is full, or an in-memory or temporary table hit its size limit.

Error number
1114
Name
ER_RECORD_FILE_FULL
SQLSTATE
HY000
Category
Server limits and settings
Error message
The table '%s' is full

What it means

1114 means the storage behind the table can't grow. For InnoDB that's usually the disk or a fixed-size tablespace; for MEMORY tables it's max_heap_table_size; and for internal temporary tables built during big GROUP BY or ORDER BY queries it can be the temporary storage limit. The server error log usually says which.

Common causes

  • The disk holding the data directory (or tmpdir) is full.
  • An InnoDB system or shared tablespace with a maximum size (innodb_data_file_path without autoextend, or with max).
  • A MEMORY table larger than max_heap_table_size.
  • A large query whose internal temporary table exceeds its limit, such as temptable_max_ram and temptable_max_mmap in MySQL 8.0.

How to fix it

  1. Check free disk space on the data and temporary directories, and the server error log.

  2. Check the settings that cap table sizes.

    SHOW VARIABLES WHERE Variable_name IN ('innodb_data_file_path', 'max_heap_table_size', 'tmp_table_size', 'tmpdir');
  3. Free or add disk space, and let the tablespace autoextend. For MEMORY tables, raise the limit for the session and recreate the table.

    SET SESSION max_heap_table_size = 512 * 1024 * 1024;

Related errors

More server limits and settings errors

The code and message text are from the MySQL 8.4 Error Message Reference. Browse the full MySQL error list or search every database error.

// fewer errors, faster fixes

Work on MySQL in SQLly

A native SQL client for macOS, Windows and Linux with schema-aware IntelliSense, guardrails for risky statements and clear error messages, for MySQL and the other databases you use.