InnoDB error 5
Had a system crash this morning and I can't seem to get mysql back up and running. This is the error: InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 2013-11-21 08:47:26 1570 [ERROR] InnoDB: Tried to read 16384 bytes at offset 589824. Was only able to read -1. 2013-11-21 08:47:26 802808c00 InnoDB: Operating system error number 5 in a file operation. InnoDB: Error number 5 means 'Input/output error'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-11-21 08:47:26 802808c00 InnoDB: File operation call: 'read' returned OS error 105. 2013-11-21 08:47:26 802808c00 InnoDB: Cannot continue operation. I followed that link but it doesn't tell me anything outside of what is above. Can I fix this? Thanks. -- Paul Halliday http://www.pintumbler.org/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: InnoDB error 5
2013/11/21 Reindl Harald h.rei...@thelounge.net Am 21.11.2013 13:51, schrieb Paul Halliday: Had a system crash this morning and I can't seem to get mysql back up and running. This is the error: InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 2013-11-21 08:47:26 1570 [ERROR] InnoDB: Tried to read 16384 bytes at offset 589824. Was only able to read -1. 2013-11-21 08:47:26 802808c00 InnoDB: Operating system error number 5 in a file operation. InnoDB: Error number 5 means 'Input/output error'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-11-21 08:47:26 802808c00 InnoDB: File operation call: 'read' returned OS error 105. 2013-11-21 08:47:26 802808c00 InnoDB: Cannot continue operation. I followed that link but it doesn't tell me anything outside of what is above. Can I fix this? i would look in the *system logs* because this pretty sure comes from the underlying operating system and is *not* mysql specific which is also in the message statet with returned OS error 105 http://lxr.free-electrons.com/source/include/uapi/asm-generic/errno-base.h#L8 Looks like a broken disk or FS corruption :-( Good luck! Manuel.
Re: InnoDB error 5
It was indeed corruption :/ what a day. I was able to move everything over to another partition and have managed to get mysql up and running again. There was a single file I could not, an .idb (the ,.frm is there). Is it possible to fix this from ibdata or the logs? Thanks. On Thu, Nov 21, 2013 at 9:46 AM, Manuel Arostegui man...@tuenti.com wrote: 2013/11/21 Reindl Harald h.rei...@thelounge.net Am 21.11.2013 13:51, schrieb Paul Halliday: Had a system crash this morning and I can't seem to get mysql back up and running. This is the error: InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 2013-11-21 08:47:26 1570 [ERROR] InnoDB: Tried to read 16384 bytes at offset 589824. Was only able to read -1. 2013-11-21 08:47:26 802808c00 InnoDB: Operating system error number 5 in a file operation. InnoDB: Error number 5 means 'Input/output error'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-11-21 08:47:26 802808c00 InnoDB: File operation call: 'read' returned OS error 105. 2013-11-21 08:47:26 802808c00 InnoDB: Cannot continue operation. I followed that link but it doesn't tell me anything outside of what is above. Can I fix this? i would look in the *system logs* because this pretty sure comes from the underlying operating system and is *not* mysql specific which is also in the message statet with returned OS error 105 http://lxr.free-electrons.com/source/include/uapi/asm-generic/errno-base.h#L8 Looks like a broken disk or FS corruption :-( Good luck! Manuel. -- Paul Halliday http://www.pintumbler.org/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: InnoDB error 5
What is the best way to backup your database. Which are the files that I need to store on a usb disk -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: InnoDB error 5
Hello Nick, On 11/21/2013 10:32 AM, Nick Cameo wrote: OOoopppsss! I do mean for recovery/continual backup. I will do it manually, but basically get all the data on a USB disk and be able to recover/move it (the data) on another machine, the same machine etc.. I hope I did not just open up a can of worms. We just went live and this post gave me a rude awakening. What is an effective easy to follow protocol for backup and recovery in mysql! Nick from Toronto There are two basic types of backups, logical and physical. Logical backups are performed by a utility that converts your database objects into their CREATE ... commands and exports your data as INSERT ... commands (or as delimited files). These kinds of backups are quite portable and compress well. An example of such a tool is mysqldump. http://dev.mysql.com/doc/refman/5.6/en/mysqldump.html Physical backups can happen many different ways. The easiest version to make/restore is the 'cold copy'. This is exactly what it sounds like. Shutdown your mysqld and make a copy of everything. At the absolute minimum you need the ibdata files, the ib_log files, and all folders inside your --datadir location. Warm or hot copies are provided by tools that coordinate with the server to synchronize the state of the InnoDB data to the moment the non-InnoDB data has been captured. One example of this is MySQL Enterprise Backup. http://dev.mysql.com/doc/mysql-enterprise-backup/3.9/en/index.html Additional details abound in the manual: http://dev.mysql.com/doc/refman/5.6/en/backup-types.html Regards, -- Shawn Green MySQL Senior Principal Technical Support Engineer Oracle USA, Inc. - Hardware and Software, Engineered to Work Together. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: InnoDB error 5
Am 21.11.2013 18:59, schrieb Paul Halliday: It was indeed corruption :/ what a day. I was able to move everything over to another partition and have managed to get mysql up and running again. There was a single file I could not, an .idb (the ,.frm is there). Is it possible to fix this from ibdata or the logs? no - that's what backups are for lesson learned the hard way for production you have usually a replication-slave in the same network which is regulary stopped and it's datadir rsynced to a offsite-backup (one possible backup strategy) and so if one server get a corrupt filesystem there is a just-in-time backup while if things are going terrible wrong (power outage and the slave is also corrupt you rsync back the slightly outdated offsite backup On Thu, Nov 21, 2013 at 9:46 AM, Manuel Arostegui man...@tuenti.com wrote: 2013/11/21 Reindl Harald h.rei...@thelounge.net Am 21.11.2013 13:51, schrieb Paul Halliday: Had a system crash this morning and I can't seem to get mysql back up and running. This is the error: InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 2013-11-21 08:47:26 1570 [ERROR] InnoDB: Tried to read 16384 bytes at offset 589824. Was only able to read -1. 2013-11-21 08:47:26 802808c00 InnoDB: Operating system error number 5 in a file operation. InnoDB: Error number 5 means 'Input/output error'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-11-21 08:47:26 802808c00 InnoDB: File operation call: 'read' returned OS error 105. 2013-11-21 08:47:26 802808c00 InnoDB: Cannot continue operation. I followed that link but it doesn't tell me anything outside of what is above. Can I fix this? i would look in the *system logs* because this pretty sure comes from the underlying operating system and is *not* mysql specific which is also in the message statet with returned OS error 105 http://lxr.free-electrons.com/source/include/uapi/asm-generic/errno-base.h#L8 Looks like a broken disk or FS corruption :-( signature.asc Description: OpenPGP digital signature
Re: InnoDB error 5
OOoopppsss! I do mean for recovery/continual backup. I will do it manually, but basically get all the data on a USB disk and be able to recover/move it (the data) on another machine, the same machine etc.. I hope I did not just open up a can of worms. We just went live and this post gave me a rude awakening. What is an effective easy to follow protocol for backup and recovery in mysql! Nick from Toronto -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: InnoDB error 5
Am 21.11.2013 13:51, schrieb Paul Halliday: Had a system crash this morning and I can't seem to get mysql back up and running. This is the error: InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 2013-11-21 08:47:26 1570 [ERROR] InnoDB: Tried to read 16384 bytes at offset 589824. Was only able to read -1. 2013-11-21 08:47:26 802808c00 InnoDB: Operating system error number 5 in a file operation. InnoDB: Error number 5 means 'Input/output error'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html 2013-11-21 08:47:26 802808c00 InnoDB: File operation call: 'read' returned OS error 105. 2013-11-21 08:47:26 802808c00 InnoDB: Cannot continue operation. I followed that link but it doesn't tell me anything outside of what is above. Can I fix this? i would look in the *system logs* because this pretty sure comes from the underlying operating system and is *not* mysql specific which is also in the message statet with returned OS error 105 http://lxr.free-electrons.com/source/include/uapi/asm-generic/errno-base.h#L8 signature.asc Description: OpenPGP digital signature
InnoDB: Error: unlock row could not find a 4 mode lock on the record
Hi All, InnoDB repeatedly prints this message in the error log: # InnoDB: Error: unlock row could not find a 4 mode lock on the record Im not sure if the error message is critical or not, but its definitely not nice to have in the error log. After some exploration, I found this error is relevant to Bugs*#41756, #48306, #53674. * But I couldn't find out, how to resolve this! Kindly help! Below are some details. mysql = 5.1.43 Storage engine = innodb; transaction-isolation = READ-COMMITTED; binlog_format = mixed; ** ** Thanks,
innodb error
Recently, I got the following error. I found the solution to solve the problem by increasing the log file size. However, I want to know why this error will happen. I can't find the explanation for that error. Anyone can give me some information about the error? 070321 16:38:41 InnoDB: Started; log sequence number 3 26658057 070321 16:38:41 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.27-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 070322 9:24:54 InnoDB: ERROR: the age of the last checkpoint is 9433633, InnoDB: which exceeds the log group capacity 9433498. InnoDB: If you are using big BLOB or TEXT rows, you must set the InnoDB: combined size of log files at least 10 times bigger than the InnoDB: largest such row. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Innodb Error 1030
I'm trying to fix a problem with a users innodb database (mysql 5.0).When they try a very simple insert they get ERROR 1030 (HY000): Got error -1 from storage engine I have dumped and reloaded the tables but the problem persists. CHECK TABLE does not indicate an error. I stopped and restarted the server once normally, without attempting any innodb_force_recovery options. There are no other unusual indications on the server. It has not been shut down abruptly recently, the load is low, memory and disk space is fine. Does anyone have any suggestions for correcting this error? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Bizarre InnoDB Error Message ( trx-active_trans == 0, but trx-conc_state != TRX_NOT_STARTED)
Hi Heikki,
Yes indeed. We have a uid field that is AUTO INC. Is the error more
an issue of the auto inc code in InnoDB not setting its error codes
correctly on a rollback than the auto increment code initiating an
error? Thank you in advance.
Best Regards,
Jason
On 12/31/06, Heikki Tuuri [EMAIL PROTECTED] wrote:
Jason,
I am Cc:ing the MySQL General mailing list, so that others who bump into
this bug can find this discussion.
Jason J. W. Williams wrote:
Mr. Tuuri,
We have a high degree of UPDATE/INSERT concurrency along with high
SELECTs. It causes a deadlock about once every 24 hours. In this case
a deadlock was associated with this event.
ha_innodb.cc in 5.0:
int
convert_error_code_to_mysql(
/**/
/* out: MySQL error code */
int error, /* in: InnoDB error code */
THD*thd)/* in: user thread handle or NULL */
{
if (error == DB_SUCCESS) {
return(0);
} else if (error == (int) DB_DUPLICATE_KEY) {
return(HA_ERR_FOUND_DUPP_KEY);
} else if (error == (int) DB_RECORD_NOT_FOUND) {
return(HA_ERR_NO_ACTIVE_RECORD);
} else if (error == (int) DB_ERROR) {
return(-1); /* unspecified error */
} else if (error == (int) DB_DEADLOCK) {
/* Since we rolled back the whole transaction, we must
tell it also to MySQL so that MySQL knows to empty the
cached binlog for this transaction */
if (thd) {
ha_rollback(thd);
}
return(HA_ERR_LOCK_DEADLOCK);
...
/*
Frees a possible InnoDB trx object associated with the current THD. */
static
int
innobase_close_connection(
/*==*/
/* out: 0 or error number */
THD*thd)/* in: handle to the MySQL thread of the user
whose resources should be free'd */
{
trx_t* trx;
trx = (trx_t*)thd-ha_data[innobase_hton.slot];
ut_a(trx);
if (trx-active_trans == 0
trx-conc_state != TRX_NOT_STARTED) {
sql_print_error(trx-active_trans == 0, but trx-conc_state !=
TRX_NOT_STARTED);
}
if (trx-conc_state != TRX_NOT_STARTED
global_system_variables.log_warnings)
sql_print_warning(MySQL is closing a connection that has an
active
InnoDB transaction. %lu row modifications
will
roll back.,
(ulong)trx-undo_no.low);
innobase_rollback_trx(trx);
trx_free_for_mysql(trx);
return(0);
}
Hmm... I need to check that the auto-increment code in ha_innodb.cc sets
trx-active_trans correctly. I guess you have an auto-inc column in your
table?
The deadlock output from
SHOW INNODB STATUS was so long, that it was truncated the SHOW
INNODB STATUS information somewhere in the middle of the deadlocked
rows output. The current transactions setting was completely missing
due to the truncation. I don't have access to the my.cnf from where I
am now, but I will send it on Monday once I get access. Lastly, there
were no errors printed to the .err log prior to the errors I sent.
Thank you so much for writing back. I do truly appreciate it! It is
very relieving to know it is not dangerous.
Best Regards,
Jason
Regards,
Heikki
On 12/30/06, Heikki Tuuri [EMAIL PROTECTED] wrote:
Jason,
Jason J. W. Williams wrote:
Hello Mr. Tuuri,
I'm sorry to bother you directly about this. I have had very little
luck finding anything on this in the forums or on Google and was
hoping you could help me understand a strange error message I received
from InnoDB (5.0.27). Any help would be very much appreciated. Thank
you in advance!
Best Regards,
Jason
---ERROR MESSAGE---
061228 19:02:55 [ERROR] trx-active_trans == 0, but trx-conc_state !=
TRX_NOT_STARTED
061228 19:02:55 [Warning] MySQL is closing a connection that has an
active InnoDB transaction. 0 row modifications will roll back.
the error itself does not sound dangerous.
But do you have an idea how you got this?
What is your my.cnf like?
Are there any other warnings or errors printed to the .err log prior to
this?
Best regards,
Heikki
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Bizarre InnoDB Error Message ( trx-active_trans == 0, but trx-conc_state != TRX_NOT_STARTED)
Jason,
I am Cc:ing the MySQL General mailing list, so that others who bump into
this bug can find this discussion.
Jason J. W. Williams wrote:
Mr. Tuuri,
We have a high degree of UPDATE/INSERT concurrency along with high
SELECTs. It causes a deadlock about once every 24 hours. In this case
a deadlock was associated with this event.
ha_innodb.cc in 5.0:
int
convert_error_code_to_mysql(
/**/
/* out: MySQL error code */
int error, /* in: InnoDB error code */
THD*thd)/* in: user thread handle or NULL */
{
if (error == DB_SUCCESS) {
return(0);
} else if (error == (int) DB_DUPLICATE_KEY) {
return(HA_ERR_FOUND_DUPP_KEY);
} else if (error == (int) DB_RECORD_NOT_FOUND) {
return(HA_ERR_NO_ACTIVE_RECORD);
} else if (error == (int) DB_ERROR) {
return(-1); /* unspecified error */
} else if (error == (int) DB_DEADLOCK) {
/* Since we rolled back the whole transaction, we must
tell it also to MySQL so that MySQL knows to empty the
cached binlog for this transaction */
if (thd) {
ha_rollback(thd);
}
return(HA_ERR_LOCK_DEADLOCK);
...
/*
Frees a possible InnoDB trx object associated with the current THD. */
static
int
innobase_close_connection(
/*==*/
/* out: 0 or error number */
THD*thd)/* in: handle to the MySQL thread of the user
whose resources should be free'd */
{
trx_t* trx;
trx = (trx_t*)thd-ha_data[innobase_hton.slot];
ut_a(trx);
if (trx-active_trans == 0
trx-conc_state != TRX_NOT_STARTED) {
sql_print_error(trx-active_trans == 0, but trx-conc_state !=
TRX_NOT_STARTED);
}
if (trx-conc_state != TRX_NOT_STARTED
global_system_variables.log_warnings)
sql_print_warning(MySQL is closing a connection that has an
active
InnoDB transaction. %lu row modifications
will
roll back.,
(ulong)trx-undo_no.low);
innobase_rollback_trx(trx);
trx_free_for_mysql(trx);
return(0);
}
Hmm... I need to check that the auto-increment code in ha_innodb.cc sets
trx-active_trans correctly. I guess you have an auto-inc column in your
table?
The deadlock output from
SHOW INNODB STATUS was so long, that it was truncated the SHOW
INNODB STATUS information somewhere in the middle of the deadlocked
rows output. The current transactions setting was completely missing
due to the truncation. I don't have access to the my.cnf from where I
am now, but I will send it on Monday once I get access. Lastly, there
were no errors printed to the .err log prior to the errors I sent.
Thank you so much for writing back. I do truly appreciate it! It is
very relieving to know it is not dangerous.
Best Regards,
Jason
Regards,
Heikki
On 12/30/06, Heikki Tuuri [EMAIL PROTECTED] wrote:
Jason,
Jason J. W. Williams wrote:
Hello Mr. Tuuri,
I'm sorry to bother you directly about this. I have had very little
luck finding anything on this in the forums or on Google and was
hoping you could help me understand a strange error message I received
from InnoDB (5.0.27). Any help would be very much appreciated. Thank
you in advance!
Best Regards,
Jason
---ERROR MESSAGE---
061228 19:02:55 [ERROR] trx-active_trans == 0, but trx-conc_state !=
TRX_NOT_STARTED
061228 19:02:55 [Warning] MySQL is closing a connection that has an
active InnoDB transaction. 0 row modifications will roll back.
the error itself does not sound dangerous.
But do you have an idea how you got this?
What is your my.cnf like?
Are there any other warnings or errors printed to the .err log prior to
this?
Best regards,
Heikki
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Bizarre InnoDB Error Message ( trx-active_trans == 0, but trx-conc_state != TRX_NOT_STARTED)
Hello, I noticed the error messages below in my MySQL error log and found them a bit perplexing. Can't find anything on them in the MySQL documentation. If anyone has any clue what they mean it is greatly appreciated. As a sidenote, SHOW INNODB STATUS completes, but only shows through the DEADLOCK section. It almost appears as if the deadlock listing is so long that it runs out of buffer and doesn't get to the TRANSACTIONS or other status sections. Thank you in advance! Best Regards, Jason ---ERROR MESSAGE--- 061228 19:02:55 [ERROR] trx-active_trans == 0, but trx-conc_state != TRX_NOT_STARTED 061228 19:02:55 [Warning] MySQL is closing a connection that has an active InnoDB transaction. 0 row modifications will roll back. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Problem INNODB error 995
Heikki: All servers have the auto upgrade on, so all the windows upgrade has been install. We have a raid 5 on all servers. Could that give a random error? We can try a give a low format to the disks. Osvaldo Sommer -Original Message- From: Heikki Tuuri [mailto:[EMAIL PROTECTED] Sent: Lunes, 06 de Marzo de 2006 11:50 p.m. To: mysql@lists.mysql.com Subject: Re: Problem INNODB error 995 Osvaldo, - Original Message - From: Osvaldo Sommer [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Tuesday, March 07, 2006 12:58 AM Subject: Problem INNODB error 995 --Boundary_(ID_PMYElD1sU13Il0ENO4J+aw) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit We have 4 windows 2003 server with mysql 4.0.12 install in each one. They have been working for about 1.5 years with no problem. Two weeks ago, in one server we lost the mysql service, and when we look the .err file it report a 995 error. We can star the service again and it works. In the two weeks the service has stop in the same server about 10 times, but none in the other server. We have the same applications working in each server. What can we do to stop the error? We even thought that we have a problem with windows, so we reinstall it, but the problem continue. Please help http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/ system_error_codes__500-999_.asp ERROR_OPERATION_ABORTED 995 The I/O operation has been aborted because of either a thread exit or an application request a few InnoDB users have reported this error number in the past 2 years. I have suspected that it is some bug in Windows or its device drivers, since InnoDB does not request aborts of I/O requests, nor do InnoDB's threads exit in the middle of an I/O operation. Did you upgrade the OS in that server before you started getting this error? Is the server identical to the other servers where mysqld works ok? The error might actually be a hardware problem. I have noticed that a hardware fault can produce strange error numbers in Linux. The same might hold for Windows. Osvaldo Sommer Best regards, Heikki Oracle Corp./Innobase Oy InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 268.2.0/275 - Release Date: 06/03/2006 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Problem INNODB error 995
Osvaldo, Osvaldo Sommer wrote: Heikki: All servers have the auto upgrade on, so all the windows upgrade has been install. this is interesting. Error 995 might then be a hardware problem. We have a raid 5 on all servers. Could that give a random error? We can try a give a low format to the disks. Osvaldo Sommer Best regards, Heikki Oracle Corp./Innobase Oy InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php -Original Message- From: Heikki Tuuri [mailto:[EMAIL PROTECTED] Sent: Lunes, 06 de Marzo de 2006 11:50 p.m. To: mysql@lists.mysql.com Subject: Re: Problem INNODB error 995 Osvaldo, - Original Message - From: Osvaldo Sommer [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Tuesday, March 07, 2006 12:58 AM Subject: Problem INNODB error 995 --Boundary_(ID_PMYElD1sU13Il0ENO4J+aw) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit We have 4 windows 2003 server with mysql 4.0.12 install in each one. They have been working for about 1.5 years with no problem. Two weeks ago, in one server we lost the mysql service, and when we look the .err file it report a 995 error. We can star the service again and it works. In the two weeks the service has stop in the same server about 10 times, but none in the other server. We have the same applications working in each server. What can we do to stop the error? We even thought that we have a problem with windows, so we reinstall it, but the problem continue. Please help http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/ system_error_codes__500-999_.asp ERROR_OPERATION_ABORTED 995 The I/O operation has been aborted because of either a thread exit or an application request a few InnoDB users have reported this error number in the past 2 years. I have suspected that it is some bug in Windows or its device drivers, since InnoDB does not request aborts of I/O requests, nor do InnoDB's threads exit in the middle of an I/O operation. Did you upgrade the OS in that server before you started getting this error? Is the server identical to the other servers where mysqld works ok? The error might actually be a hardware problem. I have noticed that a hardware fault can produce strange error numbers in Linux. The same might hold for Windows. Osvaldo Sommer Best regards, Heikki Oracle Corp./Innobase Oy InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Problem INNODB error 995
We have 4 windows 2003 server with mysql 4.0.12 install in each one. They have been working for about 1.5 years with no problem. Two weeks ago, in one server we lost the mysql service, and when we look the .err file it report a 995 error. We can star the service again and it works. In the two weeks the service has stop in the same server about 10 times, but none in the other server. We have the same applications working in each server. What can we do to stop the error? We even thought that we have a problem with windows, so we reinstall it, but the problem continue. Please help Osvaldo Sommer
Re: Problem INNODB error 995
Osvaldo, - Original Message - From: Osvaldo Sommer [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Tuesday, March 07, 2006 12:58 AM Subject: Problem INNODB error 995 --Boundary_(ID_PMYElD1sU13Il0ENO4J+aw) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit We have 4 windows 2003 server with mysql 4.0.12 install in each one. They have been working for about 1.5 years with no problem. Two weeks ago, in one server we lost the mysql service, and when we look the .err file it report a 995 error. We can star the service again and it works. In the two weeks the service has stop in the same server about 10 times, but none in the other server. We have the same applications working in each server. What can we do to stop the error? We even thought that we have a problem with windows, so we reinstall it, but the problem continue. Please help http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/system_error_codes__500-999_.asp ERROR_OPERATION_ABORTED 995 The I/O operation has been aborted because of either a thread exit or an application request a few InnoDB users have reported this error number in the past 2 years. I have suspected that it is some bug in Windows or its device drivers, since InnoDB does not request aborts of I/O requests, nor do InnoDB's threads exit in the middle of an I/O operation. Did you upgrade the OS in that server before you started getting this error? Is the server identical to the other servers where mysqld works ok? The error might actually be a hardware problem. I have noticed that a hardware fault can produce strange error numbers in Linux. The same might hold for Windows. Osvaldo Sommer Best regards, Heikki Oracle Corp./Innobase Oy InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: reinstall mysql show innodb error
Hello. Check the correct values in your configuration file for the size of the log files. If you're sure that shutdown of the server was clean, you can remove log files, InnoDB will recreate them (I suggest you to make a backup of the old log files just in case something went wrong in the shutdown and you need them to recover the tablespace). See: http://dev.mysql.com/doc/refman/5.0/en/adding-and-removing.html http://dev.mysql.com/doc/refman/5.0/en/innodb-start.html http://dev.mysql.com/doc/refman/5.0/en/innodb-configuration.html Hi, Our mysql 4.1 database server on win2000 was uninstalled by mistake, but reinstalled , caused the follow errors: InnoDB: Error: log file .\ib_logfile0 is of different size 0 14680064 bytes InnoDB: than specified in the .cnf file 0 10485760 bytes! 051020 19:30:42 [ERROR] Can't init databases 051020 19:30:42 [ERROR] Abortingwang shuming wrote: -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
reinstall mysql show innodb error
Hi, Our mysql 4.1 database server on win2000 was uninstalled by mistake, but reinstalled , caused the follow errors: InnoDB: Error: log file .\ib_logfile0 is of different size 0 14680064 bytes InnoDB: than specified in the .cnf file 0 10485760 bytes! 051020 19:30:42 [ERROR] Can't init databases 051020 19:30:42 [ERROR] Aborting Best regard! Shuming Wang Xtech Company limited Room 17G,17/F,Plaza 2, Tiancheng Building,No 96 Longkouxi Road, Tianhe Guangzhou,Guangdong,China http://www.xtech.com.cn http://www.87595959.com Email: [EMAIL PROTECTED] QQ:370783763 , MSN: [EMAIL PROTECTED] Tel:86-20-87595959---2001,2002 Fax:86-20-87576779
Re: reinstall mysql show innodb error
Shuming, http://dev.mysql.com/doc/refman/5.0/en/innodb-configuration.html you have to specify the right size for: innodb_log_file_size=14M in your my.cnf or my.ini. Please also check from: C:\Program Files\MySQL\MySQL Server 4.1\data how many ib_logfiles you have. If you have more than 2, specify also: innodb_log_files_in_group=... Regards, Heikki Oracle/Innobase - Original Message - From: wang shuming [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Thursday, October 20, 2005 3:05 PM Subject: reinstall mysql show innodb error --=_Part_890_17924509.1129809525031 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, Our mysql 4.1 database server on win2000 was uninstalled by mistake, but reinstalled , caused the follow errors: InnoDB: Error: log file .\ib_logfile0 is of different size 0 14680064 byte= s InnoDB: than specified in the .cnf file 0 10485760 bytes! 051020 19:30:42 [ERROR] Can't init databases 051020 19:30:42 [ERROR] Aborting Best regard! Shuming Wang Xtech Company limited Room 17G,17/F,Plaza 2, Tiancheng Building,No 96 Longkouxi Road, Tianhe Guangzhou,Guangdong,China http://www.xtech.com.cn http://www.87595959.com Email: [EMAIL PROTECTED] QQ:370783763 , MSN: [EMAIL PROTECTED] Tel:86-20-87595959---2001,2002 Fax:86-20-87576779 --=_Part_890_17924509.1129809525031-- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: InnoDB error unable to create temporary file
Hi Joerg et all, [snip] You said this is Solaris. AFAIK, Solaris uses the same disk area for /tmp and paging, so the available space for files in /tmp may vary even without files being manipulated. I propose you set TMPDIR to point to some other disk area. We're on Solaris, yes. I suspected that paging might be a cause so I reconfigured our QAS server (which also shows the errors) to use /var/mysql in stead of /tmp. But the problem persists. It is always at the same time: when cron runs a script that obtains table info. Everything else seems to work fine (i.e. nothing breaks), so I think I'll leave it till it's time to upgrade. Kind regards, -- Martijn ASML ITMS Webcenter / Application Support -- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. ASML is neither liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB error unable to create temporary file
Hi Martijn, all! Martijn van den Burg wrote (reordered) On Wednesday 28 September 2005 20:10, Gleb Paharenko wrote: Martijn van den Burg wrote: Hi list, After the most recent reboot (which we used to increase the ulimit/open_files_limit on our Solaris 8 machine running 4.1.10-log), the following message has started to appear in the errorlog: InnoDB: Error: unable to create temporary file; errno: 2 [[...]] TMPDIR is not set explicitly, and the first 'fallback' directory in that case is '/tmp', which is accessible and has enough diskspace. At least, when I checked this morning. You said this is Solaris. AFAIK, Solaris uses the same disk area for /tmp and paging, so the available space for files in /tmp may vary even without files being manipulated. I propose you set TMPDIR to point to some other disk area. HTH, Jörg -- Joerg Bruehe, Senior Production Engineer MySQL AB, www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB error unable to create temporary file
Hi Jörg, On Thursday 29 September 2005 12:09, you wrote: Hi Martijn, all! Martijn van den Burg wrote (reordered) On Wednesday 28 September 2005 20:10, Gleb Paharenko wrote: Martijn van den Burg wrote: Hi list, After the most recent reboot (which we used to increase the ulimit/open_files_limit on our Solaris 8 machine running 4.1.10-log), the following message has started to appear in the errorlog: InnoDB: Error: unable to create temporary file; errno: 2 [[...]] TMPDIR is not set explicitly, and the first 'fallback' directory in that case is '/tmp', which is accessible and has enough diskspace. At least, when I checked this morning. You said this is Solaris. AFAIK, Solaris uses the same disk area for /tmp and paging, so the available space for files in /tmp may vary even without files being manipulated. I propose you set TMPDIR to point to some other disk area. 'df' indeed shows that /tmp is the swap partition, although mysql can still create files there (i.e. it's not like Linux's partition type 82, which you can't write to normally IIRC). I'll check swapping. Unfortunately I'll have to reboot to change TMPDIR, and the users won't like that :( Regards, -- /Martijn -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
InnoDB error unable to create temporary file
Hi list, After the most recent reboot (which we used to increase the ulimit/open_files_limit on our Solaris 8 machine running 4.1.10-log), the following message has started to appear in the errorlog: InnoDB: Error: unable to create temporary file; errno: 2 I have searched google and the lists for this error, but couldn't find anything substantial, other then that it might have to do with the setting of tmpdir (which is unset). Any ideas? Regards, Martijn -- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. ASML is neither liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB error unable to create temporary file
Hello. Maybe some directory doesn't exist in the path where MySQL stores temporary files. See: http://dev.mysql.com/doc/mysql/en/temporary-files.html Martijn van den Burg wrote: Hi list, After the most recent reboot (which we used to increase the ulimit/open_files_limit on our Solaris 8 machine running 4.1.10-log), the following message has started to appear in the errorlog: InnoDB: Error: unable to create temporary file; errno: 2 I have searched google and the lists for this error, but couldn't find anything substantial, other then that it might have to do with the setting of tmpdir (which is unset). Any ideas? Regards, Martijn -- =0D The information contained in this communication and any attachments is co= nfidential and may be privileged, and is for the sole use of the intended= recipient(s). Any unauthorized review, use, disclosure or distribution i= s prohibited. If you are not the intended recipient, please notify the se= nder immediately by replying to this message and destroy all copies of th= is message and any attachments. ASML is neither liable for the proper and= complete transmission of the information contained in this communication= , nor for any delay in its receipt. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB error unable to create temporary file
Hi, Thanks for your reply. TMPDIR is not set explicitly, and the first 'fallback' directory in that case is '/tmp', which is accessible and has enough diskspace. At least, when I checked this morning. The error occurred in the night, maybe there were other processes that filled the directory with temporary files. I doubt that, however. I may need to set up some disk-usage logging. On Wednesday 28 September 2005 20:10, Gleb Paharenko wrote: Hello. Maybe some directory doesn't exist in the path where MySQL stores temporary files. See: http://dev.mysql.com/doc/mysql/en/temporary-files.html Martijn van den Burg wrote: Hi list, After the most recent reboot (which we used to increase the ulimit/open_files_limit on our Solaris 8 machine running 4.1.10-log), the following message has started to appear in the errorlog: InnoDB: Error: unable to create temporary file; errno: 2 I have searched google and the lists for this error, but couldn't find anything substantial, other then that it might have to do with the setting of tmpdir (which is unset). Any ideas? Regards, -- /Martijn -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
InnoDB: Error: tablespace size stored in header is 640000 pages, but the sum of data file sizes is 1056000 pages
|Dear All, As subject, Actually i've been ever meet this case when i see : InnoDB: Error: tablespace size stored in header is 877184 pages, but InnoDB: the sum of data file sizes is 953856 pages And Mr. Heikki tell me to do these steps: (953856 - 877184) / 64 = 1198 MB 1) Stop the mysqld server. 2) Add a new 1198M ibdata file at the end of innodb_data_file_path. 3) When you start mysqld, InnoDB will write that new ibdata file full of zeros, and increment the tablespace size stored in the tablespace header by 1198M. 4) Then stop the mysqld server, remove the extra 1198M ibdata file from innodb_data_file_path and delete that extra ibdata file. 5) Start mysqld again. 6) Voila! Now the tablespace size stored in the tablespace header agrees with the combined size of the files in innodb_data_file_path! BUT With my case (1056000-64) / 64 = 6500 Mbyte It's bigger than a single file in my Linux (2 Gbyte). My InnoDB data path is: innodb_data_file_path = /rsv1/ibdata1:2000M;/rsv1/ibdata2:2000M;/rsv1/ibdata3:2000M;/rsv1/ibdata4:2000M;/rsv1/ibdata5:500M;/r sv3/ibdata6:2000M;/rsv3/ibdata7:2000M;/rsv3/ibdata8:2000M;/rsv3/ibdata9:2000M; Any solutions? | |-- Regards, Ady Wicaksono HP: +628562208680 |
Re: InnoDB: Error: tablespace size stored in header is 640000 pages, but the sum of data file sizes is 1056000 pages
Reply by me. How stupid i'm :( I've finished this warning error problem by adding 4 files -- 3 file each 3 Gbyte and 1 file 500Mbyte Thx mr. heiiki :D Sorry Ady Wicaksono wrote: |Dear All, As subject, Actually i've been ever meet this case when i see : InnoDB: Error: tablespace size stored in header is 877184 pages, but InnoDB: the sum of data file sizes is 953856 pages And Mr. Heikki tell me to do these steps: (953856 - 877184) / 64 = 1198 MB 1) Stop the mysqld server. 2) Add a new 1198M ibdata file at the end of innodb_data_file_path. 3) When you start mysqld, InnoDB will write that new ibdata file full of zeros, and increment the tablespace size stored in the tablespace header by 1198M. 4) Then stop the mysqld server, remove the extra 1198M ibdata file from innodb_data_file_path and delete that extra ibdata file. 5) Start mysqld again. 6) Voila! Now the tablespace size stored in the tablespace header agrees with the combined size of the files in innodb_data_file_path! BUT With my case (1056000-64) / 64 = 6500 Mbyte It's bigger than a single file in my Linux (2 Gbyte). My InnoDB data path is: innodb_data_file_path = /rsv1/ibdata1:2000M;/rsv1/ibdata2:2000M;/rsv1/ibdata3:2000M;/rsv1/ibdata4:2000M;/rsv1/ibdata5:500M;/r sv3/ibdata6:2000M;/rsv3/ibdata7:2000M;/rsv3/ibdata8:2000M;/rsv3/ibdata9:2000M; Any solutions? | |-- Regards, Ady Wicaksono HP: +628562208680 | -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
InnoDB: Error: tablespace
Hi list, I have the following error in a MySQL server: 050617 09:16:35 mysqld started InnoDB: Error: tablespace size stored in header is 8660992 pages, but InnoDB: the sum of data file sizes is only 6432768 pages 050617 9:16:40 InnoDB: Started /usr/sbin/mysqld-max: ready for connections And here is the background: This server is setting up as a slave server, We configured it via master's full backup, so we copied all the directories of the data bases, ibdata files and its config file almost is equals to the master config file the only differences are the ibdata_path. When the server starts, displays the previous message. I checked the size of the master's ibdata files versus the slave's and both files are the same size. I did a count(*) from all the tables, check table of all the tables and it seems that all the tables are fine. Any suggestions to correct the slave message error. Thanks in advanced and greetings -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
InnoDb ERROR
Hi, I'm getting the following error in my logfile 050325 15:44:57 InnoDB: ERROR: the age of the last checkpoint is 120801862, InnoDB: which exceeds the log group capacity 120792269. InnoDB: If you are using big BLOB or TEXT rows, you must set the InnoDB: combined size of log files at least 10 times bigger than the InnoDB: largest such row. Can someone point me to a resource where this error is explained and how to fix? Also, is this serious? could i have data corruption at all? Thanks, Marc Dumontier -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: innodb error 995
Ben, - Original Message - From: Ben Kutsch [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Tuesday, February 15, 2005 1:55 AM Subject: innodb error 995 Hi I'm running version MySQL 4.0.20a-debug windows server 2003 on a dedicated database server with an external SCSI RAID array with a 1 TB of disk space (over 400 GIG free) 1 gig of RAM basic settings key buffer 512 MB sort Buffer 32 Mb innof db Buffer Pool Size 512 MB my innodb datafile is about 200 gig is size and I have 6 innodb databses. 3 are very large 40+ gigs with about 800 million records. The other 3 are very small few MB is size. Every two weeks I rebuild one of the large db and use the other 2 as backups. This configuration as worked fine for the last 2 months. I was in the process of rebuilding one of the large databases when I got the following error. 050214 16:46:56 InnoDB: Operating system error number 995 in a file operation. InnoDB: See http://www.innodb.com/ibman.php for installation help. InnoDB: See section 13.2 at http://www.innodb.com/ibman.php InnoDB: about operating system error numbers. InnoDB: File name .\ibdata1 InnoDB: File operation call: 'Windows aio'. InnoDB: Cannot continue operation. after restarting mysql, innodb rolled back my tables in the db that crashed and the rest of my data seems fine. I have googled around and there seems to be some info that this errors is some kind windows driver. Is there any more info regarding this error? a few users have reported this Windows error. I believe it is a bug in Windows. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/system_error_codes__500-999_.asp ERROR_OPERATION_ABORTED 995 The I/O operation has been aborted because of either a thread exit or an application request. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/base/readfileex.asp The ReadFileEx function may fail if there are too many outstanding asynchronous I/O requests. In the event of such a failure, GetLastError can return ERROR_INVALID_USER_BUFFER or ERROR_NOT_ENOUGH_MEMORY. To cancel all pending asynchronous I/O operations, use the CancelIo function. This function only cancels operations issued by the calling thread for the specified file handle. I/O operations that are canceled complete with the error ERROR_OPERATION_ABORTED. But InnoDB does not call CancelIo. Do you happen to have a Microsoft support contract? You could report this to Microsoft. Any help would be useful. Thank you -Ben -- Ben Kutsch Developer Suite 304, 121 South 13th ST Dept. of Computer Science and Eng. phone: (402) 472-2340 University of Nebraska-Lincoln fax: (402) 472-3135 Lincoln NE 68588-0115 email: [EMAIL PROTECTED] http://nadss.unl.edu Best regards, Heikki Tuuri Innobase Oy Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php Order MySQL Network from http://www.mysql.com/network/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
innodb error 995
Hi I'm running version MySQL 4.0.20a-debug windows server 2003 on a dedicated database server with an external SCSI RAID array with a 1 TB of disk space (over 400 GIG free) 1 gig of RAM basic settings key buffer 512 MB sort Buffer 32 Mb innof db Buffer Pool Size 512 MB my innodb datafile is about 200 gig is size and I have 6 innodb databses. 3 are very large 40+ gigs with about 800 million records. The other 3 are very small few MB is size. Every two weeks I rebuild one of the large db and use the other 2 as backups. This configuration as worked fine for the last 2 months. I was in the process of rebuilding one of the large databases when I got the following error. 050214 16:46:56 InnoDB: Operating system error number 995 in a file operation. InnoDB: See http://www.innodb.com/ibman.php for installation help. InnoDB: See section 13.2 at http://www.innodb.com/ibman.php InnoDB: about operating system error numbers. InnoDB: File name .\ibdata1 InnoDB: File operation call: 'Windows aio'. InnoDB: Cannot continue operation. after restarting mysql, innodb rolled back my tables in the db that crashed and the rest of my data seems fine. I have googled around and there seems to be some info that this errors is some kind windows driver. Is there any more info regarding this error? Any help would be useful. Thank you -Ben -- Ben Kutsch Developer Suite 304, 121 South 13th ST Dept. of Computer Science and Eng. phone: (402) 472-2340 University of Nebraska-Lincoln fax: (402) 472-3135 Lincoln NE 68588-0115 email: [EMAIL PROTECTED] http://nadss.unl.edu -- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB: Error: tablespace size stored in header is 17024 pages,
Ian, - Original Message - From: Ian Grant [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Wednesday, January 05, 2005 4:47 PM Subject: Re: InnoDB: Error: tablespace size stored in header is 17024 pages, Dear Heikki Many thanks for your reply. On Mon, 3 Jan 2005 20:41:22 +0200 Heikki Tuuri [EMAIL PROTECTED] wrote: are you sure that you copied the complete ibdata1 file to the new place? It is strange how 7 MB can be missing from the file end. I have just checked the tar file I used to do the transfer and sure enough, the file length is right there, but not in my database directory. Obviously I didn't notice any error when I unpacked it, but it is definitely short now. hmm... a bug in tar? ... Then I added it to the start of the tablespace path in my.cnf by changing innodb_data_file_path = ibdata1:10M:autoextend to innodb_data_file_path = ibdata2:7M;ibdata1:10M:autoextend You have to add new data files to the end of the line, not to the start. Please follow the instructions at http://dev.mysql.com/doc/mysql/en/Adding_and_removing.html Then I shut down: 050105 14:25:57 [Note] /local/own-1/rt/rt-3.2.2/libexec/mysqld: Normal shutdown 050105 14:25:57 InnoDB: Starting shutdown... 050105 14:26:01 InnoDB: Shutdown completed; log sequence number 0 407778847 050105 14:26:01 [Note] /local/own-1/rt/rt-3.2.2/libexec/mysqld: Shutdown complete 050105 14:26:01 mysqld ended ... and restarted MySQL but I got an error: 050105 14:26:04 mysqld started 050105 14:26:05 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 050105 14:26:05 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 407778847. InnoDB: Doing recovery: scanned up to log sequence number 0 407778847 InnoDB: Page directory corruption: supremum not pointed to followed by a page dump and a stack trace. I removed the entry for the new file in the data file path and it has started as it did before. Have I misunderstood your instructions? Best regards, Heikki Tuuri Innobase Oy Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB: Error: tablespace size stored in header is 17024 pages,
On Thu, 6 Jan 2005 11:30:33 +0200 Heikki Tuuri [EMAIL PROTECTED] wrote: innodb_data_file_path = ibdata2:7M;ibdata1:10M:autoextend You have to add new data files to the end of the line, not to the start. Please follow the instructions at http://dev.mysql.com/doc/mysql/en/Adding_and_removing.html Thanks. I realised this when I woke up in the middle of the night! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB: Error: tablespace size stored in header is 17024 pages, but
Dear Heikki Many thanks for your reply. On Mon, 3 Jan 2005 20:41:22 +0200 Heikki Tuuri [EMAIL PROTECTED] wrote: are you sure that you copied the complete ibdata1 file to the new place? It is strange how 7 MB can be missing from the file end. I have just checked the tar file I used to do the transfer and sure enough, the file length is right there, but not in my database directory. Obviously I didn't notice any error when I unpacked it, but it is definitely short now. So that (partly) explains what went wrong ... however we have new data in the database now so it is too late to go back tho that copy. What does the old .err log contain? Any message about disk space running out? The error below probably has not corrupted your tablespace. Best to run CHECK TABLE on some of your tables, though. I did that on all tables and they all show they are OK. When ibdata files are created, they are initially written full of zeros. You can probably fix the error by using another mysqld installation (or any method that makes a 7 MB zero-filled file) to create a new ibdata2 file that is 7 MB in size, and add that to the tablespace. Look from http://dev.mysql.com/doc/mysql/en/Adding_and_removing.html how to edit my.cnf then. Thanks. This is what I did: First I created ibdata2 with the command dd if=/dev/zero bs=1M count=7 of=ibdata2 Then I added it to the start of the tablespace path in my.cnf by changing innodb_data_file_path = ibdata1:10M:autoextend to innodb_data_file_path = ibdata2:7M;ibdata1:10M:autoextend Then I shut down: 050105 14:25:57 [Note] /local/own-1/rt/rt-3.2.2/libexec/mysqld: Normal shutdown 050105 14:25:57 InnoDB: Starting shutdown... 050105 14:26:01 InnoDB: Shutdown completed; log sequence number 0 407778847 050105 14:26:01 [Note] /local/own-1/rt/rt-3.2.2/libexec/mysqld: Shutdown complete 050105 14:26:01 mysqld ended ... and restarted MySQL but I got an error: 050105 14:26:04 mysqld started 050105 14:26:05 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 050105 14:26:05 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 407778847. InnoDB: Doing recovery: scanned up to log sequence number 0 407778847 InnoDB: Page directory corruption: supremum not pointed to followed by a page dump and a stack trace. I removed the entry for the new file in the data file path and it has started as it did before. Have I misunderstood your instructions? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB: Error: tablespace size stored in header is 17024 pages, but
Ian, are you sure that you copied the complete ibdata1 file to the new place? It is strange how 7 MB can be missing from the file end. What does the old .err log contain? Any message about disk space running out? The error below probably has not corrupted your tablespace. Best to run CHECK TABLE on some of your tables, though. When ibdata files are created, they are initially written full of zeros. You can probably fix the error by using another mysqld installation (or any method that makes a 7 MB zero-filled file) to create a new ibdata2 file that is 7 MB in size, and add that to the tablespace. Look from http://dev.mysql.com/doc/mysql/en/Adding_and_removing.html how to edit my.cnf then. Best regards, Heikki Tuuri Innobase Oy Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php Order MySQL technical support from https://order.mysql.com/ - Original Message - From: Ian Grant [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Friday, December 31, 2004 5:26 PM Subject: InnoDB: Error: tablespace size stored in header is 17024 pages, but Dear MySQL people I have a question regarding the error: InnoDB: Error: tablespace size stored in header is 17024 pages, but InnoDB: the sum of data file sizes is only 16576 pages which appeared when I upgraded from 4.0.7 to 4.1.7. Somehow I am 448 pages (7M) short of table space. Can I fix this using the procedure outlined in http://archives.neohapsis.com/archives/mysql/2004-q3/3723.html or should I do a dump/restore? Here are the gory details: I was running MySQL Ver 12.22 Distrib 4.0.17 with the following /etc/my.cnf file: [mysqld] user=www datadir=/local/own-1/rt/mysql-data innodb_data_file_path = ibdata1:10M:autoextend Then I built a new MySQL Ver 14.7 Distrib 4.1.7 and decided to do binary logging so I changed /etc/my.cnf to read [mysqld] user=rt datadir=/local/own-1/rt/mysql-data innodb_data_file_path = ibdata1:10M:autoextend # Set buffer pool size to 50-80% of memory set-variable = innodb_buffer_pool_size=512M set-variable = innodb_additional_mem_pool_size=10M # Set the log file size to about 25% of the buffer pool size set-variable = innodb_log_file_size=64M set-variable = innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 # Turn on binary logging and sync set-variable = log_bin=1 set-variable = sync_binlog=1 Then I shut down the old database, copied the data files and deleted the ib_logfile* files and this is what I got in the logs on starting 4.1.7. I was a bit surprised at the 'not shut down normally' message, but hey. ... 041229 14:04:51 mysqld started 041229 14:04:51 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... 041229 14:04:53 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... 041229 14:04:55 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Resetting space id's in the doublewrite buffer 041229 14:04:55 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 405584396. InnoDB: Doing recovery: scanned up to log sequence number 0 405584396 041229 14:04:55 InnoDB: Flushing modified pages from the buffer pool... 041229 14:04:55 InnoDB: Started; log sequence number 0 405584396 InnoDB: You are upgrading to an InnoDB version which allows multiple InnoDB: tablespaces. Wait that purge and insert buffer merge run to InnoDB: completion... InnoDB: Full purge and insert buffer merge completed. InnoDB: You have now successfully upgraded to the multiple tablespaces InnoDB: format. You should NOT DOWNGRADE to an earlier version of InnoDB: InnoDB! But if you absolutely need to downgrade, see InnoDB: http://dev.mysql.com/doc/mysql/en/Multiple_tablespaces.html InnoDB: for instructions. 041229 14:04:57 [Warning] mysql.user table is not updated to new password format ; Disabling new password usage until mysql_fix_privilege_tables is run 041229 14:04:57 [Warning] Can't open and lock time zone table: Table 'mysql.time _zone_leap_second' doesn't exist trying to live without them /local/own-1/rt/rt-3.2.2/libexec/mysqld: ready for connections. Version: '4.1.7-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution But now when I start the database I get: 041230 10:04:37 mysqld started InnoDB: Error: tablespace size stored in header is 17024 pages, but InnoDB: the sum of data file sizes is only 16576 pages 041230 10:04:39 InnoDB: Started; log sequence number 0 405783741 041230 10:04:39 [Warning] mysql.user table is not updated to new password format
InnoDB: Error: tablespace size stored in header is 17024 pages, but ...
Dear MySQL people I have a question regarding the error: InnoDB: Error: tablespace size stored in header is 17024 pages, but InnoDB: the sum of data file sizes is only 16576 pages which appeared when I upgraded from 4.0.7 to 4.1.7. Somehow I am 448 pages (7M) short of table space. Can I fix this using the procedure outlined in http://archives.neohapsis.com/archives/mysql/2004-q3/3723.html or should I do a dump/restore? Here are the gory details: I was running MySQL Ver 12.22 Distrib 4.0.17 with the following /etc/my.cnf file: [mysqld] user=www datadir=/local/own-1/rt/mysql-data innodb_data_file_path = ibdata1:10M:autoextend Then I built a new MySQL Ver 14.7 Distrib 4.1.7 and decided to do binary logging so I changed /etc/my.cnf to read [mysqld] user=rt datadir=/local/own-1/rt/mysql-data innodb_data_file_path = ibdata1:10M:autoextend # Set buffer pool size to 50-80% of memory set-variable = innodb_buffer_pool_size=512M set-variable = innodb_additional_mem_pool_size=10M # Set the log file size to about 25% of the buffer pool size set-variable = innodb_log_file_size=64M set-variable = innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 # Turn on binary logging and sync set-variable = log_bin=1 set-variable = sync_binlog=1 Then I shut down the old database, copied the data files and deleted the ib_logfile* files and this is what I got in the logs on starting 4.1.7. I was a bit surprised at the 'not shut down normally' message, but hey. ... 041229 14:04:51 mysqld started 041229 14:04:51 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... 041229 14:04:53 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... 041229 14:04:55 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Resetting space id's in the doublewrite buffer 041229 14:04:55 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 405584396. InnoDB: Doing recovery: scanned up to log sequence number 0 405584396 041229 14:04:55 InnoDB: Flushing modified pages from the buffer pool... 041229 14:04:55 InnoDB: Started; log sequence number 0 405584396 InnoDB: You are upgrading to an InnoDB version which allows multiple InnoDB: tablespaces. Wait that purge and insert buffer merge run to InnoDB: completion... InnoDB: Full purge and insert buffer merge completed. InnoDB: You have now successfully upgraded to the multiple tablespaces InnoDB: format. You should NOT DOWNGRADE to an earlier version of InnoDB: InnoDB! But if you absolutely need to downgrade, see InnoDB: http://dev.mysql.com/doc/mysql/en/Multiple_tablespaces.html InnoDB: for instructions. 041229 14:04:57 [Warning] mysql.user table is not updated to new password format ; Disabling new password usage until mysql_fix_privilege_tables is run 041229 14:04:57 [Warning] Can't open and lock time zone table: Table 'mysql.time _zone_leap_second' doesn't exist trying to live without them /local/own-1/rt/rt-3.2.2/libexec/mysqld: ready for connections. Version: '4.1.7-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution But now when I start the database I get: 041230 10:04:37 mysqld started InnoDB: Error: tablespace size stored in header is 17024 pages, but InnoDB: the sum of data file sizes is only 16576 pages 041230 10:04:39 InnoDB: Started; log sequence number 0 405783741 041230 10:04:39 [Warning] mysql.user table is not updated to new password format ; Disabling new password usage until mysql_fix_privilege_tables is run 041230 10:04:39 [Warning] Can't open and lock time zone table: Table 'mysql.time _zone_leap_second' doesn't exist trying to live without them /local/own-1/rt/rt-3.2.2/libexec/mysqld: ready for connections. Version: '4.1.7-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL crashed InnoDB: Error: semaphore wait has lasted 600 seconds
Hi, MySQL 4.0.16 running on Red Hat Linux release 8.0 with 4 Intel XEON 2.40 GHz with InnoDB tables. This is the stack trace : 0x81077c6 handle_segfault + 474 0x4002a929 _end + 935891041 0x8272ff8 sync_array_print_long_waits + 580 0x81a7328 srv_error_monitor_thread + 96 0x40024ada _end + 935866898 0x402868c7 _end + 938364927 Error message from log : InnoDB: Warning: a long semaphore wait: --Thread 294923 has waited at ../../innobase/include/btr0btr.ic line 28 for 625.00 seconds the semaphore: X-lock on RW-latch at 40cb26e4 created in file buf0buf.c line 444 a writer (thread id 294923) has reserved it in mode exclusive number of readers 0, waiters flag 1 Last time read locked in file btr0sea.c line 753 Last time write locked in file buf0buf.c line 1404 InnoDB: Error: semaphore wait has lasted 600 seconds InnoDB: We intentionally crash the server, because it appears to be hung. 040812 23:17:29 InnoDB: Assertion failure in thread 98311 in file sync0arr.c line 934 InnoDB: Failing assertion: 0 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8388600 read_buffer_size=131072 max_used_connections=53 max_connections=200 threads_connected=17 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 443390 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xbedff518, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x81077c6 0x4002a929 0x8272ff8 0x81a7328 0x40024ada 0x402868c7 New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://www.mysql.com/doc/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 2 mysqld process hanging, pid 810 - killed mysqld process hanging, pid 810 - killed 040812 23:17:29 mysqld restarted 040812 23:17:29 Can't start server: Bind on TCP/IP port: Address already in use 040812 23:17:29 Do you already have another mysqld server running on port: 3306 ? 040812 23:17:29 Aborting 040812 23:17:29 /usr/kasenna/mysql/bin/mysqld: Shutdown Complete 040812 23:17:29 mysqld ended 040816 13:55:44 mysqld started 040816 13:55:44 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 252191979 InnoDB: Doing recovery: scanned up to log sequence number 0 252191979 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1 row operations to undo InnoDB: Trx id counter is 0 379596032 InnoDB: Starting rollback of uncommitted transactions InnoDB: Rolling back trx with id 0 379591339, 1 rows to undo InnoDB: Rolling back of trx id 0 379591339 completed InnoDB: Rollback of uncommitted transactions completed 040816 13:55:44 InnoDB: Flushing modified pages from the buffer pool... 040816 13:55:44 InnoDB: Started /usr/kasenna/mysql/bin/mysqld: ready for connections. Version: '4.0.16' socket: '/usr/kasenna/mysql/tmp/mysql.sock' port: 3306 Any insight would be most appreciated. datta Kasenna Inc, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
InnoDB error
Hello, I started getting this error since I upgraded from mysql 4.0.13 to 4.0.15: 030918 7:17:13 InnoDB: Error: page 12412 log sequence number 0 670697749 InnoDB: is in the future! Current system log sequence number 0 186563990. InnoDB: Your database may be corrupt. any idea how to get rid of this? thanks -- -- Gustavo Baratto - Systems Engineer [EMAIL PROTECTED] * (604) 638-2525 ext. 408 Technical support web-site: http://support.superb.net Superb Internet Corp. Ahead of the Rest - -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB Error ib_logfile0 of different size
On Tue, 26 Aug 2003, Heikki Tuuri wrote: Asif, now take the old log files from the safe place and put them back! That will save your data. The instructions about changing the size of the log files are the following: http://www.innodb.com/ibman.html#Adding_and_removing If you want to change the number or the size of your InnoDB log files, you have to shut down MySQL and make sure that it shuts down without errors. Then copy the old log files into a safe place just in case something went wrong in the shutdown and you will need them to recover the database. Delete then the old log files from the log file directory, edit my.cnf, and start MySQL again. InnoDB will tell you at the startup that it is creating new log files. That worked, thanks a lot. Now I am wondering if their is any other modification on my system with 4x450Mhz, 4gig RAM, mysql 4.0.13 that I should look into to improve the performance Here is my cnf file look like [client] #password = your_password port= 3306 socket = /tmp/mysql.sock [mysqld] port= 3306 socket = /tmp/mysql.sock skip-locking key_buffer = 384M max_allowed_packet = 1M table_cache = 512 sort_buffer_size = 2M read_buffer_size = 2M myisam_sort_buffer_size = 64M thread_cache = 8 query_cache_size = 32M # Try number of CPU's*2 for thread_concurrency thread_concurrency = 8 #skip-networking #log-bin server-id = 1 # Uncomment the following if you are using InnoDB tables innodb_data_home_dir = /usr/local/mysql/data/ innodb_data_file_path = ibdata1:1882M;ibdata2:10M:autoextend innodb_log_group_home_dir = /usr/local/mysql/data/ innodb_log_arch_dir = /usr/local/mysql/data/ innodb_buffer_pool_size = 384M innodb_additional_mem_pool_size = 20M innodb_log_file_size = 100M innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 [mysqldump] quick max_allowed_packet = 16M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates Also not sure what I should do here, keep the comments? [isamchk] key_buffer = 256M sort_buffer_size = 256M read_buffer = 2M write_buffer = 2M [myisamchk] key_buffer = 256M sort_buffer_size = 256M read_buffer = 2M write_buffer = 2M [mysqlhotcopy] interactive-timeout I am doing any replication. I have just one server. I am using MyISAM and InnoDB Type tables and Row formats were Dynamic Thanks again -- Asif Iqbal http://pgpkeys.mit.edu:11371/pks/lookup?op=getsearch=0x8B686E08 There's no place like 127.0.0.1 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
InnoDB Error ib_logfile0 of different size
I already have mysql 4.0.13 running with all InnoDB tables. I am trying to use my-huge.cnf since I have 4 gig RAM with 4 x 450 Mhz processes In my MySQL data directory I have two ib_logfile files -rw-rw 1 mysqlmysql5242880 Aug 26 01:55 ib_logfile0 -rw-rw 1 mysqlmysql5242880 Aug 25 19:03 ib_logfile1 Now if I add this line in my cnf file (as recommended by my-huge.cnf) innodb_log_file_size = 100M I get the following error InnoDB: Error: log file /usr/local/mysql/data/ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 104857600 bytes! 030826 1:42:15 Can't init databases 030826 1:42:15 Aborting So as a workaround I commented the innodb_log_file_size. But I really don't like this solution. Is there a better solution ? Thanks -- Asif Iqbal http://pgpkeys.mit.edu:11371/pks/lookup?op=getsearch=0x8B686E08 There's no place like 127.0.0.1 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB Error ib_logfile0 of different size
Asif Iqbal [EMAIL PROTECTED] wrote: I already have mysql 4.0.13 running with all InnoDB tables. I am trying to use my-huge.cnf since I have 4 gig RAM with 4 x 450 Mhz processes In my MySQL data directory I have two ib_logfile files -rw-rw 1 mysqlmysql5242880 Aug 26 01:55 ib_logfile0 -rw-rw 1 mysqlmysql5242880 Aug 25 19:03 ib_logfile1 Now if I add this line in my cnf file (as recommended by my-huge.cnf) innodb_log_file_size = 100M I get the following error InnoDB: Error: log file /usr/local/mysql/data/ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 104857600 bytes! 030826 1:42:15 Can't init databases 030826 1:42:15 Aborting So as a workaround I commented the innodb_log_file_size. But I really don't like this solution. Is there a better solution ? Move old log files to the safe place. Edit my.cnf and then start MySQL server. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB Error ib_logfile0 of different size
On Tue, 26 Aug 2003, Victoria Reznichenko wrote: Asif Iqbal [EMAIL PROTECTED] wrote: I already have mysql 4.0.13 running with all InnoDB tables. I am trying to use my-huge.cnf since I have 4 gig RAM with 4 x 450 Mhz processes In my MySQL data directory I have two ib_logfile files -rw-rw 1 mysqlmysql5242880 Aug 26 01:55 ib_logfile0 -rw-rw 1 mysqlmysql5242880 Aug 25 19:03 ib_logfile1 Now if I add this line in my cnf file (as recommended by my-huge.cnf) innodb_log_file_size = 100M I get the following error InnoDB: Error: log file /usr/local/mysql/data/ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 104857600 bytes! 030826 1:42:15 Can't init databases 030826 1:42:15 Aborting So as a workaround I commented the innodb_log_file_size. But I really don't like this solution. Is there a better solution ? Move old log files to the safe place. Edit my.cnf and then start MySQL server. If I move the old log in a safe place and use innodb_log_file_size = 100M, this is what I get 030826 01:40:38 mysqld started 030826 1:40:39 InnoDB: Log file /usr/local/mysql/data/ib_logfile0 did not exist: new to be created InnoDB: Setting log file /usr/local/mysql/data/ib_logfile0 size to 100 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 030826 1:40:47 InnoDB: Log file /usr/local/mysql/data/ib_logfile1 did not exist: new to be created InnoDB: Setting log file /usr/local/mysql/data/ib_logfile1 size to 100 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 InnoDB: Cannot initialize created log files because InnoDB: data files were not in sync with each other InnoDB: or the data files are corrupt. 030826 1:40:54 Can't init databases 030826 1:40:54 Aborting -- Asif Iqbal http://pgpkeys.mit.edu:11371/pks/lookup?op=getsearch=0x8B686E08 There's no place like 127.0.0.1 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB Error ib_logfile0 of different size
Asif, now take the old log files from the safe place and put them back! That will save your data. The instructions about changing the size of the log files are the following: http://www.innodb.com/ibman.html#Adding_and_removing If you want to change the number or the size of your InnoDB log files, you have to shut down MySQL and make sure that it shuts down without errors. Then copy the old log files into a safe place just in case something went wrong in the shutdown and you will need them to recover the database. Delete then the old log files from the log file directory, edit my.cnf, and start MySQL again. InnoDB will tell you at the startup that it is creating new log files. Note above that you must make sure mysqld shuts down without errors. Only then you can change the size of the log files. Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for MySQL Order MySQL technical support from https://order.mysql.com/ - Original Message - From: Asif Iqbal [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Tuesday, August 26, 2003 9:03 PM Subject: Re: InnoDB Error ib_logfile0 of different size On Tue, 26 Aug 2003, Victoria Reznichenko wrote: Asif Iqbal [EMAIL PROTECTED] wrote: I already have mysql 4.0.13 running with all InnoDB tables. I am trying to use my-huge.cnf since I have 4 gig RAM with 4 x 450 Mhz processes In my MySQL data directory I have two ib_logfile files -rw-rw 1 mysqlmysql5242880 Aug 26 01:55 ib_logfile0 -rw-rw 1 mysqlmysql5242880 Aug 25 19:03 ib_logfile1 Now if I add this line in my cnf file (as recommended by my-huge.cnf) innodb_log_file_size = 100M I get the following error InnoDB: Error: log file /usr/local/mysql/data/ib_logfile0 is of different size 0 5242880 bytes InnoDB: than specified in the .cnf file 0 104857600 bytes! 030826 1:42:15 Can't init databases 030826 1:42:15 Aborting So as a workaround I commented the innodb_log_file_size. But I really don't like this solution. Is there a better solution ? Move old log files to the safe place. Edit my.cnf and then start MySQL server. If I move the old log in a safe place and use innodb_log_file_size = 100M, this is what I get 030826 01:40:38 mysqld started 030826 1:40:39 InnoDB: Log file /usr/local/mysql/data/ib_logfile0 did not exist: new to be created InnoDB: Setting log file /usr/local/mysql/data/ib_logfile0 size to 100 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 030826 1:40:47 InnoDB: Log file /usr/local/mysql/data/ib_logfile1 did not exist: new to be created InnoDB: Setting log file /usr/local/mysql/data/ib_logfile1 size to 100 MB InnoDB: Database physically writes the file full: wait... InnoDB: Progress in MB: 100 InnoDB: Cannot initialize created log files because InnoDB: data files were not in sync with each other InnoDB: or the data files are corrupt. 030826 1:40:54 Can't init databases 030826 1:40:54 Aborting -- Asif Iqbal http://pgpkeys.mit.edu:11371/pks/lookup?op=getsearch=0x8B686E08 There's no place like 127.0.0.1 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Innodb error
I'm getting this error in my log: -- 030618 15:08:24 mysqld started 030618 15:08:24 InnoDB: Started 030618 15:08:24 /usr/sbin/mysqld: Can't create/write to file '/var/run/mysqld/mysqld.pid' (Errcode: 2) /usr/sbin/mysqld: ready for connections. Version: '4.0.12' socket: '/var/lib/mysql/mysql.sock' port: 3306 030618 15:08:26 InnoDB: Assertion failure in thread 28680 in file page0page.c line 450 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=67108864 read_buffer_size=1044480 030618 15:08:26 mysqld ended -- Prior to this, I was doing 'mysqldump -A ...' and mysql crashed. After rebooting the server I can get mysql running again, but most queries show 'connection lost', 'mysql gone away', etc. errors - but usually the queries work after the client automatically reconnects. 'mysqlcheck [-r] ...' dies with 'connection lost'. Please help! TIA, John __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Innodb error
John,
what Linux kernel version you are running? Did the first crash occur because
of the same assertion failure?
The InnoDB tablespace is probably corrupt and it asserts in purge or insert
buffer merge.
You can try starting with
innodb_force_recovery=4
in the [mysqld] section of your my.cnf. You can try to determine how
widespread the corruption is by running CHECK TABLE ... on your tables.
Then dump your tables and recreate the whole tablespace.
MySQL-4.0.14 will have the page checksum fixed. Then we will get more
information whether this kind of corruption originates in the file system.
It might also be an ordinary bug in InnoDB. It asserts in copying of records
to another page because a record does not fit though we have calculated it
should fit.
I have now added diagnostic code to 4.0.14 which will print hex dumps of the
pages if the assertion fails again.
Best regards,
Heikki Tuuri
Innobase Oy
http://www.innodb.com
Transactions, foreign keys, and a hot backup tool for MySQL
Order MySQL technical support from https://order.mysql.com/
...
/* Copy records from the original page to the new page */
sup = page_get_supremum_rec(page);
while (sup != page_cur_get_rec(cur1)) {
ut_a(
page_cur_rec_insert(cur2, page_cur_get_rec(cur1), mtr));
page_cur_move_to_next(cur1);
page_cur_move_to_next(cur2);
}
...
- Original Message -
From: John Smith [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Thursday, June 19, 2003 12:21 AM
Subject: Innodb error
I'm getting this error in my log:
--
030618 15:08:24 mysqld started
030618 15:08:24 InnoDB: Started
030618 15:08:24 /usr/sbin/mysqld: Can't create/write
to file '/var/run/mysqld/mysqld.pid' (Errcode: 2)
/usr/sbin/mysqld: ready for connections.
Version: '4.0.12' socket: '/var/lib/mysql/mysql.sock'
port: 3306
030618 15:08:26 InnoDB: Assertion failure in thread
28680 in file page0page.c line 450
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to
[EMAIL PROTECTED]
mysqld got signal 11;
This could be because you hit a bug. It is also
possible that this binary
or one of the libraries it was linked against is
corrupt, improperly built,
or misconfigured. This error can also be caused by
malfunctioning hardware.
We will try our best to scrape up some info that will
hopefully help diagnose
the problem, but since we have already crashed,
something is definitely wrong
and this may fail.
key_buffer_size=67108864
read_buffer_size=1044480
030618 15:08:26 mysqld ended
--
Prior to this, I was doing 'mysqldump -A ...' and
mysql crashed. After rebooting the server I can get
mysql running again, but most queries show 'connection
lost', 'mysql gone away', etc. errors - but usually
the queries work after the client automatically
reconnects. 'mysqlcheck [-r] ...' dies with
'connection lost'.
Please help!
TIA,
John
__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Innodb error
John,
actually, you should first try
innodb_force_recovery=2
and run CHECK TABLEs.
Regards,
Heikki
- Original Message -
From: Heikki Tuuri [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, June 19, 2003 1:25 AM
Subject: Re: Innodb error
John,
what Linux kernel version you are running? Did the first crash occur
because
of the same assertion failure?
The InnoDB tablespace is probably corrupt and it asserts in purge or
insert
buffer merge.
You can try starting with
innodb_force_recovery=4
in the [mysqld] section of your my.cnf. You can try to determine how
widespread the corruption is by running CHECK TABLE ... on your tables.
Then dump your tables and recreate the whole tablespace.
MySQL-4.0.14 will have the page checksum fixed. Then we will get more
information whether this kind of corruption originates in the file system.
It might also be an ordinary bug in InnoDB. It asserts in copying of
records
to another page because a record does not fit though we have calculated it
should fit.
I have now added diagnostic code to 4.0.14 which will print hex dumps of
the
pages if the assertion fails again.
Best regards,
Heikki Tuuri
Innobase Oy
http://www.innodb.com
Transactions, foreign keys, and a hot backup tool for MySQL
Order MySQL technical support from https://order.mysql.com/
...
/* Copy records from the original page to the new page */
sup = page_get_supremum_rec(page);
while (sup != page_cur_get_rec(cur1)) {
ut_a(
page_cur_rec_insert(cur2, page_cur_get_rec(cur1), mtr));
page_cur_move_to_next(cur1);
page_cur_move_to_next(cur2);
}
...
- Original Message -
From: John Smith [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Thursday, June 19, 2003 12:21 AM
Subject: Innodb error
I'm getting this error in my log:
--
030618 15:08:24 mysqld started
030618 15:08:24 InnoDB: Started
030618 15:08:24 /usr/sbin/mysqld: Can't create/write
to file '/var/run/mysqld/mysqld.pid' (Errcode: 2)
/usr/sbin/mysqld: ready for connections.
Version: '4.0.12' socket: '/var/lib/mysql/mysql.sock'
port: 3306
030618 15:08:26 InnoDB: Assertion failure in thread
28680 in file page0page.c line 450
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to
[EMAIL PROTECTED]
mysqld got signal 11;
This could be because you hit a bug. It is also
possible that this binary
or one of the libraries it was linked against is
corrupt, improperly built,
or misconfigured. This error can also be caused by
malfunctioning hardware.
We will try our best to scrape up some info that will
hopefully help diagnose
the problem, but since we have already crashed,
something is definitely wrong
and this may fail.
key_buffer_size=67108864
read_buffer_size=1044480
030618 15:08:26 mysqld ended
--
Prior to this, I was doing 'mysqldump -A ...' and
mysql crashed. After rebooting the server I can get
mysql running again, but most queries show 'connection
lost', 'mysql gone away', etc. errors - but usually
the queries work after the client automatically
reconnects. 'mysqlcheck [-r] ...' dies with
'connection lost'.
Please help!
TIA,
John
__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
InnoDB: Error: tablespace size stored in header
Hi, we're using Innodb here and I just upped the number of datafiles that innodb was using. When I did a show table status I noticed that I didn't get all the space that I had added. When I looked at the error log, I got recieved the following error. InnoDB: Error: tablespace size stored in header is 96 pages, but InnoDB: the sum of data file sizes is 1152000 pages Can anyone help me out here? BTW, we recompiled innodb to use 64kb pages rather then the default of 16kb. Here is the my.cnf we are using... Thanks! --shak innodb_data_file_path = ibdata1:4000M;ibdata2:4000M;ibdata3:4000M;ibdata4:4000M;ibdata5:4000M;ibdata6:4000M;ibdata7:4000M;ibdata8:4000M;ibdata9:4000M;ibdata10:4000M;ibdata11:4000M;ibdata12:4000M;ibdata13:4000M;ibdata14:4000M;ibdata15:4000M;ibdata16:4000M;ibdata17:4000M;ibdata18:4000M innodb_flush_log_at_trx_commit=0 set-variable = innodb_buffer_pool_size=2048M innodb_data_home_dir = /opt/mysql/data/ innodb_log_group_home_dir = /opt/mysql/data/ innodb_log_arch_dir = /opt/mysql/data/ set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=128M set-variable = innodb_log_buffer_size=192M innodb_log_archive=0 innodb_fast_shutdown=1 innodb_flush_method=nosync set-variable = innodb_additional_mem_pool_size=128M set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=50 set-variable = innodb_thread_concurrency=12 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: InnoDB: Error: tablespace size stored in header
Shakeel, - Original Message - From: Shakeel Sorathia [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Wednesday, November 13, 2002 9:39 PM Subject: InnoDB: Error: tablespace size stored in header Hi, we're using Innodb here and I just upped the number of datafiles that innodb was using. When I did a show table status I noticed that I didn't get all the space that I had added. When I looked at the error log, I got recieved the following error. InnoDB: Error: tablespace size stored in header is 96 pages, but InnoDB: the sum of data file sizes is 1152000 pages Can anyone help me out here? BTW, we recompiled innodb to use 64kb pages rather then the default of 16kb. Here is the my.cnf we are using... the support for 16 kB pages is not tested. Big pages were used in 2001 to let InnoDB store BLOBs of size up to 30 kB. But when big BLOBs up to 4 GB were implemented, that was no longer needed. I recommend keeping the page size at the default 16 kB. The error message above can occur if mysqld crashes or fails when you add a new data file. Then it may be that the new data file already got created, but the tablespace size in the tablespace header in the first data file was not yet updated. In that case you normally can remove the extra data file and create a new. But in your case this might also be some bug which surfaces because of the 64 kB page size. 96 pages = 60 000 MB 1152000 pages = 72 000 MB Did you add the last 3 data files manually, and did not let InnoDB to create them and write them full? If yes, that explains why the tablespace size in the tablespace header was not updated. Thanks! --shak Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ See http://www.innodb.com for the online manual and latest news on InnoDB sql query innodb_data_file_path = ibdata1:4000M;ibdata2:4000M;ibdata3:4000M;ibdata4:4000M;ibdata5:4000M;ibdata 6:4000M;ibdata7:4000M;ibdata8:4000M;ibdata9:4000M;ibdata10:4000M;ibdata11:40 00M;ibdata12:4000M;ibdata13:4000M;ibdata14:4000M;ibdata15:4000M;ibdata16:400 0M;ibdata17:4000M;ibdata18:4000M innodb_flush_log_at_trx_commit=0 set-variable = innodb_buffer_pool_size=2048M innodb_data_home_dir = /opt/mysql/data/ innodb_log_group_home_dir = /opt/mysql/data/ innodb_log_arch_dir = /opt/mysql/data/ set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=128M set-variable = innodb_log_buffer_size=192M innodb_log_archive=0 innodb_fast_shutdown=1 innodb_flush_method=nosync set-variable = innodb_additional_mem_pool_size=128M set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=50 set-variable = innodb_thread_concurrency=12 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Innodb error on windows ME platform
My guess on your problem is that you're running a database in WinME. It is
the worst, buggiest product out from a company that is famous for their
buggy OSs. Microsoft doesn't even support it worth a damn anymore, I'd
suggest going and getting a real OS. Nothing against you, many people don't
actually know what a steaming pile of crap WinME is.
Matt
- Original Message -
From: Heikki Tuuri [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, September 07, 2002 2:03 PM
Subject: Re: Innodb error on windows ME platform
Neil,
- Original Message -
From: Neil Malkani [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Saturday, September 07, 2002 7:46 PM
Subject: Innodb error on windows ME platform
Hi,
I have just installed and setup MySQL unfortunately I do not seem to be
able
to resolve this issue concerning the Innodb functionality in MySQL. Any
help
would be much appreciated.
the assertion means that InnoDB cannot create an event semaphore. I have
not
seen this assertion fail before. Maybe Windows has run out of some
resources?
Is there a Task Manager in Windows ME with which you could look how much
resources (handles, memory, etc.) are currently used? Do you have free
disk
space?
I will add better diagnostics to 3.23.53.
Below is the source code. CreateEvent returns a NULL value, and the
assertion ut_a(event) fails.
/*
Creates an event semaphore, i.e., a semaphore which may
just have two states: signaled and nonsignaled.
The created event is manual reset: it must be reset
explicitly by calling sync_os_reset_event. */
os_event_t
os_event_create(
/**/
/* out: the event handle */
char* name) /* in: the name of the event, if NULL
the event is created without a name */
{
#ifdef __WIN__
HANDLE event;
event = CreateEvent(NULL, /* No security attributes */
TRUE, /* Manual reset */
FALSE, /* Initial state nonsignaled */
name);
ut_a(event);
return(event);
Thanks,
Neil Malkani
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, row level locking, and foreign key support for
MySQL
See http://www.innodb.com, download MySQL-Max from http://www.mysql.com
020907 17:24:29 InnoDB: Assertion failure in thread 4294335835 in file
E:\build-3.23.52\innobase\os\os0sync.c line 52
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to [EMAIL PROTECTED]
020907 17:24:29 C:\MYSQL\BIN\MYSQLD~2.EXE: Got signal 11. Aborting!
020907 17:24:29 Aborting
020907 17:24:29 InnoDB: Warning: shutting down a not properly started
InnoDB: or created database!
020907 17:24:29 C:\MYSQL\BIN\MYSQLD~2.EXE: Shutdown Complete
_
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail
[EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail
[EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Innodb error on windows ME platform
Neil,
- Original Message -
From: Neil Malkani [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Saturday, September 07, 2002 7:46 PM
Subject: Innodb error on windows ME platform
Hi,
I have just installed and setup MySQL unfortunately I do not seem to be
able
to resolve this issue concerning the Innodb functionality in MySQL. Any
help
would be much appreciated.
the assertion means that InnoDB cannot create an event semaphore. I have not
seen this assertion fail before. Maybe Windows has run out of some
resources?
Is there a Task Manager in Windows ME with which you could look how much
resources (handles, memory, etc.) are currently used? Do you have free disk
space?
I will add better diagnostics to 3.23.53.
Below is the source code. CreateEvent returns a NULL value, and the
assertion ut_a(event) fails.
/*
Creates an event semaphore, i.e., a semaphore which may
just have two states: signaled and nonsignaled.
The created event is manual reset: it must be reset
explicitly by calling sync_os_reset_event. */
os_event_t
os_event_create(
/**/
/* out: the event handle */
char* name) /* in: the name of the event, if NULL
the event is created without a name */
{
#ifdef __WIN__
HANDLE event;
event = CreateEvent(NULL, /* No security attributes */
TRUE, /* Manual reset */
FALSE, /* Initial state nonsignaled */
name);
ut_a(event);
return(event);
Thanks,
Neil Malkani
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, row level locking, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-Max from http://www.mysql.com
020907 17:24:29 InnoDB: Assertion failure in thread 4294335835 in file
E:\build-3.23.52\innobase\os\os0sync.c line 52
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to [EMAIL PROTECTED]
020907 17:24:29 C:\MYSQL\BIN\MYSQLD~2.EXE: Got signal 11. Aborting!
020907 17:24:29 Aborting
020907 17:24:29 InnoDB: Warning: shutting down a not properly started
InnoDB: or created database!
020907 17:24:29 C:\MYSQL\BIN\MYSQLD~2.EXE: Shutdown Complete
_
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail
[EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Innodb error on windows ME platform
Hi, I have just installed and setup MySQL unfortunately I do not seem to be able to resolve this issue concerning the Innodb functionality in MySQL. Any help would be much appreciated. Thanks, Neil Malkani 020907 17:24:29 InnoDB: Assertion failure in thread 4294335835 in file E:\build-3.23.52\innobase\os\os0sync.c line 52 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] 020907 17:24:29 C:\MYSQL\BIN\MYSQLD~2.EXE: Got signal 11. Aborting! 020907 17:24:29 Aborting 020907 17:24:29 InnoDB: Warning: shutting down a not properly started InnoDB: or created database! 020907 17:24:29 C:\MYSQL\BIN\MYSQLD~2.EXE: Shutdown Complete _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Innodb Error
Hi, I was converting my table from MyISAM to Innodb, but i had a trouble. I had to kill an alter table command (It was an ADD INDEX in a DATETIME field) but it didn't stop. So i restarted the mysql but the mysql starts only if i disable innodb. Did i lost all my innodb tables? Is there anyway to save the data or should i recreate the innodb space? Thank u very much, Edilson. Edilson Vasconcelos de Melo Junior [EMAIL PROTECTED] (19) 3256-3577 ICQ 136192234 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
InnoDB Error 150, MySQL 4.0.1 alpha 3.23.49
Hello,
When attempting to create some tables using the MySQL 4.0.1 alpha and
3.23.49, I'm getting a generic error message, General error: Can't
create table './industria/ORDEREDITEMS.frm' (errno: 150). The other 6
tables, all using similar features, are created without a problem.
perror just says, Error code 150: Unknown error 150 which isn't
terribly helpful.
Some assistance with this would be appreciated. :-)
-rh
CREATE TABLE VENDORS ( V_VENDORID BIGINT NOT NULL, V_VENDORNAME
VARCHAR(20) NOT NULL, V_DESCRIPTION VARCHAR(80) NOT NULL, V_LOCKCNT
BIGINT NOT NULL DEFAULT '0', V_TIMESTAMP TIMESTAMP NOT NULL, PRIMARY KEY
(V_VENDORID), UNIQUE KEY VENDORS_VENDORNAME_IDX (V_VENDORNAME) )
TYPE=InnoDB;
CREATE TABLE ITEMS ( I_ITEMID BIGINT NOT NULL, I_V_VENDORID BIGINT NOT
NULL, I_ITEMNAME VARCHAR(20) NOT NULL, I_DESCRIPTION VARCHAR(80) NOT
NULL, I_ACTIVE ENUM('T','F') NOT NULL, I_PRICE DECIMAL(10, 2) NOT NULL,
I_LOCKCNT BIGINT NOT NULL DEFAULT '0', I_TIMESTAMP TIMESTAMP NOT NULL,
PRIMARY KEY (I_ITEMID), UNIQUE KEY ITEMS_VENDORITEM_IDX (I_V_VENDORID,
I_ITEMNAME), FOREIGN KEY (I_V_VENDORID) REFERENCES VENDORS(V_VENDORID)
ON DELETE CASCADE ) TYPE=InnoDB;
CREATE TABLE CATALOGS ( C_CATALOGID BIGINT NOT NULL, C_CATALOGNAME
VARCHAR(20) NOT NULL, C_DESCRIPTION VARCHAR(80) NOT NULL, C_LOCKCNT
BIGINT NOT NULL DEFAULT '0', C_TIMESTAMP TIMESTAMP NOT NULL, PRIMARY KEY
(C_CATALOGID), UNIQUE KEY CATALOGS_CATALOGNAME_IDX (C_CATALOGNAME) )
TYPE=InnoDB;
CREATE TABLE CATEGORIES ( CG_CATEGORYID BIGINT NOT NULL, CG_C_CATALOGID
BIGINT NOT NULL, CG_CATEGORYNAME VARCHAR(20) NOT NULL, CG_CG_CATEGORYID
BIGINT NOT NULL, CG_DESCRIPTION VARCHAR(80) NOT NULL, CG_LOCKCNT BIGINT
NOT NULL DEFAULT '0', CG_TIMESTAMP TIMESTAMP NOT NULL, PRIMARY KEY
(CG_CATEGORYID), UNIQUE KEY CATEGORIES_CATALOGCATEGORY_IDX
(CG_C_CATALOGID, CG_CATEGORYNAME), KEY CATEGORIES_CATALOGID_IDX
(CG_C_CATALOGID), KEY CATEGORIES_PARENTCATEGORYID_IDX
(CG_CG_CATEGORYID), FOREIGN KEY (CG_C_CATALOGID) REFERENCES
CATALOGS(C_CATALOGID) ON DELETE CASCADE, FOREIGN KEY (CG_CG_CATEGORYID)
REFERENCES CATEGORIES(CG_CATEGORYID) ON DELETE CASCADE ) TYPE=InnoDB;
CREATE TABLE CATAGORYITEMS ( CI_CG_CATEGORYID BIGINT NOT NULL,
CI_I_ITEMID BIGINT NOT NULL, CI_LOCKCNT BIGINT NOT NULL DEFAULT '0',
CI_TIMESTAMP TIMESTAMP NOT NULL, PRIMARY KEY (CI_CG_CATEGORYID,
CI_I_ITEMID), KEY CATAGORYITEMS_ITEMID_IDX (CI_I_ITEMID), FOREIGN KEY
(CI_CG_CATEGORYID) REFERENCES CATEGORIES(CG_CATEGORYID) ON DELETE
CASCADE, FOREIGN KEY (CI_I_ITEMID) REFERENCES ITEMS(I_ITEMID) ON DELETE
CASCADE ) TYPE=InnoDB;
CREATE TABLE ORDERS ( O_ORDERID BIGINT NOT NULL, O_ORDEREDITEMSEQUENCE
INT NOT NULL, O_LOCKCNT BIGINT NOT NULL DEFAULT '0', O_TIMESTAMP
TIMESTAMP NOT NULL, PRIMARY KEY (O_ORDERID) ) TYPE=InnoDB;
CREATE TABLE ORDEREDITEMS ( OI_O_ORDERID BIGINT NOT NULL,
OI_ORDEREDITEMSEQUENCE INT NOT NULL, OI_I_ITEMID BIGINT NOT NULL,
OI_QUANTITY INT(4) NOT NULL, OI_LOCKCNT BIGINT NOT NULL DEFAULT '0',
OI_TIMESTAMP TIMESTAMP NOT NULL, PRIMARY KEY (OI_O_ORDERID,
OI_ORDEREDITEMSEQUENCE), FOREIGN KEY (OI_O_ORDERID) REFERENCES
ORDERS(O_ORDERID) ON DELETE CASCADE, FOREIGN KEY (OI_I_ITEMID)
REFERENCES ITEMS(I_ITEMID) ON DELETE CASCADE ) TYPE=InnoDB;
java.sql.SQLException: General error: Can't create table
'./industria/ORDEREDITEMS.frm' (errno: 150)
at org.gjt.mm.mysql.MysqlIO.sendCommand(Unknown Source)
at org.gjt.mm.mysql.MysqlIO.sqlQueryDirect(Unknown Source)
at org.gjt.mm.mysql.MysqlIO.sqlQuery(Unknown Source)
at org.gjt.mm.mysql.Connection.execSQL(Unknown Source)
at org.gjt.mm.mysql.Connection.execSQL(Unknown Source)
at org.gjt.mm.mysql.Statement.executeQuery(Unknown Source)
at org.gjt.mm.mysql.jdbc2.Statement.executeQuery(Unknown Source)
at
com.darkrealms.entities.DatabaseUtilities.createMissingTable(DatabaseUti
lities.java:432)
at
com.darkrealms.entities.DatabaseUtilities.checkTables(DatabaseUtilities.
java:464)
at
com.darkrealms.entities.DatabaseUtilities.openDatabaseConnection(Databas
eUtilities.java:38)
at
com.darkrealms.entities.DatabaseUtilitiesForMySQL.init(DatabaseUtiliti
esForMySQL.java:19)
at
com.darkrealms.entities.DatabaseFromXML.main(DatabaseFromXML.java:17)
Exception in thread main
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: InnoDB Error 150, MySQL 4.0.1 alpha 3.23.49
Richard,
- Original Message -
From: Richard Harms [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Monday, April 22, 2002 2:32 AM
Subject: InnoDB Error 150, MySQL 4.0.1 alpha 3.23.49
Hello,
When attempting to create some tables using the MySQL 4.0.1 alpha and
3.23.49, I'm getting a generic error message, General error: Can't
create table './industria/ORDEREDITEMS.frm' (errno: 150). The other 6
tables, all using similar features, are created without a problem.
perror just says, Error code 150: Unknown error 150 which isn't
terribly helpful.
Some assistance with this would be appreciated. :-)
-rh
CREATE TABLE VENDORS ( V_VENDORID BIGINT NOT NULL, V_VENDORNAME
VARCHAR(20) NOT NULL, V_DESCRIPTION VARCHAR(80) NOT NULL, V_LOCKCNT
BIGINT NOT NULL DEFAULT '0', V_TIMESTAMP TIMESTAMP NOT NULL, PRIMARY KEY
(V_VENDORID), UNIQUE KEY VENDORS_VENDORNAME_IDX (V_VENDORNAME) )
TYPE=InnoDB;
CREATE TABLE ITEMS ( I_ITEMID BIGINT NOT NULL, I_V_VENDORID BIGINT NOT
NULL, I_ITEMNAME VARCHAR(20) NOT NULL, I_DESCRIPTION VARCHAR(80) NOT
NULL, I_ACTIVE ENUM('T','F') NOT NULL, I_PRICE DECIMAL(10, 2) NOT NULL,
I_LOCKCNT BIGINT NOT NULL DEFAULT '0', I_TIMESTAMP TIMESTAMP NOT NULL,
PRIMARY KEY (I_ITEMID), UNIQUE KEY ITEMS_VENDORITEM_IDX (I_V_VENDORID,
I_ITEMNAME), FOREIGN KEY (I_V_VENDORID) REFERENCES VENDORS(V_VENDORID)
ON DELETE CASCADE ) TYPE=InnoDB;
CREATE TABLE CATALOGS ( C_CATALOGID BIGINT NOT NULL, C_CATALOGNAME
VARCHAR(20) NOT NULL, C_DESCRIPTION VARCHAR(80) NOT NULL, C_LOCKCNT
BIGINT NOT NULL DEFAULT '0', C_TIMESTAMP TIMESTAMP NOT NULL, PRIMARY KEY
(C_CATALOGID), UNIQUE KEY CATALOGS_CATALOGNAME_IDX (C_CATALOGNAME) )
TYPE=InnoDB;
CREATE TABLE CATEGORIES ( CG_CATEGORYID BIGINT NOT NULL, CG_C_CATALOGID
BIGINT NOT NULL, CG_CATEGORYNAME VARCHAR(20) NOT NULL, CG_CG_CATEGORYID
BIGINT NOT NULL, CG_DESCRIPTION VARCHAR(80) NOT NULL, CG_LOCKCNT BIGINT
NOT NULL DEFAULT '0', CG_TIMESTAMP TIMESTAMP NOT NULL, PRIMARY KEY
(CG_CATEGORYID), UNIQUE KEY CATEGORIES_CATALOGCATEGORY_IDX
(CG_C_CATALOGID, CG_CATEGORYNAME), KEY CATEGORIES_CATALOGID_IDX
(CG_C_CATALOGID), KEY CATEGORIES_PARENTCATEGORYID_IDX
(CG_CG_CATEGORYID), FOREIGN KEY (CG_C_CATALOGID) REFERENCES
CATALOGS(C_CATALOGID) ON DELETE CASCADE, FOREIGN KEY (CG_CG_CATEGORYID)
REFERENCES CATEGORIES(CG_CATEGORYID) ON DELETE CASCADE ) TYPE=InnoDB;
CREATE TABLE CATAGORYITEMS ( CI_CG_CATEGORYID BIGINT NOT NULL,
CI_I_ITEMID BIGINT NOT NULL, CI_LOCKCNT BIGINT NOT NULL DEFAULT '0',
CI_TIMESTAMP TIMESTAMP NOT NULL, PRIMARY KEY (CI_CG_CATEGORYID,
CI_I_ITEMID), KEY CATAGORYITEMS_ITEMID_IDX (CI_I_ITEMID), FOREIGN KEY
(CI_CG_CATEGORYID) REFERENCES CATEGORIES(CG_CATEGORYID) ON DELETE
CASCADE, FOREIGN KEY (CI_I_ITEMID) REFERENCES ITEMS(I_ITEMID) ON DELETE
CASCADE ) TYPE=InnoDB;
CREATE TABLE ORDERS ( O_ORDERID BIGINT NOT NULL, O_ORDEREDITEMSEQUENCE
INT NOT NULL, O_LOCKCNT BIGINT NOT NULL DEFAULT '0', O_TIMESTAMP
TIMESTAMP NOT NULL, PRIMARY KEY (O_ORDERID) ) TYPE=InnoDB;
CREATE TABLE ORDEREDITEMS ( OI_O_ORDERID BIGINT NOT NULL,
OI_ORDEREDITEMSEQUENCE INT NOT NULL, OI_I_ITEMID BIGINT NOT NULL,
OI_QUANTITY INT(4) NOT NULL, OI_LOCKCNT BIGINT NOT NULL DEFAULT '0',
OI_TIMESTAMP TIMESTAMP NOT NULL, PRIMARY KEY (OI_O_ORDERID,
OI_ORDEREDITEMSEQUENCE), FOREIGN KEY (OI_O_ORDERID) REFERENCES
ORDERS(O_ORDERID) ON DELETE CASCADE, FOREIGN KEY (OI_I_ITEMID)
REFERENCES ITEMS(I_ITEMID) ON DELETE CASCADE ) TYPE=InnoDB;
there is no index on OI_I_ITEMID. InnoDB requires that a suitable index is
explicitly defined for a foreign key. Also note that ON DELETE CASCADE only
works from 3.23.50 up. When you migrate to 3.23.50, you must recreate your
tables so that InnoDB is aware of ON DELETE CASCADE.
java.sql.SQLException: General error: Can't create table
'./industria/ORDEREDITEMS.frm' (errno: 150)
at org.gjt.mm.mysql.MysqlIO.sendCommand(Unknown Source)
at org.gjt.mm.mysql.MysqlIO.sqlQueryDirect(Unknown Source)
at org.gjt.mm.mysql.MysqlIO.sqlQuery(Unknown Source)
at org.gjt.mm.mysql.Connection.execSQL(Unknown Source)
at org.gjt.mm.mysql.Connection.execSQL(Unknown Source)
at org.gjt.mm.mysql.Statement.executeQuery(Unknown Source)
at org.gjt.mm.mysql.jdbc2.Statement.executeQuery(Unknown Source)
at
com.darkrealms.entities.DatabaseUtilities.createMissingTable(DatabaseUti
lities.java:432)
at
com.darkrealms.entities.DatabaseUtilities.checkTables(DatabaseUtilities.
java:464)
at
com.darkrealms.entities.DatabaseUtilities.openDatabaseConnection(Databas
eUtilities.java:38)
at
com.darkrealms.entities.DatabaseUtilitiesForMySQL.init(DatabaseUtiliti
esForMySQL.java:19)
at
com.darkrealms.entities.DatabaseFromXML.main(DatabaseFromXML.java:17)
Exception in thread main
Best regards,
Heikki Tuuri
Innobase Oy
---
InnoDB - transactions, row level locking, and foreign key support for MySQL
See http://www.innodb.com, download MySQL-Max from http
InnoDB: Error creating table
Encounter the following error in MyCC: [root@localhost:3306]ERROR 1005: Can't create table '.\abc\def.frm' (errno 121) I'm using MySQL 3.23.49 and Win98se. The statement I used work on the default MYISAM table and DBD table and I did changed the TYPE=InnoDB in the CREATE statement. The following is part of the my.ini settings: [mysqld] innodb_data_home_dir=c:\ibdata innodb_data_file_path=ibdata1:50M set-variable=innodb_buffer_pool_size=40M set-variable=innodb_additional_mem_pool_size=5M innodb_log_group_home_dir=c:\iblogs innodb_log_arch_dir=c:\iblogs innodb_log_archive=0 set-variable=innodb_log_files_in_group=3 set-variable=innodb_log_file_size=5M set-variable=innodb_log_buffer_size=4M innodb_flush_log_at_trx_commit=1 set-variable=innodb_file_io_threads=4 set-variable=innodb_lock_wait_timeout=50 Thank you __ Do You Yahoo!? Yahoo! Messenger - Instant Messaging, Instant Gratification. (Now with new emoticons!) http://messenger.yahoo.com.sg/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: mysql innodb error
Heikki Tuuri wrote: Kannan, please upgrade to 3.23.49a or 4.0.1. 101 used to mean lock wait timeout. It has been replaced by a clear-English error code. Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ See http://www.innodb.com for the online manual and latest news on InnoDB - Original Message - From: [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Monday, April 01, 2002 1:30 PM Subject: mysql innodb error Placed At : Hi ... I 'm getting this very odd error with my update query..I run mysql-4.0.0-alpha on a redhat linux machine.. My table type is innodb. the error is as follows.. ERROR 1030: Got error 101 from table handler I do not have a very complex table structure and this error comes up only for one record or so..I restart the mysql on the server then the update starts working for this record..I 'm not able to create another table selecting from this table also..I feel that there is somekind of lock that gets set..but i have fought for long with this problem .. Should i go for a higher version of mysql can anyone suggest please.. regards kannan ** Quality Policy To be the best-in-class service provider by practising international standards in providing world-class services and end-to-end network solutions. ** - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php Hi there im fairly new myself from a PostgreSql background anyway is there a location to view and make copy of the error messages new and old types for reference and obviously one can quickly rectify. Cheers Chuck Amadi Systems Programmer - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
mysql innodb error
Placed At : Hi ... I 'm getting this very odd error with my update query..I run mysql-4.0.0-alpha on a redhat linux machine.. My table type is innodb. the error is as follows.. ERROR 1030: Got error 101 from table handler I do not have a very complex table structure and this error comes up only for one record or so..I restart the mysql on the server then the update starts working for this record..I 'm not able to create another table selecting from this table also..I feel that there is somekind of lock that gets set..but i have fought for long with this problem .. Should i go for a higher version of mysql can anyone suggest please.. regards kannan ** Quality Policy To be the best-in-class service provider by practising international standards in providing world-class services and end-to-end network solutions. ** - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: mysql innodb error
Kannan, please upgrade to 3.23.49a or 4.0.1. 101 used to mean lock wait timeout. It has been replaced by a clear-English error code. Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ See http://www.innodb.com for the online manual and latest news on InnoDB - Original Message - From: [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Monday, April 01, 2002 1:30 PM Subject: mysql innodb error Placed At : Hi ... I 'm getting this very odd error with my update query..I run mysql-4.0.0-alpha on a redhat linux machine.. My table type is innodb. the error is as follows.. ERROR 1030: Got error 101 from table handler I do not have a very complex table structure and this error comes up only for one record or so..I restart the mysql on the server then the update starts working for this record..I 'm not able to create another table selecting from this table also..I feel that there is somekind of lock that gets set..but i have fought for long with this problem .. Should i go for a higher version of mysql can anyone suggest please.. regards kannan ** Quality Policy To be the best-in-class service provider by practising international standards in providing world-class services and end-to-end network solutions. ** - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: mysql innodb error
I thought the 4.0 series was still Beta? On Mon, 1 Apr 2002, Heikki Tuuri wrote: Date: Mon, 1 Apr 2002 18:09:53 +0300 From: Heikki Tuuri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: mysql innodb error Kannan, please upgrade to 3.23.49a or 4.0.1. 101 used to mean lock wait timeout. It has been replaced by a clear-English error code. Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ See http://www.innodb.com for the online manual and latest news on InnoDB - Original Message - From: [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Monday, April 01, 2002 1:30 PM Subject: mysql innodb error Placed At : Hi ... I 'm getting this very odd error with my update query..I run mysql-4.0.0-alpha on a redhat linux machine.. My table type is innodb. the error is as follows.. ERROR 1030: Got error 101 from table handler I do not have a very complex table structure and this error comes up only for one record or so..I restart the mysql on the server then the update starts working for this record..I 'm not able to create another table selecting from this table also..I feel that there is somekind of lock that gets set..but i have fought for long with this problem .. Should i go for a higher version of mysql can anyone suggest please.. regards kannan ** Quality Policy To be the best-in-class service provider by practising international standards in providing world-class services and end-to-end network solutions. ** - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php Sincerely, William Mussatto, Senior Systems Engineer CyberStrategies, Inc ph. 909-920-9154 ext. 27 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: mysql innodb error
William, - Original Message - From: William R. Mussatto [EMAIL PROTECTED] To: Heikki Tuuri [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, April 01, 2002 6:29 PM Subject: Re: mysql innodb error I thought the 4.0 series was still Beta? yes, 4.0.1 is beta or alpha, depending on terminology. 4.0.2 will contain a lot of new MySQL code. Thus we cannot yet say how stable 4.0.2 will be. InnoDB in 4.0 and 3.23 is the same. Thus the InnoDB part is stable also in 4.0.2. Regards, Heikki On Mon, 1 Apr 2002, Heikki Tuuri wrote: Date: Mon, 1 Apr 2002 18:09:53 +0300 From: Heikki Tuuri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: mysql innodb error Kannan, please upgrade to 3.23.49a or 4.0.1. 101 used to mean lock wait timeout. It has been replaced by a clear-English error code. Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ See http://www.innodb.com for the online manual and latest news on InnoDB - Original Message - From: [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Monday, April 01, 2002 1:30 PM Subject: mysql innodb error Placed At : Hi ... I 'm getting this very odd error with my update query..I run mysql-4.0.0-alpha on a redhat linux machine.. My table type is innodb. the error is as follows.. ERROR 1030: Got error 101 from table handler I do not have a very complex table structure and this error comes up only for one record or so..I restart the mysql on the server then the update starts working for this record..I 'm not able to create another table selecting from this table also..I feel that there is somekind of lock that gets set..but i have fought for long with this problem .. Should i go for a higher version of mysql can anyone suggest please.. regards kannan ** Quality Policy To be the best-in-class service provider by practising international standards in providing world-class services and end-to-end network solutions. ** - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php Sincerely, William Mussatto, Senior Systems Engineer CyberStrategies, Inc ph. 909-920-9154 ext. 27 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Trouble with InnoDB: Error message file errmsg.sys doesn't have enough messages?
Hi! On Dec 05, JW wrote: Using mysql-3.23.33-4 on SuSE Linux 7.1: root@fluorite:/usr/sbin uname -a Linux fluorite 2.4.0-64GB-SMP #1 SMP Wed Jan 24 15:52:30 GMT 2001 i686 unknown We've been using MySQL for a while and we're trying to test InnoDB. According the InnoDB page all we need to do is untar the package and overwrite /usr/sbin/mysqld. I also found I have to create to following directory/symlink: root@fluorite:/usr/bin ls -l /usr/local/mysql/share/ total 0 lrwxrwxrwx1 root root 17 Dec 5 16:05 mysql - /usr/share/mysql/ becauwe without that the new mysqld (mysqld-max) couldn't find /usr/local/mysql/share/mysql/english/errmsg.sys. Now that I have that all set up, I'm getting the following errors: root@fluorite:/usr/bin /usr/sbin/mysqld /usr/sbin/mysqld: Fatal error: Error message file '/usr/local/mysql/share/mysql/english/errmsg.sys' had only 203 error messages, but it should have at least 218 error messages. Check that the above file is the right version for this program! I don't think it's a version problem because the RPM was mysql-3.23.33-4 and the tarball is mysql-max-3.23.46-pc-linux-gnu-i686.tar.gz. It is version problem. Can anyone give me some tips on what's wrong? Is there's something wrong with the SuSE version of mysql-3.23.33-4 that's incompatible with mysql-max-3.23.46-pc-linux-gnu-i686.tar.gz ? Replace /usr/local/mysql/share/language/errmsg.sys files by those from new rpm. MySQL stores error messages in these files. between 3.23.33 and 3.23.46 some new error messages were added, so new mysqld won't work with old errmsg.sys Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ___/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: [SLE] Trouble with InnoDB: Error message file errmsg.sys doesn't have enough messages?
Well, I got around the problem by replacing the old mysql/english directory with a new one from the tarball. I hope that was an o.k. thing to do. At 04:35 PM 12/5/2001 -0600, you wrote: Using mysql-3.23.33-4 on SuSE Linux 7.1: root@fluorite:/usr/sbin uname -a Linux fluorite 2.4.0-64GB-SMP #1 SMP Wed Jan 24 15:52:30 GMT 2001 i686 unknown We've been using MySQL for a while and we're trying to test InnoDB. According the InnoDB page all we need to do is untar the package and overwrite /usr/sbin/mysqld. I also found I have to create to following directory/symlink: root@fluorite:/usr/bin ls -l /usr/local/mysql/share/ total 0 lrwxrwxrwx1 root root 17 Dec 5 16:05 mysql - /usr/share/mysql/ becauwe without that the new mysqld (mysqld-max) couldn't find /usr/local/mysql/share/mysql/english/errmsg.sys. Now that I have that all set up, I'm getting the following errors: root@fluorite:/usr/bin /usr/sbin/mysqld /usr/sbin/mysqld: Fatal error: Error message file '/usr/local/mysql/share/mysql/english/errmsg.sys' had only 203 error messages, but it should have at least 218 error messages. Check that the above file is the right version for this program! I don't think it's a version problem because the RPM was mysql-3.23.33-4 and the tarball is mysql-max-3.23.46-pc-linux-gnu-i686.tar.gz. Can anyone give me some tips on what's wrong? Is there's something wrong with the SuSE version of mysql-3.23.33-4 that's incompatible with mysql-max-3.23.46-pc-linux-gnu-i686.tar.gz ? TIA Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com -- To unsubscribe send e-mail to [EMAIL PROTECTED] For additional commands send e-mail to [EMAIL PROTECTED] Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Trouble with InnoDB: Error message file errmsg.sys doesn't have enough messages?
I don't think it's a version problem because the R PM was mysql-3.23.33-4 and the tarball is mysql-max -3.23.46-pc-linux-gnu-i686.tar.gz. 33 != 46 I'd be surprised if that's not the reason for the problems you're having, especially considering how much has changed since 3.22. //C - points to the section on line length in the netiquette FAQ. -- Carl Troein - Círdan / Istari-PixelMagic - UIN 16353280 [EMAIL PROTECTED] | http://pixelmagic.dyndns.org/~cirdan/ Amiga user since '89, and damned proud of it too. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
mysql win32 binary w/ innodb: error number 3
Hi folks, I need help to start my server with InnoDB. I have manually created innodb_data_home_dir, which is c:\mysql\ibdata. The mysql server is running on Windows ME platform. my.cnf is as follows: # Example mysql config file. # Copy this file to c:\my.cnf to set global options # # One can use all long options that the program supports. # Run the program with --help to get a list of available options # This will be passed to all mysql clients [client] #password=my_password port=3306 #socket=MySQL # Here is entries for some specific programs # The following values assume you have at least 32M ram # The MySQL server [mysqld] port=3306 #socket=MySQL skip-locking default-character-set=latin1 set-variable = key_buffer=16M set-variable = max_allowed_packet=1M set-variable = thread_stack=128K set-variable = flush_time=1800 # Uncomment the following rows if you move the MySQL distribution to another # location basedir = c:/mysql/ datadir = c:/mysql/data/ # Uncomment the following rows if you are using InnoDB tables # Create the directories ibdata and iblogs before to start the server. # If necessary, modify the size of the files innodb_data_file_path = ibdata1:200M innodb_data_home_dir = c:\mysql\ibdata set-variable = innodb_mirrored_log_groups=1 innodb_log_group_home_dir = c:\mysql\iblogs set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=30M set-variable = innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 #.._arch_dir must be the same as .._log_group_home_dir innodb_log_arch_dir = c:\mysql\iblogs innodb_log_archive=0 set-variable = innodb_buffer_pool_size=80M set-variable = lower_case_table_names =0 set-variable = innodb_additional_mem_pool_size=10M set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=50 # Uncomment the following row if you are using a Max server and you don't want the # InnoDb tables #skip-innobd [mysqldump] quick set-variable = max_allowed_packet=16M [mysql] no-auto-rehash [isamchk] set-variable= key=16M [client_fltk] help_file= c:\mysql\sql_client\MySQL.help client_file= c:\mysql\MySQL.options history_length=20 database = test queries_root= c:\mysql\queries last_database_file= c:\mysql\lastdb The error I am getting is as follows: C:\c:\mysql\bin\mysqld-max --standalone InnoDB: Warning: operating system error number 3 in a file operation. InnoDB: Cannot continue operation. I appreciate your great help. Thanks - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: mysql win32 binary w/ innodb: error number 3
At 20:45 25/11/01 -0800, Bryan Chong wrote: Hi, Hi folks, I need help to start my server with InnoDB. I have manually created innodb_data_home_dir, which is c:\mysql\ibdata. The mysql server is running on Windows ME platform. my.cnf is Notice that beside the c:\mysql\ibdata directory you need to create the c:\mysql\iblogs too. Before to try again the first start, delete the files created in c:\mysql\ibdata. Regards, Miguel as follows: # Example mysql config file. # Copy this file to c:\my.cnf to set global options # # One can use all long options that the program supports. # Run the program with --help to get a list of available options # This will be passed to all mysql clients [client] #password=my_password port=3306 #socket=MySQL # Here is entries for some specific programs # The following values assume you have at least 32M ram # The MySQL server [mysqld] port=3306 #socket=MySQL skip-locking default-character-set=latin1 set-variable = key_buffer=16M set-variable = max_allowed_packet=1M set-variable = thread_stack=128K set-variable = flush_time=1800 # Uncomment the following rows if you move the MySQL distribution to another # location basedir = c:/mysql/ datadir = c:/mysql/data/ # Uncomment the following rows if you are using InnoDB tables # Create the directories ibdata and iblogs before to start the server. # If necessary, modify the size of the files innodb_data_file_path = ibdata1:200M innodb_data_home_dir = c:\mysql\ibdata set-variable = innodb_mirrored_log_groups=1 innodb_log_group_home_dir = c:\mysql\iblogs set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=30M set-variable = innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 #.._arch_dir must be the same as .._log_group_home_dir innodb_log_arch_dir = c:\mysql\iblogs innodb_log_archive=0 set-variable = innodb_buffer_pool_size=80M set-variable = lower_case_table_names =0 set-variable = innodb_additional_mem_pool_size=10M set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=50 # Uncomment the following row if you are using a Max server and you don't want the # InnoDb tables #skip-innobd [mysqldump] quick set-variable = max_allowed_packet=16M [mysql] no-auto-rehash [isamchk] set-variable= key=16M [client_fltk] help_file= c:\mysql\sql_client\MySQL.help client_file= c:\mysql\MySQL.options history_length=20 database = test queries_root= c:\mysql\queries last_database_file= c:\mysql\lastdb The error I am getting is as follows: C:\c:\mysql\bin\mysqld-max --standalone InnoDB: Warning: operating system error number 3 in a file operation. InnoDB: Cannot continue operation. I appreciate your great help. Thanks - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php -- For technical support contracts, goto https://order.mysql.com/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Miguel A. Solórzano [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Mogi das Cruzes - São Paulo, Brazil ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
