Re: How To Remove Zombie Databases from INFORMATION_SCHEMA 5.7.29
Ok, I found a quick-and-dirty solution:
- create the missing directory in the filesystem ("mkdir /var/lib/mysql/Mand3")
- do NOT copy another database's file there (else MySQL will crash with "[ERROR] [FATAL] InnoDB: Tablespace id is 332 in the data dictionary but in file ./Mand3/sg_adr_adrarten.ibd it is 8234!")
- set lower_case_table_names = 0 (normal = 1 here)
- start MySQL
- start the client and execute "drop database Mand3;"
- stop MySQL
- set lower_case_table_names = 1 again
- start MySQL
No error messages any more at startup!
Nevertheless, I'm still interested in "how to repair INFORMATION_SCHEMA"... just in case ;)
-Matt
Subject
Written By
Posted
Re: How To Remove Zombie Databases from INFORMATION_SCHEMA 5.7.29
March 15, 2020 10:49AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.