![]() ![]() Hope this is solution helped you to resolve “ Unknown collation: ‘utf8mb4_0900_ai_ci’” issue. after the above changes, the database was successfully restored! sed -i 's/utf8mb4_0900_ai_ci/utf8_general_ci/g' backup.sql sed -i 's/CHARSET=utf8mb4/CHARSET=utf8/g' backup.sql The Linux system users can use the sed command to replace text in files directly. With: ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci Navicat Premium 16.2.2 Crack simplifies a lot of functions it makes copies, and the intrusion of data between tables between various databases is just. Replace the below string: ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci Edit the database backup file in text editor and replace “ utf8mb4_0900_ai_ci” with “ utf8mb4_general_ci” and “ CHARSET=utf8mb4” with “ CHARSET=utf8“. Then we do a little tweak in the backup file to resolve this. After installed, key in the Registration Key (16 digit) on the pop-up Registration screen and click Activate to online activate the key. Drag Navicat to your Applications folder to install. So we got that the destination server doesn’t contain the required database collation. Load the Navicat CD Installation disk into the CD-ROM drive. See the error screenshot during database restoration.Īfter a little investigation, I found that the MySQL server running on the destination is an older version than the source. The collation id may differ based on the MySQL version.Įrror message: Error 1273 (HY000) at line 25 Unknown collation: 'utf8mb4_0900_ai_ci' ![]() Let’s see the problem and solution to the issue faced recently: Problemĭuring the migration of a web application, I got the below error while restoring a database on another server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |