Xxn x chat


10-Feb-2015 23:38

If you move that file to a safe temporary location (just to be safe) that should fix the problem. Otherwise you just end up with another orphaned file when you try a second time. I deleted the orphaned idb file..when I went the recreate the table with the exact same name I got a message saying that the table already exists(for which I deleted the file)...after the above action a new orphaned file was created in the dir..strange... However, the easier option is this: restart mysql, then do the same four steps listed near the beginning of the post.One caveat though, make sure what ever is causing the problem originally, e.g. This way, the tablespace id on the data dictionary and the file matched; thus importing the tablespace succeeded.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.When I try to run queries using these tables, Navicat then warns me that the particular table does not exist.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?Even made larger, the 'tablespace full' can still occur with larger queries and such (lots of non-table 'stuff' is stored in there, undo logs, caches, etc...).

I am running a local server of my SQL 5.6.10 on Mac OS 10.8.3 and manage my database via Navicat essentials for My SQL.

As I said, I'm new to the subject and pretty much clueless. resetting my local My SQL server, or maybe user permission rights might have to do with it, but I am just hypothesizing here. A 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.

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.

This can give you greater confidence in dealing with some of the Inno DB "gotcha's" during the recovery process or even file transfers.

Xxn x chat-41

global updating epo 4 5

So far so good - here comes the good part: When I try to CREATE the table, e.g.

named "temp", that was previously there, I get the following error message: So that means that I am advised to discard the table space but when I try to do so the table does not exist.