- Newest
- Most votes
- Most comments
Hello,
Is it failing due to "its failing because a table mysql.host exists." or "its failing because a table mysql.host do not exists."
In the Aurora MySQL upgrade prechecks
- There must be no InnoDB metadata inconsistency in the mysql.host table.
can you confirm the error message as following
"id": "checkTableOutput", "title": "Issues reported by 'check table x for upgrade' command", "status": "OK", "detectedProblems": [ { "level": "Error", "dbObject": "mysql.host", "description": "Table 'mysql.host' doesn't exist" } ] },
With master user please try this
mysql> use mysql; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A
Database changed
-
mysql> show tables like 'host'; +------------------------+ | Tables_in_mysql (host) | +------------------------+ | host | +------------------------+ 1 row in set (0.26 sec)
-
mysql> describe host;
Hope it helps and if it does, I would appreciate if answer can be accepted so that community can benefit for clarity when searching for similar enquiries in repost/aws guide..
Hello,
Yes, the 'mysql.host' is causing the issue, during the checkTableOutput pre-check it is failing and will not upgrade , although you can create BG with same version but during upgrade it will fail again .
As you do not have access to mysql and storage , I'll suggest of you reach out to AWS support to work on this table or precheck mitigation so this precheck can pass .
Another option you may try , i haven't tested as i do not have any cluster with this issue , (but please test and take a snapshot of present cluster)
-
Upgrade is failing due to the presence of 'mysql.host' table in the Aurora clusters.
-
Try to clone the cluster , and check the mysql.host table
-
i expect the clone should not have this table , and try to upgrade the clone .
Hope it helps and if it does, I would appreciate if answer can be accepted so that community can benefit for clarity when searching for similar enquiries in repost/aws guide..
I have reached out to AWS support now. Cloning is too tedious for us to do at this point but if we do it and it works, i will let you know.
Relevant content
- asked 8 months ago
- asked 4 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
The error is as follows
When i look into the database, I see a very weird mysql.host table If I list tables in the mysql database using the following command, i can see that the table is in the returned list
However when I try to describe it, I get the following error