Without going into too much detail (more here), the database server's tablespace is defined by the innodb_data_file_path setting and by default is rather small. resetting my local MySQL server, or maybe user permission rights might have to do with it, but I am just hypothesizing here.Ī little late here but generally I've seen this problem occur when you get a 'tablespace full' error when running in a 'innodb_file_per_table' mode.
I suspect that re-booting my laptop, i.e. Is it possible that there is some type of remnant of this table at a different place where the DISCARD query isn't checking? And does anybody have an idea what could trigger all that - completely randomly as it seems? So that means that I am advised to discard the table space but when I try to do so the table does not exist. I get the following error messages: Error : Unknown table 'database.temp'Įrror : Table 'database.temp' doesn't exist However, if I try to drop the table, or try to discard the tablespace for this table, using DROP TABLE temp Please DISCARD the tablespace before IMPORT. named "temp", that was previously there, I get the following error message: Error : Tablespace for table '`database`.`temp`' exists. So far so good - here comes the good part: When I try to run queries using these tables, Navicat then warns me that the particular table does not exist.
The error I get is that after running and managing my database just fine for a couple of days/weeks something triggers to (it appears incompletely) delete some of the tables I created using queries from within Navicat. I am running a local server of MySQL 5.6.10 on MacOS 10.8.3 and manage my database via Navicat essentials for MySQL.
0 kommentar(er)
