EC
1683
MySQLERRORNotableInnoDBMEDIUM confidence

InnoDB full-text auxiliary table name does not contain a hex table ID

Production Risk

Medium — full-text searches on the affected table may fail.

What this means

InnoDB encountered an auxiliary full-text index table whose name does not follow the expected hex-ID naming convention, indicating possible corruption or manual rename.

Why it happens
  1. 1Auxiliary FTS tables were manually renamed.
  2. 2Database restored from a partial or incompatible backup.
How to reproduce
trigger — this will error
trigger — this will error
-- Occurs internally; triggered during FTS index operations on a corrupted table.

expected output

ERROR 1683 (HY000): InnoDB: FTS auxiliary table name does not contain a hex table id.

Fix

Drop and recreate the full-text index

Drop and recreate the full-text index
ALTER TABLE t DROP INDEX ft_idx;
ALTER TABLE t ADD FULLTEXT INDEX ft_idx (col);

Why this works

Recreating the index regenerates correctly-named auxiliary tables.

What not to do

✕

Sources
Official documentation ↗

MySQL 8.0 — 1683 ER_INNODB_FT_AUX_NOT_HEX_ID

Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev

← All MySQL errors