# Problem with switching from mariadb to percona

**URL:** <https://forums.percona.com/t/problem-with-switching-from-mariadb-to-percona/10356>\
**Category:** Percona Distribution for MySQL\
**Created:** [May 6, 2021, 9:32am UTC](https://forums.percona.com/t/problem-with-switching-from-mariadb-to-percona/10356 "2021-05-06T09:32:14Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![AnPa](https://avatars.discourse-cdn.com/v4/letter/a/bc8723/32.png) [@AnPa](https://forums.percona.com/u/AnPa)\
**Post date:** [May 6, 2021, 9:32am UTC](https://forums.percona.com/t/problem-with-switching-from-mariadb-to-percona/10356/1 "2021-05-06T09:32:14Z")

</div>

Hi,

i would like to change my database server to percona xtradb cluster (5.7 or 8)  
Actually we use mariadb 10.5.9 and i am not able to import my mysql dump from mariadb to my new test-percona-node.

i receive for this:  
`seit` date NOT NULL DEFAULT current\_timestamp(),

ERROR 1067 (42000): Invalid default value for ‘seit’

Any Idea why it is working in mariadb and not in percona?

Regards

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [May 6, 2021, 3:54pm UTC](https://forums.percona.com/t/problem-with-switching-from-mariadb-to-percona/10356/2 "2021-05-06T15:54:59Z")

</div>

Helllo @AnPa ,  
Current timestamp is not a function when used in create table. This is the proper way:

```
CREATE TABLE stuff (
    id int UNSIGNED PRIMARY KEY AUTO_INCREMENT,
    seit date NOT NULL DEFAULT CURRENT_TIMESTAMP
);

```

---

<div class="post-metadata">

**Author:** ![AnPa](https://avatars.discourse-cdn.com/v4/letter/a/bc8723/32.png) [@AnPa](https://forums.percona.com/u/AnPa)\
**Post date:** [May 6, 2021, 3:58pm UTC](https://forums.percona.com/t/problem-with-switching-from-mariadb-to-percona/10356/3 "2021-05-06T15:58:03Z")

</div>

but it is a mysqldump from my actual mariadb server. What goes wrong that it makes bad dumps? ☹

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [May 6, 2021, 4:19pm UTC](https://forums.percona.com/t/problem-with-switching-from-mariadb-to-percona/10356/4 "2021-05-06T16:19:58Z")

</div>

> **[CURRENT\_TIMESTAMP](https://mariadb.com/kb/en/current_timestamp/)**
>
> Synonym for NOW().

Perhaps a bug in maria’s mysqldump? Have you tried the dump binary from community? What about using mydumper?

---

<div class="post-metadata">

**Author:** ![AnPa](https://avatars.discourse-cdn.com/v4/letter/a/bc8723/32.png) [@AnPa](https://forums.percona.com/u/AnPa)\
**Post date:** [May 10, 2021, 8:15am UTC](https://forums.percona.com/t/problem-with-switching-from-mariadb-to-percona/10356/5 "2021-05-10T08:15:46Z")

</div>

now tryed with mydumper and restored with myloader. Same issue:

 ![grafik](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/8/8e9eb1c009d8e3601eedb479740d4d4a9902077e.png)

---

<div class="post-metadata">

**Author:** ![CTutte](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ctutte/32/1341_2.png) [@CTutte](https://forums.percona.com/u/CTutte)\
**Post date:** [May 10, 2021, 12:51pm UTC](https://forums.percona.com/t/problem-with-switching-from-mariadb-to-percona/10356/6 "2021-05-10T12:51:53Z")

</div>

Hi Anpa,

For the record and as shown in [MariaDB versus MySQL - Compatibility - MariaDB Knowledge Base](https://mariadb.com/kb/en/mariadb-vs-mysql-compatibility/) , there are some imcompabilities between different MariaDB and MySQL versions.  
There is currently no information about MariaDB 10.5 to 5.7.

It might be possible to workaround the error by modifying some columns as my college suggested, but since there is no official support from MariaDB 10.5 to MySQL 5.7, chances are more errors can pop up.  
I suggest trying to restore the dump from MariaDB 10.5 into MariaDB 10.4 or even MariaDB 10.3, then use mysqldump binary from MariaDB10.4 to restore on MySQL 5.7 and see if it works. You can do a mysqldump --no-data to dump schema only and do a fast test.

Do note that there are other incompatibilities between different MariaDB and MYSQL 5.7 version (described on the above link). The products have been diverging on every newer release and doing a migration back and forth is becoming more complex on recent versions, having to use intermediate servers for the migration

Regards