???ขอต่อ กระทู้หน่อยนะครับ ใน xxxx.err ขึ้นแบบนี้หลัง up vertion จากเดิม 3.53.3.28 เป็น 3.54.2.2
ครั้งแรก upgrade struger ไม่ผ่านขึ้นแบบนี้ครับ ครั้ง 2 ผ่านใช้มา2-3วันแล้วครับ
แต่ไม่ทราบว่าขึ้นแบบนี้จะมีปัญหากับระบบหรือเปล่าครับ(แต่ก็ใช้งานได้ปกติ) ไม่มั้นใจเลยมือใหม่ครับ
ตัดมาให้ดูบางส่วนนะครับเยอะเกินตาลาย
Version: '5.1.39-percona' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL), XtraDB 8, Revision 45
110313 1:00:12 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 1001 iterations
110313 1:00:12 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 1002 iterations
110313 1:00:12 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 1003 iterations
110313 1:00:12 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 1004 iterations
110313 1:00:12 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 1005 iterations
110313 1:00:12 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 1006 iterations
110313 1:00:12 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 1007 iterations
110313 1:00:12 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 1008 iterations
110313 1:00:12 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 1009 iterations
110313 1:06:32 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 19898 iterations
110313 1:06:32 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 19899 iterations
InnoDB: Warning: tablespace './hos/tmp_patient_history.ibd' has i/o ops stopped for a long time 20001
110313 1:06:32 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 19900 iterations
InnoDB: Warning: tablespace './hos/tmp_patient_history.ibd' has i/o ops stopped for a long time 20002
110313 1:06:32 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 19901 iterations
InnoDB: Warning: tablespace './hos/tmp_patient_history.ibd' has i/o ops stopped for a long time 20003
110313 1:06:32 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 19902 iterations
InnoDB: Warning: tablespace './hos/tmp_patient_history.ibd' has i/o ops stopped for a long time 20004
110313 1:06:32 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 19903 iterations
InnoDB: Warning: tablespace './hos/tmp_patient_history.ibd' has i/o ops stopped for a long time 20005
InnoDB: Warning: tablespace './hos/tmp_patient_history.ibd' has i/o ops stopped for a long time 25110
110313 1:08:15 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 24998 iterations
InnoDB: Warning: tablespace './hos/tmp_patient_history.ibd' has i/o ops stopped for a long time 25111
110313 1:08:15 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 24999 iterations
InnoDB: Warning: tablespace './hos/tmp_patient_history.ibd' has i/o ops stopped for a long time 25112
110313 1:08:15 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 25000 iterations
InnoDB: Warning: tablespace './hos/tmp_patient_history.ibd' has i/o ops stopped for a long time 25113
110313 1:08:15 InnoDB: Warning: problems renaming 'hos/tmp_patient_history' to 'hos/#sql2-154d-4c', 25001 iterations
110313 1:08:15 InnoDB: Error; possible reasons:
InnoDB: 1) Table rename would cause two FOREIGN KEY constraints
InnoDB: to have the same internal name in case-insensitive comparison.
InnoDB: 2) table `hos`.`tmp_patient_history` exists in the InnoDB internal data
InnoDB: dictionary though MySQL is trying to rename table `hos`.`#sql-154d_4c` to it.
InnoDB: Have you deleted the .frm file and not used DROP TABLE?
InnoDB: You can look for further help from
InnoDB:
http://dev.mysql.com/doc/refman/5.1/en/innodb-troubleshooting.htmlInnoDB: If table `hos`.`tmp_patient_history` is a temporary table #sql..., then it can be that
InnoDB: there are still queries running on the table, and it will be
InnoDB: dropped automatically when the queries end.
InnoDB: You can drop the orphaned table inside InnoDB by
InnoDB: creating an InnoDB table with the same name in another
InnoDB: database and copying the .frm file to the current database.
InnoDB: Then MySQL thinks the table exists, and DROP TABLE will
InnoDB: succeed.
110313 1:08:15 InnoDB: Error: table `hos`.`#sql2-154d-4c` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to rename the table.
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.html110313 1:58:13 [Note] /usr/sbin/mysqld: Normal shutdown
หัวข้อ: sql error (อ่าน 5111 ครั้ง)