Database Backup and Recovery (MOSC)

MOSC Banner

MySQL NDB cluster 7.6.13 dump restore failing when "mysql" DB is included in the mysqldump

edited May 19, 2020 5:01AM in Database Backup and Recovery (MOSC) 1 commentAnswered

Use Case:

Upgrade MySQL NDB cluster 7.2.33 to MySQL NDB cluster 7.6.13 (upgrade path: MySQL 7.2.33 > 7.4.23 > MySQL 7.6.13)

Observations:

  • mysqldump/restore works on 7.2.33 with only one error ( Table 'ndb_apply_status' is read only)
  • Upgrading from MySQL 7.2.33 to 7.4.23 goes smoothly and no issues have been observed.
  • Upgrading from 7.4.23 to 7.6.13 goes fine, mysql starts up normally, tables can be updated without issue before restore. Once restore fails, mysql shows empty tables which gets read-only after restore
    • The issue starts when a dump is restored where the dump contains the “mysql” DB. When excluding this DB from the dump, dump restore has no issues. (for errors please see attached log file mysql-dump-restore-7.6.13-error-logl.txt and error.log).

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center