Re: mysqld-nt error 23. Urgent pls
Thanks, We tried copying the file but with no success. Running Norton DD reported errors with file descriptors. regards --- Heikki Tuuri <[EMAIL PROTECTED]> wrote: > Hi! > > 4.0.14 on Windows prints a wrong (errno) > explanation. You should look at > http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html > > " > 23 (ERROR_CRC) > Data error (cyclic redundancy check). > " > > Your file (system) is corrupt, and Windows notices > it. It is a hardware > fault or a Windows bug. > > Try copy:ing ibdata1 to another file. Does it > succeed? > > 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: "A Z" <[EMAIL PROTECTED]> > Newsgroups: mailing.database.myodbc > Sent: Wednesday, November 17, 2004 1:48 AM > Subject: mysqld-nt error 23. Urgent pls > > > > > > > > MySQL 4.0.14 > > > > Need help please with the folowing: > > > > > > On starting mysqld-nt using > > mysqld-nt --console > > we the get the follwing output > > > > 041115 10:31:59 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 3 3136790960 > > InnoDB: Doing recovery: scanned up to log sequence > > number 3 3136791157 > > 041115 10:32:00 InnoDB: Starting an apply batch > of > > log records to the database > > .. > > InnoDB: Progress in percents: 32 33 34 35 36 37 38 > 39 > > 40 41 42 43 44 45 46 47 4 > > 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 > > 5 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 > 92 > > 93 94 95 96 97 98 99 > > InnoDB: Apply batch completed > > 041115 10:32:00 InnoDB: Flushing modified pages > from > > the buffer pool... > > 041115 10:32:02 InnoDB: Started > > 041115 10:32:09 InnoDB: Operating system error > number > > 23 in a file operation. > > InnoDB: See http://www.innodb.com/ibman.html for > > installation help. > > InnoDB: Error number 23 means 'Too many open files > in > > system'. > > InnoDB: See also section 13.2 at > > http://www.innodb.com/ibman.html > > InnoDB: about operating system error numbers. > > InnoDB: File name .\ibdata1 > > InnoDB: File operation call: 'Windows aio'. > > InnoDB: Cannot continue operation. > > > > > > regards > > > > > > > > > > > ___ > > Win a castle for NYE with your mates and Yahoo! > Messenger > > http://uk.messenger.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] > > ___ Win a castle for NYE with your mates and Yahoo! Messenger http://uk.messenger.yahoo.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqld-nt error 23. Urgent pls
Hi! 4.0.14 on Windows prints a wrong (errno) explanation. You should look at http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html " 23 (ERROR_CRC) Data error (cyclic redundancy check). " Your file (system) is corrupt, and Windows notices it. It is a hardware fault or a Windows bug. Try copy:ing ibdata1 to another file. Does it succeed? 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: "A Z" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Wednesday, November 17, 2004 1:48 AM Subject: mysqld-nt error 23. Urgent pls MySQL 4.0.14 Need help please with the folowing: On starting mysqld-nt using mysqld-nt --console we the get the follwing output 041115 10:31:59 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 3 3136790960 InnoDB: Doing recovery: scanned up to log sequence number 3 3136791157 041115 10:32:00 InnoDB: Starting an apply batch of log records to the database .. InnoDB: Progress in percents: 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 4 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 5 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 041115 10:32:00 InnoDB: Flushing modified pages from the buffer pool... 041115 10:32:02 InnoDB: Started 041115 10:32:09 InnoDB: Operating system error number 23 in a file operation. InnoDB: See http://www.innodb.com/ibman.html for installation help. InnoDB: Error number 23 means 'Too many open files in system'. InnoDB: See also section 13.2 at http://www.innodb.com/ibman.html InnoDB: about operating system error numbers. InnoDB: File name .\ibdata1 InnoDB: File operation call: 'Windows aio'. InnoDB: Cannot continue operation. regards ___ Win a castle for NYE with your mates and Yahoo! Messenger http://uk.messenger.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: mysqld-nt error 23. Urgent pls
Hello. I didn't found any bug in bug database, which was similar to your's. Also I haven't ever heard about that thing: count of open files exceeded OS limit in Windows. So for the beginning take a look at: http://dev.mysql.com/doc/mysql/en/Not_enough_file_handles.html And, if it won't be helpful, try to uprade your MySQL. May be you can wait, if somebody gives better advice. A Z <[EMAIL PROTECTED]> wrote: > > > MySQL 4.0.14 > > Need help please with the folowing: > > > On starting mysqld-nt using > mysqld-nt --console > we the get the follwing output > > 041115 10:31:59 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 3 3136790960 > InnoDB: Doing recovery: scanned up to log sequence > number 3 3136791157 > 041115 10:32:00 InnoDB: Starting an apply batch of > log records to the database > .. > InnoDB: Progress in percents: 32 33 34 35 36 37 38 39 > 40 41 42 43 44 45 46 47 4 > 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 > 5 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 > 93 94 95 96 97 98 99 > InnoDB: Apply batch completed > 041115 10:32:00 InnoDB: Flushing modified pages from > the buffer pool... > 041115 10:32:02 InnoDB: Started > 041115 10:32:09 InnoDB: Operating system error number > 23 in a file operation. > InnoDB: See http://www.innodb.com/ibman.html for > installation help. > InnoDB: Error number 23 means 'Too many open files in > system'. > InnoDB: See also section 13.2 at > http://www.innodb.com/ibman.html > InnoDB: about operating system error numbers. > InnoDB: File name .\ibdata1 > InnoDB: File operation call: 'Windows aio'. > InnoDB: Cannot continue operation. > > > regards > > > > > ___ > Win a castle for NYE with your mates and Yahoo! Messenger > http://uk.messenger.yahoo.com > -- 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]
mysqld-nt error 23. Urgent pls
MySQL 4.0.14 Need help please with the folowing: On starting mysqld-nt using mysqld-nt --console we the get the follwing output 041115 10:31:59 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 3 3136790960 InnoDB: Doing recovery: scanned up to log sequence number 3 3136791157 041115 10:32:00 InnoDB: Starting an apply batch of log records to the database .. InnoDB: Progress in percents: 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 4 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 5 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 041115 10:32:00 InnoDB: Flushing modified pages from the buffer pool... 041115 10:32:02 InnoDB: Started 041115 10:32:09 InnoDB: Operating system error number 23 in a file operation. InnoDB: See http://www.innodb.com/ibman.html for installation help. InnoDB: Error number 23 means 'Too many open files in system'. InnoDB: See also section 13.2 at http://www.innodb.com/ibman.html InnoDB: about operating system error numbers. InnoDB: File name .\ibdata1 InnoDB: File operation call: 'Windows aio'. InnoDB: Cannot continue operation. regards ___ Win a castle for NYE with your mates and Yahoo! Messenger http://uk.messenger.yahoo.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
