Re: Strange problem with mysqldump / automysqlbackup (ERROR 1300)
So, as a followup, I ran mysqldump on the actual server (with the output directed over AFP to another machine on the network) -- as opposed to running mysqldump on the destination server and connecting to the databases over TCP/IP (both are running 5.1.39 PPC 64-bit). *That* dump file imported OK. So... It appears there's a bug in mysqldump that occurs intermittently when using TCP/IP connections to the MySQL database server. I haven't seen this bug occur on smaller databases, but it was pretty consistent on my non-damaged database of 9GB+. Anyway, for now I'm going to run automysqlbackup on the actual machine and simply dump to an external drive or another server on the network. On 2009-11-20, at 12:58 PM, René Fournier wrote: > Yes, still exhibits this problem -- although at a different line in the file. > (Seems random.) I should also mention, the backup is running across a local > network. The machine the starts automysqlbackup (and internally, mysqldump) > connects over TCP/IP to the database server. I am going to try running > mysqldump on the database server itself, but it's not something I can do > during normal hours -- plus at 10GB, it's a time-consuming thing to test. > (Would it matter? I guess I need to find out.)
Re: Strange problem with mysqldump / automysqlbackup (ERROR 1300)
Except that, in my case, both machines are running 5.1.39. Mac "OS X" PPC 64-bit. I tried importing another, different dump file of the same database, and this time mysql returned a different error: Sat Nov 21 13:16:20 -- Minas-Tirith :: mysql -u root -p < dump_file.sql Enter password: ERROR 1136 (21S01) at line 6300: Column count doesn't match value count at row 6253 So, a different error. And it appears that each time mysqldump runs, the resulting file has different problem. On 2009-11-21, at 5:05 PM, Claudio Nanni wrote: > There is a bug in mysqldump that prevents mysql from version 5.0.80 from > importing dumps from a old version of mysqldump. > I had this verified by MySQL support. > You can have a look at this bug: http://bugs.mysql.com/bug.php?id=41486 > > Cheers > > Claudio > > > > 2009/11/21 René Fournier > >> It's just odd, because that error was on 5.0. I'm running 5.1.39 -- surely >> enough time for the MySQL devs to fix it right? >> >> Could it be with extended inserts that the max statement length is greater >> than the default 16MB max allowed packet? I'm increasing that value to 256 >> MB and going to try again. >> >> Thanks for the idea though. At least I'm not the only one to have >> encountered that error. >> >> ...Rene >> >> On 2009-11-21, at 5:44 AM, 王浩 wrote: >> >>> i googled the problem,it says that's a mysql bug.This is the source page >> :http://www.shinguz.ch/MySQL/mysql_trouble_shooting.html#backup_restore, >>> And i suggest you ignore the error when import or correct the dump to the >> source database and then import again. >>> >>> Best wishes! >> >> > > > -- > Claudio
Re: Strange problem with mysqldump / automysqlbackup (ERROR 1300)
There is a bug in mysqldump that prevents mysql from version 5.0.80 from importing dumps from a old version of mysqldump. I had this verified by MySQL support. You can have a look at this bug: http://bugs.mysql.com/bug.php?id=41486 Cheers Claudio 2009/11/21 René Fournier > It's just odd, because that error was on 5.0. I'm running 5.1.39 -- surely > enough time for the MySQL devs to fix it right? > > Could it be with extended inserts that the max statement length is greater > than the default 16MB max allowed packet? I'm increasing that value to 256 > MB and going to try again. > > Thanks for the idea though. At least I'm not the only one to have > encountered that error. > > ...Rene > > On 2009-11-21, at 5:44 AM, 王浩 wrote: > > > i googled the problem,it says that's a mysql bug.This is the source page > :http://www.shinguz.ch/MySQL/mysql_trouble_shooting.html#backup_restore, > > And i suggest you ignore the error when import or correct the dump to the > source database and then import again. > > > > Best wishes! > > -- Claudio
Re: Strange problem with mysqldump / automysqlbackup (ERROR 1300)
It's just odd, because that error was on 5.0. I'm running 5.1.39 -- surely enough time for the MySQL devs to fix it right? Could it be with extended inserts that the max statement length is greater than the default 16MB max allowed packet? I'm increasing that value to 256 MB and going to try again. Thanks for the idea though. At least I'm not the only one to have encountered that error. ...Rene On 2009-11-21, at 5:44 AM, 王浩 wrote: > i googled the problem,it says that's a mysql bug.This is the source page > :http://www.shinguz.ch/MySQL/mysql_trouble_shooting.html#backup_restore, > And i suggest you ignore the error when import or correct the dump to the > source database and then import again. > > Best wishes!
Re: Strange problem with mysqldump / automysqlbackup (ERROR 1300)
Yes, still exhibits this problem -- although at a different line in the file. (Seems random.) I should also mention, the backup is running across a local network. The machine the starts automysqlbackup (and internally, mysqldump) connects over TCP/IP to the database server. I am going to try running mysqldump on the database server itself, but it's not something I can do during normal hours -- plus at 10GB, it's a time-consuming thing to test. (Would it matter? I guess I need to find out.) In any case, it seems clear that during the dump, mysqldump is periodically adding a character to the dump file. On 2009-11-20, at 12:41 PM, Gavin Towey wrote: > Have you tried dumping that table manually using mysqldump on the command > line to confirm it's not an issue with automysqlbackup? > > Regards, > Gavin Towey > > -Original Message- > From: René Fournier [mailto:m...@renefournier.com] > Sent: Friday, November 20, 2009 8:31 AM > To: mysql > Subject: Strange problem with mysqldump / automysqlbackup (ERROR 1300) > > I've been using automysqlbackup 2.5 for years on a particular database, and > it's always performed great. Recently, however, I've become encountering > problems when trying to re-import one of its dumped sql files. (Not sure if > it matters, but the database file in question is large and growing -- about > 10GB. The other databases automysqlbackup backs up are fine.) > > Basically on the import, MySQL fails and returns an error indicating a > problem with the dump file: > > mysql -u root -p < dump_file.sql (~10GB) > Enter password: > ERROR 1300 (HY000) at line 426: Invalid utf8 character string: '?03422' > > Sure enough, I look at the line in dump_file.sql, which should contain two > unsigned ints, and two unsigned small ints: > >[...],(32562206,1228?03422,1641,135),[...] > > And yup, there's a question mark in the middle of the second unsigned int, > for some strange reason. Not in any of the other rows in that statement. When > I look at the existing database from which the dump file was made, that row > is fine: > > mysql> SELECT * FROM bandwidth WHERE id = 32562206; > +--++---+---+ > | id | time_sec | device_id | bytes | > +--++---+---+ > | 32562206 | 1228803422 | 1641 | 135 | > +--++---+---+ > 1 row in set (0.00 sec) > > > So... It appears either mysqldump and/or automysqlbackup is having a problem > dumping a true copy of the database. > > Anyone else run into this sort of thing? Any suggestions? Thanks. > > ...Rene > > The information contained in this transmission may contain privileged and > confidential information. It is intended only for the use of the person(s) > named above. If you are not the intended recipient, you are hereby notified > that any review, dissemination, distribution or duplication of this > communication is strictly prohibited. If you are not the intended recipient, > please contact the sender by reply email and destroy all copies of the > original message. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
RE: Strange problem with mysqldump / automysqlbackup (ERROR 1300)
Have you tried dumping that table manually using mysqldump on the command line to confirm it's not an issue with automysqlbackup? Regards, Gavin Towey -Original Message- From: René Fournier [mailto:m...@renefournier.com] Sent: Friday, November 20, 2009 8:31 AM To: mysql Subject: Strange problem with mysqldump / automysqlbackup (ERROR 1300) I've been using automysqlbackup 2.5 for years on a particular database, and it's always performed great. Recently, however, I've become encountering problems when trying to re-import one of its dumped sql files. (Not sure if it matters, but the database file in question is large and growing -- about 10GB. The other databases automysqlbackup backs up are fine.) Basically on the import, MySQL fails and returns an error indicating a problem with the dump file: mysql -u root -p < dump_file.sql (~10GB) Enter password: ERROR 1300 (HY000) at line 426: Invalid utf8 character string: '?03422' Sure enough, I look at the line in dump_file.sql, which should contain two unsigned ints, and two unsigned small ints: [...],(32562206,1228?03422,1641,135),[...] And yup, there's a question mark in the middle of the second unsigned int, for some strange reason. Not in any of the other rows in that statement. When I look at the existing database from which the dump file was made, that row is fine: mysql> SELECT * FROM bandwidth WHERE id = 32562206; +--++---+---+ | id | time_sec | device_id | bytes | +--++---+---+ | 32562206 | 1228803422 | 1641 | 135 | +--++---+---+ 1 row in set (0.00 sec) So... It appears either mysqldump and/or automysqlbackup is having a problem dumping a true copy of the database. Anyone else run into this sort of thing? Any suggestions? Thanks. ...Rene The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Strange problem with mysqldump / automysqlbackup (ERROR 1300)
I've been using automysqlbackup 2.5 for years on a particular database, and it's always performed great. Recently, however, I've become encountering problems when trying to re-import one of its dumped sql files. (Not sure if it matters, but the database file in question is large and growing -- about 10GB. The other databases automysqlbackup backs up are fine.) Basically on the import, MySQL fails and returns an error indicating a problem with the dump file: mysql -u root -p < dump_file.sql (~10GB) Enter password: ERROR 1300 (HY000) at line 426: Invalid utf8 character string: '?03422' Sure enough, I look at the line in dump_file.sql, which should contain two unsigned ints, and two unsigned small ints: [...],(32562206,1228?03422,1641,135),[...] And yup, there's a question mark in the middle of the second unsigned int, for some strange reason. Not in any of the other rows in that statement. When I look at the existing database from which the dump file was made, that row is fine: mysql> SELECT * FROM bandwidth WHERE id = 32562206; +--++---+---+ | id | time_sec | device_id | bytes | +--++---+---+ | 32562206 | 1228803422 | 1641 | 135 | +--++---+---+ 1 row in set (0.00 sec) So... It appears either mysqldump and/or automysqlbackup is having a problem dumping a true copy of the database. Anyone else run into this sort of thing? Any suggestions? Thanks. ...Rene
Re: Problem with mysqldump and local-infile
Mark van Herpen <[EMAIL PROTECTED]> writes: > Hi, > > I want to backup my databases with mysqldump, but mysqldump won't run > because I use the 'local-infile=1' option in the my.cnf file: > > [client] > port= 3306 > socket = /tmp/mysql.sock > local-infile= 1 > > This is because I want php and other clients to use local-infile. This > works, by when I start mysqldump I got this error: > > ~ # mysqldump > mysqldump: unknown variable 'local-infile=1' > > So, what is wrong? As far as I know local-infile is a valid option to > put in the my.cnf. > > Is there a way to unset the local-infile option and start then start > mysqldump or something? Or any other solution? If you use LOAD DATA LOCAL in Perl scripts or other programs that read the [client] group from option files, you can add the local-infile=1 option to that group. However, to keep this from causing problems for programs that do not understand local-infile, specify it using the loose- prefix: [client] loose-local-infile=1 http://dev.mysql.com/doc/refman/5.0/en/load-data-local.html > Grtz, > > Mark van Herpen -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Problem with mysqldump and local-infile
It looks to me that local-infile is a command-line parameter to mysql client mysql --local-infile -u user dbname I've not been able to find this option elsewhere. -- Later Mogens Melander +45 40 85 71 38 +66 870 133 224 On Mon, April 16, 2007 12:14, Mark van Herpen wrote: > Hi, > > I want to backup my databases with mysqldump, but mysqldump won't run > because I use the 'local-infile=1' option in the my.cnf file: > > [client] > port= 3306 > socket = /tmp/mysql.sock > local-infile= 1 > > This is because I want php and other clients to use local-infile. This > works, by when I start mysqldump I got this error: > > ~ # mysqldump > mysqldump: unknown variable 'local-infile=1' > > So, what is wrong? As far as I know local-infile is a valid option to > put in the my.cnf. > > Is there a way to unset the local-infile option and start then start > mysqldump or something? Or any other solution? > > Grtz, > > Mark van Herpen > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] > > > -- > This message has been scanned for viruses and > dangerous content by OpenProtect(http://www.openprotect.com), and is > believed to be clean. > -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Problem with mysqldump and local-infile
Hi, I want to backup my databases with mysqldump, but mysqldump won't run because I use the 'local-infile=1' option in the my.cnf file: [client] port= 3306 socket = /tmp/mysql.sock local-infile= 1 This is because I want php and other clients to use local-infile. This works, by when I start mysqldump I got this error: ~ # mysqldump mysqldump: unknown variable 'local-infile=1' So, what is wrong? As far as I know local-infile is a valid option to put in the my.cnf. Is there a way to unset the local-infile option and start then start mysqldump or something? Or any other solution? Grtz, Mark van Herpen -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: problem with mysqldump when there is a merge table
Hi, Have you tried '\\' ? Mathias Selon nyem <[EMAIL PROTECTED]>: > Hello, > > I have a database (on Win2k) with merge table. Mysqldump output includes > some path information on the merged tables such as DATA DIRECTORY and > INDEX DIRECTORY > > DROP TABLE IF EXISTS `rptpricing1996`; > CREATE TABLE `rptpricing1996` ( > `PricingId` int(11) NOT NULL default '0', > `commodity` char(22) NOT NULL default '', > `variables` char(7) NOT NULL default '', > `PricingDt` date NOT NULL default '-00-00', > `PricingHighPrice` decimal(12,2) default NULL, > `PricingLowPrice` decimal(12,2) default NULL, > `PricingAvgPrice` decimal(12,2) default NULL, > PRIMARY KEY (`PricingId`), > KEY `commodityDate` (`commodity`,`PricingDt`) > ) ENGINE=MyISAM DEFAULT CHARSET=latin1 > DATA DIRECTORY='C:\SDVI\DB\mysql\data\dbsdvi\' > INDEX DIRECTORY='C:\SDVI\DB\mysql\data\dbsdvi\'; > > > When trying to load the database back (mysql dbsdvi < dbsdvi.dump) > the path information produces errors as mysql treats the \ character as > an escaped character. > > Removing the path information eliminates the error, but how do I tell > mysqldump not to output the path information? > > regards, > nyem > > > > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] > > Hope that helps :o) Mathias -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
problem with mysqldump when there is a merge table
Hello, I have a database (on Win2k) with merge table. Mysqldump output includes some path information on the merged tables such as DATA DIRECTORY and INDEX DIRECTORY DROP TABLE IF EXISTS `rptpricing1996`; CREATE TABLE `rptpricing1996` ( `PricingId` int(11) NOT NULL default '0', `commodity` char(22) NOT NULL default '', `variables` char(7) NOT NULL default '', `PricingDt` date NOT NULL default '-00-00', `PricingHighPrice` decimal(12,2) default NULL, `PricingLowPrice` decimal(12,2) default NULL, `PricingAvgPrice` decimal(12,2) default NULL, PRIMARY KEY (`PricingId`), KEY `commodityDate` (`commodity`,`PricingDt`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 DATA DIRECTORY='C:\SDVI\DB\mysql\data\dbsdvi\' INDEX DIRECTORY='C:\SDVI\DB\mysql\data\dbsdvi\'; When trying to load the database back (mysql dbsdvi < dbsdvi.dump) the path information produces errors as mysql treats the \ character as an escaped character. Removing the path information eliminates the error, but how do I tell mysqldump not to output the path information? regards, nyem -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Problem with mysqldump
-- Original message -- From: Tom Crimmins <[EMAIL PROTECTED]> > > $ mysqldump -u root -p govern > test.sql > Enter password: > mysqldump: Got error: 1017: Can't find file: './govern/VT_SY_LANGUAGE.frm' > (errno: 24) when using LOCK TABLES > perror says 24 is too many open files http://dev.mysql.com/doc/mysql/en/Not_enough_file_handles.html The manual says how to fix the problem. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Problem with mysqldump
perror 24 Error code 24: Too many open files Looks like you've hit a system limit. Michael Tom Crimmins wrote: In mysql version 4.1.7 running on Redhat 3ES I get the following error from mysql dump. $ mysqldump -u root -p govern > test.sql Enter password: mysqldump: Got error: 1017: Can't find file: './govern/VT_SY_LANGUAGE.frm' (errno: 24) when using LOCK TABLES This file does in fact exist and mysql has permission to access it. I can query this table and lock this table when running mysql client. I've found that people have had similar problems, but I have yet to find a solution. --- Tom Crimmins Interface Specialist Pottawattamie County, Iowa -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Problem with mysqldump
In mysql version 4.1.7 running on Redhat 3ES I get the following error from mysql dump. $ mysqldump -u root -p govern > test.sql Enter password: mysqldump: Got error: 1017: Can't find file: './govern/VT_SY_LANGUAGE.frm' (errno: 24) when using LOCK TABLES This file does in fact exist and mysql has permission to access it. I can query this table and lock this table when running mysql client. I've found that people have had similar problems, but I have yet to find a solution. --- Tom Crimmins Interface Specialist Pottawattamie County, Iowa -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Problem with mysqldump between two servers
Hello, I did a mysql dump of a database between two servers we have using the following command: mysqldump --opt -u --password= | mysql --host= -C -u --password= This command seemed to run ok as it transferred all the structure and data from the original server to the new server database. However, on closer inspection there is a problem. Many characters in the new database are showing up as a a question mark ? (e.g. characters such as ", trademark symbol, and fractions such as 1/3). If I edit this data using phpmyadmin and replace it with the relevant symbol manually then it is ok. The difference between versions of mysql on both servers are not that different: 3.23.58 - new server 3.23.52 - old server I got the status information when I logged into mysql on both servers, and it showed that they are both using the same character sets. Client characterset:latin1 Server characterset:latin1 According to the documentation, mysqldump in these versions dumps using latin1 character set by default. I did a dump of the database locally on the old server using the following command: mysqldump --opt -u --password= | mysql -C -u --password= I made a copy of the web site and pointed it at db_name_bak and all the characters in question displayed ok. So it does not look like a problem with the mysqldump output. It does look like there is some configuration issue on the new server regarding mysql, or maybe even php or apache, that is causing this. Or could there be some configuration in between the versions of Linux on the two servers. The old server is running red hat 7.3. The new server is running centos Any help would be appreciated. Thanks, Regards, Eugene. -- Eugene van den Hurk Rocket Media 118 Patrick St. Cork. http://www.rocketmedia.ie Tel: +353 21 4279517
Re: problem with mysqldump, ustf8 with mysql 4.1
"neal" <[EMAIL PROTECTED]> wrote: > I need to backup a mysql 4.1 database with UTF8 characters using InnoDB > and then restore the backup on another machine > > I tried the following (same machine - Windows XP) > mysqldump.exe -u root stp2 city > d1.sql# backup > stp2.city > mysql.exe -u root t1 < d1.sql # > restore to t1.city > > The UTF8 data in city.City is garbage after the transfer , it is valid > Thai language characters in the original. > > CREATE TABLE `city` ( > `city_id` int(11) NOT NULL default '0', > `City` varchar(25) NOT NULL default '', > `EngCity` varchar(25) NOT NULL default '', > PRIMARY KEY (`city_id`) > ) ENGINE=InnoDB DEFAULT CHARSET=utf8; Use --default-character-set option of mysqldump: http://www.mysql.com/doc/en/mysqldump.html -- 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]
problem with mysqldump, ustf8 with mysql 4.1
I need to backup a mysql 4.1 database with UTF8 characters using InnoDB and then restore the backup on another machine I tried the following (same machine - Windows XP) mysqldump.exe -u root stp2 city > d1.sql# backup stp2.city mysql.exe -u root t1 < d1.sql # restore to t1.city The UTF8 data in city.City is garbage after the transfer , it is valid Thai language characters in the original. CREATE TABLE `city` ( `city_id` int(11) NOT NULL default '0', `City` varchar(25) NOT NULL default '', `EngCity` varchar(25) NOT NULL default '', PRIMARY KEY (`city_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; Any help would be appreciated, Neal Katz
Re: problem with mysqldump
I had the same problem. It occurs when you try to load (3.23.51 or higher) dump file to lower version of MySQL. Look at this line... > /*!4 ALTER TABLE mobile_dev DISABLE KEYS */; As soon as version is not equal 4 everything in comments will be deleted. So we have > ; empty query. Mikhail. - Original Message - From: "Victoria Reznichenko" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 14, 2002 4:32 PM Subject: Re: problem with mysqldump > jan, > Tuesday, August 13, 2002, 12:34:23 PM, you wrote: > > jb> Hello i got a problem with mysqldump, > jb> i'm forced to dump it to to place the database on a new laptop > > > jb> mysql -u root -p hardwaredb < hardwaredbbackup.sql > jb> Enter password: > jb> ERROR 1065 at line 25: Query was empty > > > jb> and the corresponding line: > > jb> ) TYPE=MyISAM; > > jb> 25: /*!4 ALTER TABLE mobile_dev DISABLE KEYS */; > > jb> what may i do to correct it, to dump the database? > > What is the version of your 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 > > > > > - > 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: problem with mysqldump
jan, Tuesday, August 13, 2002, 12:34:23 PM, you wrote: jb> Hello i got a problem with mysqldump, jb> i'm forced to dump it to to place the database on a new laptop jb> mysql -u root -p hardwaredb < hardwaredbbackup.sql jb> Enter password: jb> ERROR 1065 at line 25: Query was empty jb> and the corresponding line: jb> ) TYPE=MyISAM; jb> 25: /*!4 ALTER TABLE mobile_dev DISABLE KEYS */; jb> what may i do to correct it, to dump the database? What is the version of your 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 - 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
problem with mysqldump
Hello i got a problem with mysqldump, i'm forced to dump it to to place the database on a new laptop mysql -u root -p hardwaredb < hardwaredbbackup.sql Enter password: ERROR 1065 at line 25: Query was empty and the corresponding line: ) TYPE=MyISAM; 25: /*!4 ALTER TABLE mobile_dev DISABLE KEYS */; what may i do to correct it, to dump the database? - 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: Problem with mysqldump when using query caching
Nick, Wednesday, April 10, 2002, 7:27:20 PM, you wrote: NP> I'm using Mysql 4.0.1 with query caching: NP> set-variable = query_cache_limit=10M NP> set-variable = query_cache_size=10M NP> set-variable = query_cache_startup_type=1 NP> The Command: NP> mysqldump -q -K -t --tab='.' \ NP> --fields-optionally-enclosed-by='"' \ NP> --fields-terminated-by=',' sched oweek NP> The first execution of the command writes the expected NP> data to oweek.txt. NP> Any subsequent executions do not. This is because of query caching. NP> I can run --> mysql -e "reset query cache" <-- which will enable NP> the next call to mysqldump to write data. NP> I believe that mysqldump should write data whether query caching NP> is enabled/disabled or not-flushed/flushed. Looks quite interesting, but can you please try to run that on MySQL official binary release? As it seems that you have compiled MySQL from source, and it's tricky to do that correctly. -- For technical support contracts, goto https://order.mysql.com/ This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ 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
Re: Problem with mysqldump when using query caching (4.01)
Ken, On Wed, Apr 10, 2002 at 01:24:46PM -0400, Ken Menzel wrote: > Hi Nick, >I am seeing some rather strange problem here with mysqldump, after > trying very hard to reproduce the problem on a test server, I gave > up. Do the options make any difference when you run it? Can you send ^^ If I run: mysqldump --result-file="oweek.dump" sched oweek I works every time. If I run: mysqldump -q -K -t --tab='.' \ --fields-optionally-enclosed-by='"' \ --fields-terminated-by=',' sched oweek It works the first time, when it is not query cached. Any subsequent executions, when it is cached, do not. If I clear the cache with: mysql -e "reset query cache" it will write data on the first execution but then stops writing data on any other tries. ---( Nick )--- > a trace of the actual dump? I was seeing mysqldump terminate in my > case, now it just seems to loop, and I am not sure why the behavior > changed. > > If we could reproduce this reliably maybe we could get a fix! Can you > do this everytime? > Ken > > - Original Message - > From: "Nick Pasich" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, April 10, 2002 12:27 PM > Subject: Problem with mysqldump when using query caching > > > > > > >Description: > > I'm using Mysql 4.0.1 with query caching: > > > > set-variable = query_cache_limit=10M > > set-variable = query_cache_size=10M > > set-variable = query_cache_startup_type=1 > > > > The Command: > > mysqldump -q -K -t --tab='.' \ > > --fields-optionally-enclosed-by='"' \ > > --fields-terminated-by=',' sched oweek > > > > The first execution of the command writes the expected > > data to oweek.txt. > > > > Any subsequent executions do not. This is because of query caching. > > I can run --> mysql -e "reset query cache" <-- which will enable > > the next call to mysqldump to write data. > > > > I believe that mysqldump should write data whether query caching > > is enabled/disabled or not-flushed/flushed. > > > > >How-To-Repeat: > > Execute a mysqldump command more than once. > > >Fix: > > > > >Submitter-Id: > > >Originator: Nick Pasich > > >Organization: > > >MySQL support: email support > > >Synopsis: Problem with mysqldump when using query caching > > >Severity: serious > > >Priority: medium > > >Category: mysql > > >Class: sw-bug > > >Release: mysql-4.0.1-alpha (Source distribution) > > >Server: /usr/local/MYSQL/bin/mysqladmin Ver 8.23 Distrib > 4.0.1-alpha, for pc-linux-gnu on i686 > > Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB > > This software comes with ABSOLUTELY NO WARRANTY. This is free > software, > > and you are welcome to modify and redistribute it under the GPL > license > > > > Server version 4.0.1-alpha-log > > Protocol version 10 > > Connection Localhost via UNIX socket > > UNIX socket /usr/local/MYSQL/mysql.sock > > Uptime: 13 hours 49 min 48 sec > > > > Threads: 2 Questions: 1653 Slow queries: 2 Opens: 135 Flush > tables: 15 Open tables: 3 Queries per second avg: 0.033 > > >Environment: > > > > System: Linux NICK 2.4.18-ac3 #1 Mon Mar 4 12:38:33 PST 2002 i586 > unknown > > Architecture: i586 > > > > Some paths: /usr/local/bin/perl /usr/bin/make /usr/bin/gmake > /usr/bin/gcc /usr/bin/cc > > GCC: Reading specs from > /usr/local/GCC/gcc-2.95.3/lib/gcc-lib/i586-pc-linux-gnulibc1/2.95.3/sp > ecs > > gcc version 2.95.3 20010315 (release) > > Compilation info: CC='gcc' CFLAGS='-O3 -march=i586' CXX='gcc' > CXXFLAGS='-O3 -march=i586 -felide-constructors -fno-exceptions -fno-rt > ti' LDFLAGS='' > > LIBC: > > lrwxrwxrwx1 root root 13 Feb 24 20:49 > /lib/libc.so.4 -> libc.so.4.7.6 > > -rwxr-xr-x1 root root 623620 Feb 26 1996 > /lib/libc.so.4.5.26 > > -rwxr-xr-x1 bin bin634880 Aug 13 1996 > /lib/libc.so.4.7.5 > > -rwxr-xr-x1 root wheel 634880 Apr 29 1996 > /lib/libc.so.4.7.6 > > lrwxrwxrwx1 root root 14 Feb 24 20:49 > /lib/libc.so.5 -> libc.so.5.4.46 > > -rwxr > > > > > - > > 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: Problem with mysqldump when using query caching
Hi Nick, I am seeing some rather strange problem here with mysqldump, after trying very hard to reproduce the problem on a test server, I gave up. Do the options make any difference when you run it? Can you send a trace of the actual dump? I was seeing mysqldump terminate in my case, now it just seems to loop, and I am not sure why the behavior changed. If we could reproduce this reliably maybe we could get a fix! Can you do this everytime? Ken - Original Message - From: "Nick Pasich" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 10, 2002 12:27 PM Subject: Problem with mysqldump when using query caching > > >Description: > I'm using Mysql 4.0.1 with query caching: > > set-variable = query_cache_limit=10M > set-variable = query_cache_size=10M > set-variable = query_cache_startup_type=1 > > The Command: > mysqldump -q -K -t --tab='.' \ > --fields-optionally-enclosed-by='"' \ > --fields-terminated-by=',' sched oweek > > The first execution of the command writes the expected > data to oweek.txt. > > Any subsequent executions do not. This is because of query caching. > I can run --> mysql -e "reset query cache" <-- which will enable > the next call to mysqldump to write data. > > I believe that mysqldump should write data whether query caching > is enabled/disabled or not-flushed/flushed. > > >How-To-Repeat: > Execute a mysqldump command more than once. > >Fix: > > >Submitter-Id: > >Originator: Nick Pasich > >Organization: > >MySQL support: email support > >Synopsis: Problem with mysqldump when using query caching > >Severity: serious > >Priority: medium > >Category: mysql > >Class: sw-bug > >Release: mysql-4.0.1-alpha (Source distribution) > >Server: /usr/local/MYSQL/bin/mysqladmin Ver 8.23 Distrib 4.0.1-alpha, for pc-linux-gnu on i686 > Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB > This software comes with ABSOLUTELY NO WARRANTY. This is free software, > and you are welcome to modify and redistribute it under the GPL license > > Server version 4.0.1-alpha-log > Protocol version 10 > Connection Localhost via UNIX socket > UNIX socket /usr/local/MYSQL/mysql.sock > Uptime: 13 hours 49 min 48 sec > > Threads: 2 Questions: 1653 Slow queries: 2 Opens: 135 Flush tables: 15 Open tables: 3 Queries per second avg: 0.033 > >Environment: > > System: Linux NICK 2.4.18-ac3 #1 Mon Mar 4 12:38:33 PST 2002 i586 unknown > Architecture: i586 > > Some paths: /usr/local/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc /usr/bin/cc > GCC: Reading specs from /usr/local/GCC/gcc-2.95.3/lib/gcc-lib/i586-pc-linux-gnulibc1/2.95.3/sp ecs > gcc version 2.95.3 20010315 (release) > Compilation info: CC='gcc' CFLAGS='-O3 -march=i586' CXX='gcc' CXXFLAGS='-O3 -march=i586 -felide-constructors -fno-exceptions -fno-rt ti' LDFLAGS='' > LIBC: > lrwxrwxrwx1 root root 13 Feb 24 20:49 /lib/libc.so.4 -> libc.so.4.7.6 > -rwxr-xr-x1 root root 623620 Feb 26 1996 /lib/libc.so.4.5.26 > -rwxr-xr-x1 bin bin634880 Aug 13 1996 /lib/libc.so.4.7.5 > -rwxr-xr-x1 root wheel 634880 Apr 29 1996 /lib/libc.so.4.7.6 > lrwxrwxrwx1 root root 14 Feb 24 20:49 /lib/libc.so.5 -> libc.so.5.4.46 > -rwxr > > - > 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
Problem with mysqldump when using query caching
>Description: I'm using Mysql 4.0.1 with query caching: set-variable = query_cache_limit=10M set-variable = query_cache_size=10M set-variable = query_cache_startup_type=1 The Command: mysqldump -q -K -t --tab='.' \ --fields-optionally-enclosed-by='"' \ --fields-terminated-by=',' sched oweek The first execution of the command writes the expected data to oweek.txt. Any subsequent executions do not. This is because of query caching. I can run --> mysql -e "reset query cache" <-- which will enable the next call to mysqldump to write data. I believe that mysqldump should write data whether query caching is enabled/disabled or not-flushed/flushed. >How-To-Repeat: Execute a mysqldump command more than once. >Fix: >Submitter-Id: >Originator:Nick Pasich >Organization: >MySQL support: email support >Synopsis: Problem with mysqldump when using query caching >Severity: serious >Priority: medium >Category: mysql >Class: sw-bug >Release: mysql-4.0.1-alpha (Source distribution) >Server: /usr/local/MYSQL/bin/mysqladmin Ver 8.23 Distrib 4.0.1-alpha, for >pc-linux-gnu on i686 Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license Server version 4.0.1-alpha-log Protocol version10 Connection Localhost via UNIX socket UNIX socket /usr/local/MYSQL/mysql.sock Uptime: 13 hours 49 min 48 sec Threads: 2 Questions: 1653 Slow queries: 2 Opens: 135 Flush tables: 15 Open tables: 3 Queries per second avg: 0.033 >Environment: System: Linux NICK 2.4.18-ac3 #1 Mon Mar 4 12:38:33 PST 2002 i586 unknown Architecture: i586 Some paths: /usr/local/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc /usr/bin/cc GCC: Reading specs from /usr/local/GCC/gcc-2.95.3/lib/gcc-lib/i586-pc-linux-gnulibc1/2.95.3/specs gcc version 2.95.3 20010315 (release) Compilation info: CC='gcc' CFLAGS='-O3 -march=i586' CXX='gcc' CXXFLAGS='-O3 -march=i586 -felide-constructors -fno-exceptions -fno-rtti' LDFLAGS='' LIBC: lrwxrwxrwx1 root root 13 Feb 24 20:49 /lib/libc.so.4 -> libc.so.4.7.6 -rwxr-xr-x1 root root 623620 Feb 26 1996 /lib/libc.so.4.5.26 -rwxr-xr-x1 bin bin634880 Aug 13 1996 /lib/libc.so.4.7.5 -rwxr-xr-x1 root wheel 634880 Apr 29 1996 /lib/libc.so.4.7.6 lrwxrwxrwx1 root root 14 Feb 24 20:49 /lib/libc.so.5 -> libc.so.5.4.46 -rwxr - 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: problem with mysqldump
Dear Agent Smith, as said, mysqldump is a command line program, not an SQL command. In PhpMyAdmin, use the CSV or SQL dump function built in. To dump a database, select the database (left frame), then click "dump database" (right frame), best with options "structure and data", "with drop table statement" and "save to file". When prompted, select a file name on your local machine. Then have a look at the file on your machine, and you will find you have a perfect dump to import whereever you need it :) Regards, Stefan Hinz (Geschäftsleitung) iConnect e-commerce solutions GmbH www.iConnect.de - www.js-webShop.de TEL +49 30 46307-382 - FAX -388 --- - Original Message - From: Agent Smith <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, August 05, 2001 4:28 AM Subject: problem with mysqldump > Hi everybody, > > I got a problem with the "mysqldump" function. > > I connect to mySql trough phpMyAdmin, select the database "xyz", which > is the only database on the server. > Then I enter the following string into the text field "Run SQL > query/queries on database xyz:": > > mysqldump xyz | mysql --host=XXX.168.XXX.14 --port=3306 > --socket=/var/mysql/mysql.sock --username=X --password[X] xyz > > I want to copy the whole databse from one server to the other, but i > always get th error message, > > MySQL said: You have an error in your SQL syntax near 'mysqldump > catfxpboard | mysql --host=194.168.102.14 --port=3306 --socket=/var/my' > at line 1 > > But I can't find a mistake there!? Can you helpp me? > > > 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 > - 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: problem with mysqldump
Hi, Agent Smith wrote: > > Hi everybody, > > I got a problem with the "mysqldump" function. > > I connect to mySql trough phpMyAdmin, select the database "xyz", which > is the only database on the server. > Then I enter the following string into the text field "Run SQL > query/queries on database xyz:": > > mysqldump xyz | mysql --host=XXX.168.XXX.14 --port=3306 > --socket=/var/mysql/mysql.sock --username=X --password[X] xyz > > I want to copy the whole databse from one server to the other, but i > always get th error message, > > MySQL said: You have an error in your SQL syntax near 'mysqldump > catfxpboard | mysql --host=194.168.102.14 --port=3306 --socket=/var/my' > at line 1 mysqldump is not an SQL command. mysqldump is a program that must be run from the command line. > > But I can't find a mistake there!? Can you helpp me? > > Thanks! > -- Joseph Bueno NetClub/Trader.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
problem with mysqldump
Hi everybody, I got a problem with the "mysqldump" function. I connect to mySql trough phpMyAdmin, select the database "xyz", which is the only database on the server. Then I enter the following string into the text field "Run SQL query/queries on database xyz:": mysqldump xyz | mysql --host=XXX.168.XXX.14 --port=3306 --socket=/var/mysql/mysql.sock --username=X --password[X] xyz I want to copy the whole databse from one server to the other, but i always get th error message, MySQL said: You have an error in your SQL syntax near 'mysqldump catfxpboard | mysql --host=194.168.102.14 --port=3306 --socket=/var/my' at line 1 But I can't find a mistake there!? Can you helpp me? 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: Problem with mysqldump....
To import you should do cat filename | mysql -uusername -ppassword databasename ryan - Original Message - From: "Rachel-MY" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 01, 2001 9:38 PM Subject: Problem with mysqldump Hi everyone, I'm trying to backup all the databases from Server_A to Server_B. I'd issue "mysqldump" command in server_A to backup every single database, as below :- > mysqldump -uusername -ppassword databases_name > file_name In server_B, i create a new database using the command below :- > mysqladmin -uusername -ppassword create database_name Then... i issued another "mysqldump" command to put everything back to server_B, as below:- > mysqldump -uusername -ppassword databases_name < file_name Problem happened where the databases being backup are all empty!! No tables being copied!! Anyone have idea on this? - 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: Problem with mysqldump....
Dont use mysqldump to import. Use mysql. I can't remember the exact syntax, but reference mysql.com for mysqldump, then in the syntax example for that, they show you how to import it. Ryan Shrout Production Manager Amdmb.com http://www.amdmb.com/ [EMAIL PROTECTED] (859) 653-3341 - Original Message - From: "Rachel-MY" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 01, 2001 10:38 PM Subject: Problem with mysqldump Hi everyone, I'm trying to backup all the databases from Server_A to Server_B. I'd issue "mysqldump" command in server_A to backup every single database, as below :- > mysqldump -uusername -ppassword databases_name > file_name In server_B, i create a new database using the command below :- > mysqladmin -uusername -ppassword create database_name Then... i issued another "mysqldump" command to put everything back to server_B, as below:- > mysqldump -uusername -ppassword databases_name < file_name Problem happened where the databases being backup are all empty!! No tables being copied!! Anyone have idea on this? _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.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
Problem with mysqldump....
Hi everyone, I'm trying to backup all the databases from Server_A to Server_B. I'd issue "mysqldump" command in server_A to backup every single database, as below :- > mysqldump -uusername -ppassword databases_name > file_name In server_B, i create a new database using the command below :- > mysqladmin -uusername -ppassword create database_name Then... i issued another "mysqldump" command to put everything back to server_B, as below:- > mysqldump -uusername -ppassword databases_name < file_name Problem happened where the databases being backup are all empty!! No tables being copied!! Anyone have idea on this?
Problem with mysqldump and importing the data.
I used mysqldump to backup a database before I ran a structure change script on it. Well, things didnt work right, so I deleted the database, recreated it, and tried to import the data again. No luck. I am getting this error message.. [root@fg tep_catalog-pr2.1]# mysql -p catalog/ < /root/tep_catalog-pr2.1/backup.sql Enter password: ERROR 1136 at line 711: Column count doesn't match value count at row 1 How can something so simple.. mess up? ARGHLAH Thanks for any help.. -dre - 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
Problem with mysqldump - Segmentation Fault
cerveja:/var/lib/mysql# mysqldump -e -l -F -h champagne velop > champagne.velop.20010214.dump Segmentation fault cerveja:/var/lib/mysql# :/ --- Tenha uma conta de email Grátis no ACBusca! - 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
