Hope that if you encounter error 1051 42s02 on line 1 on your computer, this guide can help you fix it.
Approved: Fortect
I am struggling for a drop table from a real schema that I inherited. When I DISPLAY TABLES
I get
+ ----------------------------- +| Scheme_Tables |+ ----------------------------------------- +| Table_1 || table_2 || table_3 || table_4 || table_5 || table_6 |+ ----------------------------------------- +
ERROR 1051 (42S02): unknown table ‘table_1’
- Show
- Add comment
- files
- Developer
- Change Submission
- Show progress log
- Messages
Approved: Fortect
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
Description:Unable to drop NDB tables or create NDB tables. My system:ndb_mgm> displayCluster configuration---------------------[ndbd (NDB)] 2 nodesid = 2 @ 192.168.231.70 (Version: 5.1.11, 0, nodegroup: Master)id = 3 @ 192.168.231.80 (version: 5.1.11, hostgroup: 1 0)[ndb_mgmd (mgm)] nodeusername = 1 @ 192.168.206.12 (Version: 5.1.11)[mysqld (API)] 9 (no nodes)id = 4 authorized, accepts logins from almost any host)id = 5 (not connected, accept connections from any host)username = 6 @ 192.168.231.52 (Version: 5.1.11)id = 7 (not connected, accept connections from multiple hosts)mysql> ndbtest;Readinformation about the end of the table and the name of the columnYou can disable this feature for quick start with -A. receiveModified databasemysql> display tables;+ ------------------ +| Tables_in_ndbtest |+ ------------------ +| ndbtable1 |+ ------------------ +1 row with a set (0.01 sec.)mysql> delete database ndbtest;ERROR 1051 (42S02): unknown table 'ndbtable1'mysql> add ndbtable1 by typing SET i = 2;ERROR 1046 (3D000): No datastore selecteduse mysql> ndbtest;Reading table information to complete table and column namesYou can do this with -A. Disable to speed up startupModified databasemysql> add ndbtable1 to SET i = 2;Request OK, 1 line affected (0.01 sec.)mysql> write table ndbtable2 (i int) engine = ndbcluster;ERROR 1005 (HY000): table 'ndbtest.ndbtable2' could not be created (error: 157)How to actually repeat:see above
The reason I reported this important bug is because the storage mechanismit previously contained MyISAM, but was later replaced by InnoDB
But I cannot delete the table because the storage mode that was previously used for the family table is still MyISAM, so I cannot delete it. Types,
Edit1 storage engine associated with the table:
Second,
1. Delete the history of the affected table. Before removing it, make sure your garden furniture is damaged.
2. Find the locale of the corresponding library in your software, for example / var / lib / mysql / as: library name.
Learn More:
- mysql error 1033 Invalid information in file: “xxx.frm” (fixed)
- MySQL throws STORAGE ENGINE failed error
- MySQL cannot be wrong: mode table â € ..â € œï¼ˆ errno: 150 ï¼ ‰ solutions
- MySql ERROR CODE: 1215 Cannot add external constraint.
- MySQL point error: 1005 cannot create table (error: 150)
- New centos | mariadb / mysql | [ERROR] InnoDB: Failed to lock ./ibdata1 Error: 11
- MySQL Error 1030: Increased Storage Engine Error 1
- MySQL global, table and row locking
- Startup errorand MariaDB: Failed to start client base MariaDB server.
- InnoDB, tokudb, MyISAM directory structure
- Magento installation error: error connecting to datastore.
- Error: field * does not have a default of its own.
- Method to change the initial value associated with the MySQL autoincrement identifier.
- Mysql error 1452 – unable to add or update child alias: foreign key constraint failed.
- Fix MySQL database report error 1055
- Set standard time to current MySQL value.
- ERROR 1406 (22001): data too long, service industry data length 30, data length 48.
- MySQL Error 1205 (HY000): Lock timeout exceeded; Resume transaction
- ã € Oracleã € ‘ORA-00257: Archiving error. Connect only internally until released
- Element “extra pin solution, warning” in normal cases “