ERROR 1030 (HY000) at line 25: Got error 168 from storage engine

Question

I'm trying to import sql to my database.

I'm using Ubuntu OS.

Here is an error:

david@david-VirtualBox:~$ mysql -u root -p test_project < db.sql
Enter password: 
ERROR 1030 (HY000) at line 25: Got error 168 from storage engine`

mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
| sys                |
| testBase           |
| test_project       |
+--------------------+
6 rows in set (0,05 sec)

mysql> use test_project;
Database changed

mysql> show tables;
Empty set (0,00 sec)

Any ideas how to fix it? I've tried to google this problem, but couldn't find anything useful.

Thank you for your answers.

This could be a potential answer: https://dba.stackexchange.com/questions/138505/receiving-general-error-1030-got-error-168-from-storage-engine — Florian Humblot, May 31 '17 at 09:02
Go to phpmyadmin (if you have it), select your database and in the table of tables you'll see a column called "type", that's the storage engine — Florian Humblot, May 31 '17 at 09:06
Maybe mysql doesn't have permission to write to the storage folder on your system or you could be out of space on that volume — Florian Humblot, May 31 '17 at 09:10
I guess the error message comes from your SQL statement while creating table. Engine name should be quoted with ' but not ` . — Joe Horn, May 31 '17 at 09:11

score 5 · Answer 1 · answered Feb 26 '18 at 17:30

I ran into this error as well and it turned out that the hard disk drive on the server was full.

I was trying to truncate a table. I couldn't do it through the web script or through MySQL Workbench.

After shaking my fist at the server admin I deleted some temporary files, as I had to wait for his availability, and I was then able to perform my truncate.

score 0 · Answer 2 · answered Apr 23 '19 at 10:30

Did you have test_project already before importing?

I was getting the same error after failed attempt to drop the schema and deleting the schema dir.

The only solution that worked for me was to drop the existing schema with the same name, delete related dir under /var/lib/mysql/, then import.

See this great answer for more details.

score 0 · Answer 3 · answered Jun 06 '20 at 03:36

0

Look at your MySQL error logs. When I did that, I saw a bunch of messages like:

2020-06-05T22:40:16.305594Z 57444 [Warning] InnoDB: Tablespace 'client_sg_AdminItUS/SomeTable' exists in the cache with id 4982441 != 5000680

I dropped the bad DB (this is a test server) and everything is fine now.

drop database client_sg_AdminItUS;

answered Jun 06 '20 at 03:36

Ryan Shillington

23,006
14
93
108

Thanks. Same error , I'm getting. But, dropping the db isn't option for me. I can drop the table, which I did already. Any other workaround do you have? – Channa Jul 11 '21 at 19:15
Unfortunately I don't, @Shiwangini. – Ryan Shillington Jul 12 '21 at 19:58

score 0 · Answer 4 · answered Mar 09 '21 at 21:25

I just wanted to say that I too was getting this error but got past it by commenting out the variables below. I cannot tell you the combination that was causing it because I am in dire straits trying to get this K8s image up and running. One or a combo of these commented-out variables is the cause.

  - args:
    - --max-connections=1001
    - --lower-case-table-names=1
    - --max-allowed-packet=128M
    #- --innodb_data_file_path=ibdata1:10M:autoextend:max:512M
    #- --innodb_buffer_pool_size=3G
    #- --innodb_log_buffer_size=1024M
    #- --innodb_log_file_size=2G
    #- --innodb_write_io_threads=18
    #- --innodb_flush_log_at_trx_commit=0
    #- --innodb_doublewrite=0        
    #- --innodb_force_recovery=1
    #- --tmp_table_size=256M
    #- --max_heap_table_size=256M

ERROR 1030 (HY000) at line 25: Got error 168 from storage engine

4 Answers4

Linked