# Database restore errors Dolibarr 20.0.3 / Ubuntu 24 / MyPHPAdmin

**URL:** <https://www.dolibarr.org/forum/t/database-restore-errors-dolibarr-20-0-3-ubuntu-24-myphpadmin/30386>\
**Category:** Maintaining my Dolibarr\
**Tags:** Help, Linux, Issue\
**Created:** [May 29, 2025, 3:16pm UTC](https://www.dolibarr.org/forum/t/database-restore-errors-dolibarr-20-0-3-ubuntu-24-myphpadmin/30386 "2025-05-29T15:16:46Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![RSAutomation](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/r/47e85d/32.png) [@RSAutomation](https://www.dolibarr.org/forum/u/RSAutomation)\
**Post date:** [May 29, 2025, 3:16pm UTC](https://www.dolibarr.org/forum/t/database-restore-errors-dolibarr-20-0-3-ubuntu-24-myphpadmin/30386/1 "2025-05-29T15:16:46Z")

</div>

Moving Dolibarr from DoliWamp (Windows) based system to Ubuntu (Linux) workstation. I have been unable to restore the database using the provided mysql command line shown in the restore wizard. Was able to install phpMyAdmin. When attempting to restore DB database using phpMyAdmin I’m seeing the following errors. Any help would be appreciated.

 ![Screenshot_2025-05-29_15-05-55](https://www.dolibarr.org/forum/uploads/dolibarrorg/original/2X/e/e619add41fc79eae68bc86b129b4ddc36a60b142.png)

---

<div class="post-metadata">

**Author:** ![jonbendtsen](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jonbendtsen](https://www.dolibarr.org/forum/u/jonbendtsen)\
**Post date:** [May 29, 2025, 7:32pm UTC](https://www.dolibarr.org/forum/t/database-restore-errors-dolibarr-20-0-3-ubuntu-24-myphpadmin/30386/2 "2025-05-29T19:32:47Z")

</div>

on the CREATE TABLE line there is a (

but I can not find the corresponding )

---

<div class="post-metadata">

**Author:** ![RSAutomation](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/r/47e85d/32.png) [@RSAutomation](https://www.dolibarr.org/forum/u/RSAutomation)\
**Post date:** [May 30, 2025, 12:23pm UTC](https://www.dolibarr.org/forum/t/database-restore-errors-dolibarr-20-0-3-ubuntu-24-myphpadmin/30386/3 "2025-05-30T12:23:09Z")

</div>

It exists further down in the code. This table is the first one, at the very beginning of the SQL dump.

DROP TABLE IF EXISTS `llx_accounting_account`;  
/\*!40101 SET @saved\_cs\_client = @@character\_set\_client _/;  
/_!40101 SET character\_set\_client = utf8 _/;  
CREATE TABLE `llx_accounting_account` (  
 `rowid` bigint(20) NOT NULL AUTO\_INCREMENT,  
 `entity` int(11) NOT NULL DEFAULT 1,  
 `datec` datetime DEFAULT NULL,  
 `tms` timestamp NOT NULL DEFAULT current\_timestamp() ON UPDATE current\_timestamp(),  
 `fk_pcg_version` varchar(32) COLLATE utf8mb3\_unicode\_ci NOT NULL,  
 `pcg_type` varchar(60) COLLATE utf8mb3\_unicode\_ci DEFAULT NULL,  
 `account_number` varchar(32) COLLATE utf8mb3\_unicode\_ci NOT NULL,  
 `account_parent` int(11) DEFAULT 0,  
 `label` varchar(255) COLLATE utf8mb3\_unicode\_ci NOT NULL,  
 `labelshort` varchar(255) COLLATE utf8mb3\_unicode\_ci DEFAULT NULL,  
 `fk_accounting_category` int(11) DEFAULT 0,  
 `fk_user_author` int(11) DEFAULT NULL,  
 `fk_user_modif` int(11) DEFAULT NULL,  
 `active` tinyint(4) NOT NULL DEFAULT 1,  
 `reconcilable` tinyint(4) NOT NULL DEFAULT 0,  
 `import_key` varchar(14) COLLATE utf8mb3\_unicode\_ci DEFAULT NULL,  
 `extraparams` varchar(255) COLLATE utf8mb3\_unicode\_ci DEFAULT NULL,  
PRIMARY KEY (`rowid`),  
UNIQUE KEY `uk_accounting_account` (`account_number`,`entity`,`fk_pcg_version`),  
KEY `idx_accounting_account_fk_pcg_version` (`fk_pcg_version`),  
KEY `idx_accounting_account_account_parent` (`account_parent`),  
CONSTRAINT `fk_accounting_account_fk_pcg_version` FOREIGN KEY (`fk_pcg_version`) REFERENCES `llx_accounting_system` (`pcg_version`)  
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3\_unicode\_ci;  
/_!40101 SET character\_set\_client = @saved\_cs\_client \*/;

---

<div class="post-metadata">

**Author:** ![jonbendtsen](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jonbendtsen](https://www.dolibarr.org/forum/u/jonbendtsen)\
**Post date:** [May 30, 2025, 12:45pm UTC](https://www.dolibarr.org/forum/t/database-restore-errors-dolibarr-20-0-3-ubuntu-24-myphpadmin/30386/4 "2025-05-30T12:45:31Z")

</div>

du you use mysql or mariadb?

---

<div class="post-metadata">

**Author:** ![RSAutomation](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/r/47e85d/32.png) [@RSAutomation](https://www.dolibarr.org/forum/u/RSAutomation)\
**Post date:** [May 30, 2025, 4:30pm UTC](https://www.dolibarr.org/forum/t/database-restore-errors-dolibarr-20-0-3-ubuntu-24-myphpadmin/30386/5 "2025-05-30T16:30:41Z")

</div>

MariaDB but I don’t think it matters? Mysql commands execute the same, as far as I know.

I attempted to run the import from command line and receive same error.

 ![Screenshot_2025-05-30_16-29-08](https://www.dolibarr.org/forum/uploads/dolibarrorg/original/2X/d/d88d853fe4f3c4750ae6f61a74907f06529c0af3.png)

---

<div class="post-metadata">

**Author:** ![RSAutomation](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/r/47e85d/32.png) [@RSAutomation](https://www.dolibarr.org/forum/u/RSAutomation)\
**Post date:** [May 30, 2025, 4:49pm UTC](https://www.dolibarr.org/forum/t/database-restore-errors-dolibarr-20-0-3-ubuntu-24-myphpadmin/30386/6 "2025-05-30T16:49:21Z")

</div>

In MariaDB I ran command “SHOW ENGINE INNODB STATUS;” and received the following:

 ![Screenshot_2025-05-30_16-47-11](https://www.dolibarr.org/forum/uploads/dolibarrorg/original/2X/b/b81c213384feaeda3af7efdcd5a6d240c121230e.png)

I’ll add that I am exporting the database from a DoliWamp windows environment to Ubuntu. Not sure if that is the issue.

---

<div class="post-metadata">

**Author:** ![RSAutomation](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/r/47e85d/32.png) [@RSAutomation](https://www.dolibarr.org/forum/u/RSAutomation)\
**Post date:** [May 30, 2025, 5:10pm UTC](https://www.dolibarr.org/forum/t/database-restore-errors-dolibarr-20-0-3-ubuntu-24-myphpadmin/30386/7 "2025-05-30T17:10:12Z")

</div>

Looks like their may be some differences in the database environments:

Windows machine:

 ![wef23f23f](https://www.dolibarr.org/forum/uploads/dolibarrorg/original/2X/6/6d77b52cbf22056a14f9c02a7a9f99d033b00a74.png)

Ubuntu machine:

 ![ubuntu-machine](https://www.dolibarr.org/forum/uploads/dolibarrorg/original/2X/1/1e104150603eb45aff43363a7888ddbd1dcb4bb6.png)

---

<div class="post-metadata">

**Author:** ![RSAutomation](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/r/47e85d/32.png) [@RSAutomation](https://www.dolibarr.org/forum/u/RSAutomation)\
**Post date:** [May 30, 2025, 5:25pm UTC](https://www.dolibarr.org/forum/t/database-restore-errors-dolibarr-20-0-3-ubuntu-24-myphpadmin/30386/8 "2025-05-30T17:25:01Z")

</div>

Further inspection reveals the tables differ between Windows / Ubuntu environments. Suspect this may be the problem?

Windows:

 ![tables-windows](https://www.dolibarr.org/forum/uploads/dolibarrorg/original/2X/6/67e917f7a221f9bbcdbea29f7fa61ea5369992b0.png)

Ubuntu:

 ![ubuntu-table](https://www.dolibarr.org/forum/uploads/dolibarrorg/original/2X/9/95fdbe50ff0167c37a11750764bf6a1170107966.png)

---

<div class="post-metadata">

**Author:** ![jonbendtsen](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jonbendtsen](https://www.dolibarr.org/forum/u/jonbendtsen)\
**Post date:** [June 1, 2025, 6:48am UTC](https://www.dolibarr.org/forum/t/database-restore-errors-dolibarr-20-0-3-ubuntu-24-myphpadmin/30386/10 "2025-06-01T06:48:57Z")

</div>

I am pretty sure it is possible to convert between the charset formats, but you might want to consult a database manual.

I also use mariadb, but I have not used windows for a long time

---

<div class="post-metadata">

**Author:** ![RSAutomation](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/r/47e85d/32.png) [@RSAutomation](https://www.dolibarr.org/forum/u/RSAutomation)\
**Post date:** [June 2, 2025, 2:12pm UTC](https://www.dolibarr.org/forum/t/database-restore-errors-dolibarr-20-0-3-ubuntu-24-myphpadmin/30386/11 "2025-06-02T14:12:49Z")

</div>

PROBLEM SOLVED!!!

It was indeed the additional table from the Windows system export that was throwing off the Linux import. I manually edited the SQL file using Notepad++ and removed the erroneous table entry. It then imported via command line with no issues.
