critical
confirmed
oxmysql / database · AGN-KB-DB-0001
oxmysql: table does not exist (ER_NO_SUCH_TABLE)
The message
ER_NO_SUCH_TABLE
An AGN feature is missing part of its database. Staff have to fix it; nothing on your side is involved.
What you see
- A whole feature fails for everyone immediately after a deploy
- The server console repeats the same error
What usually causes it
- The resource's SQL migration was never run on this server
- The migration ran on Dev but not on Main (or the reverse)
- A migration written with MariaDB-only syntax silently created nothing usable on a MySQL server
Worth checking first
- Confirm which server (Main or Dev) and which database
- Check whether the table exists at all, and whether it has columns
- Check the migration file for MariaDB-only clauses
Safe steps, one at a time
- Player-side: nothing; report it
- Staff: run the resource's migration against the correct database
- Staff: an `ADD COLUMN IF NOT EXISTS` migration is MariaDB-only — on MySQL 8 it can leave a table created with no columns. Use the portable guarded pattern
These are suggestions, not instructions. Do only what you are comfortable with, back up anything important first, and stop if a step does not match what is on your screen. Advice, risk and responsibility.
When to stop and ask staff
Always staff, immediately — this is server-wide.
Looks like
AGN server
What staff will need
- Exact error with table name
- Server (Main/Dev)
- Resource and version
- When it was deployed
Applies to
MariaDB 10.4 on this box; migrations must stay portable.
Last reviewed Fri Sep 18.