2 Answers
- Newest
- Most votes
- Most comments
1
Hello.
Were there any warnings or errors when creating a dump file from the database?
What often happens is that code related to GTID is included in the obtained dump file, resulting in an error.
If you open the dump file and find a line with a command like the one below, try deleting it.
SET @MYSQLDUMP_TEMP_LOG_BIN = @@SESSION.SQL_LOG_BIN;
SET @@SESSION.SQL_LOG_BIN= 0;
SET @@GLOBAL.GTID_PURGED='';
SET @@SESSION.SQL_LOG_BIN = @MYSQLDUMP_TEMP_LOG_BIN;
Alternatively, try using "--set-gtid-purged=OFF" as a command option when obtaining the dump file.
0
Are you using the admin user to grant those privileges? Did you run FLUSH PRIVILEGES
after updating and granting access?
Relevant content
- asked 2 years ago
- asked 5 years ago
- asked 6 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago