Cannot upgrade due to full table in MySQL
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
問題
When upgrading Confluence, an error occurs which keeps the process from completing. An error similar to the following is seen in atlassian-confluence.log
The following example is specific to the BODYCONTENT table but could occur for any table of the Confluence database
2013-04-29 16:34:42,712 ERROR [main] [hibernate.tool.hbm2ddl.SchemaUpdate] execute Unsuccessful: alter table BODYCONTENT add
column BODYTYPEID smallint
2013-04-29 16:34:42,713 ERROR [main] [hibernate.tool.hbm2ddl.SchemaUpdate] execute The table '#sql-1b3f_61186' is full
2013-04-29 16:34:42,715 ERROR [main] [hibernate.tool.hbm2ddl.SchemaUpdate] execute could not complete schema update
java.sql.SQLException: The table '#sql-1b3f_61186' is full
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1072)原因
The underlining MySQL database table is full and will not allow anymore entries. There are a number of reasons why this could occur, all of which lay on the database and not Confluence.
ソリューション
For more details on why the table is full and ways to increase the table size, please see the MySQL documentation found here.