Documentation Home
MySQL 9.3 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 40.8Mb
PDF (A4) - 40.9Mb
Man Pages (TGZ) - 261.1Kb
Man Pages (Zip) - 368.3Kb
Info (Gzip) - 4.1Mb
Info (Zip) - 4.1Mb


MySQL 9.3 Reference Manual  / ...  / The InnoDB Storage Engine  / InnoDB and Online DDL  /  Online DDL Failure Conditions

17.12.7 Online DDL Failure Conditions

The failure of an online DDL operation is typically due to one of the following conditions:

  • AnALGORITHM clause specifies an algorithm that is not compatible with the particular type of DDL operation or storage engine.

  • ALOCK clause specifies a low degree of locking (SHARED orNONE) that is not compatible with the particular type of DDL operation.

  • A timeout occurs while waiting for anexclusive lock on the table, which may be needed briefly during the initial and final phases of the DDL operation.

  • Thetmpdir orinnodb_tmpdir file system runs out of disk space, while MySQL writes temporary sort files on disk during index creation. For more information, seeSection 17.12.3, “Online DDL Space Requirements”.

  • The operation takes a long time and concurrent DML modifies the table so much that the size of the temporary online log exceeds the value of theinnodb_online_alter_log_max_size configuration option. This condition causes aDB_ONLINE_LOG_TOO_BIG error.

  • Concurrent DML makes changes to the table that are allowed with the original table definition, but not with the new one. The operation only fails at the very end, when MySQL tries to apply all the changes from concurrent DML statements. For example, you might insert duplicate values into a column while a unique index is being created, or you might insertNULL values into a column while creating aprimary key index on that column. The changes made by the concurrent DML take precedence, and theALTER TABLE operation is effectivelyrolled back.