คือ ตอนนี้ Login ได้แต่ทำไร ไม่ได้ เลยครับ ระบบ แจ้ง ว่า
table 'xxx' was not locked with LOCK TABLE
XXX คือ ตารางที่ระบบ เรียกใช้งานครับ
OS Windows 2003 Server MySQL 5.1.28-rc-community
Error Log มีอยู่ว่า
ช่วงแรก ๆ
InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
090405 14:35:46 InnoDB: Setting file .\ibdata1 size to 100 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100
090405 14:35:48 InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 64 MB
InnoDB: Database physically writes the file full: wait...
090405 14:35:50 InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 64 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
090405 14:35:53 InnoDB: Started; log sequence number 0 0
090405 14:35:54 [Note] Event Scheduler: Loaded 0 events
090405 14:35:54 [Note] D:\HOSxP\MySQL\bin\mysqld.exe: ready for connections.
Version: '5.1.28-rc-community' socket: '' port: 3306 MySQL Community Server (GPL)
090405 14:58:07 InnoDB: Error: table `pangmapha`.`access_menu` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB:
http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting.html090405 14:58:07 InnoDB: Error creating file '.\pangmapha\access_menu.ibd'.
090405 14:58:07 InnoDB: Operating system error number 80 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB:
http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.htmlInnoDB: The file already exists though the corresponding table did not
InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB
InnoDB: .ibd files around without using the SQL commands
InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did
InnoDB: mysqld crash in the middle of CREATE TABLE? You can
InnoDB: resolve the problem by removing the file '.\pangmapha\access_menu.ibd'
InnoDB: under the 'datadir' of MySQL.
090405 14:58:08 InnoDB: Error: table `pangmapha`.`accessoperation` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB:
http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting.html090405 14:58:08 InnoDB: Error creating file '.\pangmapha\accessoperation.ibd'.
090405 14:58:08 InnoDB: Operating system error number 80 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB:
http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.htmlInnoDB: The file already exists though the corresponding table did not
InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB
InnoDB: .ibd files around without using the SQL commands
InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did
InnoDB: mysqld crash in the middle of CREATE TABLE? You can
InnoDB: resolve the problem by removing the file '.\pangmapha\accessoperation.ibd'
InnoDB: under the 'datadir' of MySQL.
090405 14:58:09 InnoDB: Error: table `pangmapha`.`active_medication` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB:
http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting.html090405 14:58:09 InnoDB: Error creating file '.\pangmapha\active_medication.ibd'.
090405 14:58:09 InnoDB: Operating system error number 80 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB:
http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.htmlInnoDB: The file already exists though the corresponding table did not
InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB
InnoDB: .ibd files around without using the SQL commands
InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did
InnoDB: mysqld crash in the middle of CREATE TABLE? You can
InnoDB: resolve the problem by removing the file '.\pangmapha\active_medication.ibd'
InnoDB: under the 'datadir' of MySQL.
090405 14:58:09 InnoDB: Error: table `pangmapha`.`adr_cause` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB:
http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting.html090405 14:58:09 InnoDB: Error creating file '.\pangmapha\adr_cause.ibd'.
090405 14:58:09 InnoDB: Operating system error number 80 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB:
http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.htmlInnoDB: The file already exists though the corresponding table did not
InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB
InnoDB: .ibd files around without using the SQL commands
InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did
InnoDB: mysqld crash in the middle of CREATE TABLE? You can
InnoDB: resolve the problem by removing the file '.\pangmapha\adr_cause.ibd'
InnoDB: under the 'datadir' of MySQL.
090405 14:58:10 InnoDB: Error: table `pangmapha`.`adr_continue_rechallenge` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB:
http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting.html090405 14:58:10 InnoDB: Error creating file '.\pangmapha\adr_continue_rechallenge.ibd'.
090405 14:58:10 InnoDB: Operating system error number 80 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB:
http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.htmlInnoDB: The file already exists though the corresponding table did not
InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB
InnoDB: .ibd files around without using the SQL commands
InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did
InnoDB: mysqld crash in the middle of CREATE TABLE? You can
InnoDB: resolve the problem by removing the file '.\pangmapha\adr_continue_rechallenge.ibd'
InnoDB: under the 'datadir' of MySQL.
090405 14:58:10 InnoDB: Error: table `pangmapha`.`adr_death` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
ช่วงหลัง ๆ
090515 14:48:24 [ERROR] Cannot find or open table pangmapha_blank/ovst from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See
http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting.htmlhow you can resolve the problem.
090515 14:49:17 [ERROR] Cannot find or open table pangmapha_blank/ovst from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See
http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting.htmlhow you can resolve the problem.
090515 14:55:24 [Note] D:\HOSxP\MySQL\bin\mysqld.exe: Normal shutdown
090515 14:55:24 [Note] Event Scheduler: Purging the queue. 0 events
090515 14:55:26 [Warning] D:\HOSxP\MySQL\bin\mysqld.exe: Forcing close of thread 1988 user: 'sa'
090515 14:55:26 [Warning] D:\HOSxP\MySQL\bin\mysqld.exe: Forcing close of thread 1987 user: 'sa'
090515 14:55:26 [Warning] D:\HOSxP\MySQL\bin\mysqld.exe: Forcing close of thread 1961 user: 'sa'
090515 14:55:26 [Warning] D:\HOSxP\MySQL\bin\mysqld.exe: Forcing close of thread 400 user: 'sa'
090515 14:55:26 [Warning] D:\HOSxP\MySQL\bin\mysqld.exe: Forcing close of thread 372 user: 'sa'
090515 14:55:26 [Warning] D:\HOSxP\MySQL\bin\mysqld.exe: Forcing close of thread 367 user: 'sa'
090515 14:55:26 [Warning] D:\HOSxP\MySQL\bin\mysqld.exe: Forcing close of thread 366 user: 'sa'