Hello Neil,
On 1/22/2016 3:23 PM, Neil Tompkins wrote:
2016-01-22 19:43:48 2556 [ERROR] InnoDB: Attempted to open a previously
opened tablespace. Previous tablespace mysql/innodb_table_stats uses space
ID: 1 at filepath: .\mysql\innodb_table_stats.ibd. Cannot open tablespace
sportstrader/event w
One point to add, that might be of interest is that the primary key and
foreign key for two of related tables is a VARCHAR(255), and my MySQL
version is '5.6.12-log'
On Fri, Jan 22, 2016 at 8:47 PM, Lisa Smith wrote:
> Hi Neil,
>
> When you say you delete the current database, do you mean the da
Sorry to clarify; I have my database schema, and when the database crashes
at the moment, I delete that crashed database, create the new database
using the schema, and then restore the data using a import routine I have
written in C Sharp, to import data from a CSV file to MySQL tables.
The datab
Hi Neil,
When you say you delete the current database, do you mean the database
files only? Are you doing a complete restore?
On Fri, Jan 22, 2016 at 1:23 PM, Neil Tompkins wrote:
> Hi,
>
> Hoping someone can help me identify why I keep having to restore my
> database. You can see below, that
The error is stating that your innodb log sequence is higher that that of
the actual data files...any chance your data partition is full after your
restore?
On Fri, Jan 22, 2016 at 3:23 PM, Neil Tompkins wrote:
> Hi,
>
> Hoping someone can help me identify why I keep having to restore my
> datab
My disk drive has about 3 gb free space. The sequence of events is
1. Create database
2. Restore the data
3. Use the database, SELECT data etc
4. Shut down PC
5. When I restart PC I get this error
Hi,
Hoping someone can help me identify why I keep having to restore my
database. You can see below, that my machine shut down normally, yet when
I restarted the machine back up, I'm getting the error
'mysql\innodb_table_stats.ibd. Cannot open tablespace' and am having to
delete the current datab
