# Problem with update (database migration) to version 6.3.0.0

**URL:** <https://forum.shopware.com/t/problem-with-update-database-migration-to-version-6-3-0-0/88776>\
**Category:** Shopware 6 (English)\
**Tags:** general, administration, programming\
**Created:** [2. Juli 2021 um 11:23 UTC](https://forum.shopware.com/t/problem-with-update-database-migration-to-version-6-3-0-0/88776 "2021-07-02T11:23:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jacek.balczewski](https://avatars.discourse-cdn.com/v4/letter/j/ea5d25/32.png) [@jacek.balczewski](https://forum.shopware.com/u/jacek.balczewski)\
**Post date:** [2. Juli 2021 um 11:23 UTC](https://forum.shopware.com/t/problem-with-update-database-migration-to-version-6-3-0-0/88776/1 "2021-07-02T11:23:50Z")

</div>

Hello,  
I get the following error when updating shopware to version 6.3.0.0

Error  
Received the following error message:  
An exception occurred while executing ’ CREATE TABLE `language` ( `id` BINARY(16) NOT NULL, `name` VARCHAR(50) COLLATE utf8mb4\_unicode\_ci NOT NULL, `parent_id` BINARY(16) NULL, `locale_id` BINARY(16) NOT NULL, `translation_code_id` BINARY(16) NULL, `custom_fields` JSON NULL, `created_at` DATETIME(3) NOT NULL, `updated_at` DATETIME(3) NULL, PRIMARY KEY (`id`), UNIQUE `uniq.translation_code_id` (translation\_code\_id), KEY `idx.language.translation_code_id` (`translation_code_id`), KEY `idx.language.language_id_parent_language_id` (`id`, `parent_id`), CONSTRAINT `json.language.custom_fields` CHECK (JSON\_VALID(`custom_fields`)), CONSTRAINT `fk.language.parent_id` FOREIGN KEY (`parent_id`) REFERENCES `language` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4\_unicode\_ci; ': SQLSTATE[42S01]: Base table or view already exists: 1050 Table ‚language‘ already exists

Please try to fix this error and restart the update.  
Response  
{„valid“:false,„errorMsg“:„An exception occurred while executing '\n CREATE TABLE `language` (\n `id` BINARY(16) NOT NULL,\n `name` VARCHAR(50) COLLATE utf8mb4\_unicode\_ci NOT NULL,\n `parent_id` BINARY(16) NULL,\n `locale_id` BINARY(16) NOT NULL,\n `translation_code_id` BINARY(16) NULL,\n `custom_fields` JSON NULL,\n `created_at` DATETIME(3) NOT NULL,\n `updated_at` DATETIME(3) NULL,\n PRIMARY KEY (`id`),\n UNIQUE `uniq.translation_code_id` (translation\_code\_id),\n KEY `idx.language.translation_code_id` (`translation_code_id`),\n KEY `idx.language.language_id_parent_language_id` (`id`, `parent_id`),\n CONSTRAINT `json.language.custom_fields` CHECK (JSON\_VALID(`custom_fields`)),\n CONSTRAINT `fk.language.parent_id` FOREIGN KEY (`parent_id`)\n REFERENCES `language` (`id`) ON DELETE CASCADE ON UPDATE CASCADE\n ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4\_unicode\_ci;\n ':\n\nSQLSTATE[42S01]: Base table or view already exists: 1050 Table ‚language‘ already exists“}

Removing the „language“ table from the database does not help (information appears that the ‚locale‘ table exists, after removing it, the error informs that the language table does not exist …).  
An attempt was made to set a parameter ‚log\_bin\_trust\_function\_creators = ON‘, but nothing helps. All plugins were disabled prior to update.