Re: mysqldump problem with large innodb tables...
Try to look for Lost connection error in MySQL manual and it can give your some hints like http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html Dusan Hartleigh Burton napsal(a): Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. If anyone can help me out with this problem the assistance is greatly appreciated. I have scoured google and various other sources and not found much information that has been useful to me. I hope I have enough info below... if more is required let me know. mysqldump example P:\mysqldump -u username -p mraentertainment mraentertainment.sql --opt --verbose --max_allowed_packet=500M --hex-blob --single_transaction --net_buffer_length=100M Enter password: ** -- Connecting to localhost... -- Retrieving table structure for table albums... -- Sending SELECT query... ... -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 my.ini configuration file [client] port=3306 [mysql] default-character-set=latin1 [mysqld] log-bin=itd002-bin server-id=1 port=3306 wait_timeout=86400 max_allowed_packet=100M basedir=C:/Program Files/MySQL/MySQL Server 5.0/ datadir=C:/Program Files/MySQL/MySQL Server 5.0/Data/ default-character-set=latin1 default-storage-engine=INNODB sql-mode=STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION max_connections=100 query_cache_size=0 table_cache=256 tmp_table_size=77M thread_cache_size=8 #*** MyISAM Specific options myisam_max_sort_file_size=100G myisam_max_extra_sort_file_size=100G myisam_sort_buffer_size=154M key_buffer_size=130M read_buffer_size=64K read_rnd_buffer_size=256K sort_buffer_size=256K #skip-innodb innodb_additional_mem_pool_size=6M innodb_flush_log_at_trx_commit=1 innodb_log_buffer_size=3M innodb_buffer_pool_size=252M innodb_log_file_size=126M innodb_thread_concurrency=8 Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: {Spam?} Re: mysqldump problem with large innodb tables...
Have you considered using the archive storage engine? I have gotten 30:1
compression using it.
Create table archive_multimedia engine=Archive as select * from multimedia
table
John Mancuso
Linux Administrator/MySQL DBA
IT Infrastructure
American Home Mortgage
w: 631-622-6382
c: 516-652-2475
-Original Message-
From: Dušan Pavlica [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 19, 2007 5:08 AM
To: Hartleigh Burton
Cc: MySql
Subject: {Spam?} Re: mysqldump problem with large innodb tables...
Try to look for Lost connection error in MySQL manual and it can give your some
hints like http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html
Dusan
Hartleigh Burton napsal(a):
Hi All,
I have a database which is currently at ~10GB in it's test phase. It
is containing uncompressed audio and is expected to reach 1.5TB in no
time at all. I am just running some backup tests and I have been
having lots of problems creating an accurate backup.
I have tried both MySQL Administrator mysqldump, both applications
drop out on the same table, the table `trackdata` which contains ~9GB
worth of data. There is no single row any larger than 50MB, most
average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt
and all tables are InnoDB.
If anyone can help me out with this problem the assistance is greatly
appreciated. I have scoured google and various other sources and not
found much information that has been useful to me. I hope I have
enough info below... if more is required let me know.
mysqldump example
P:\mysqldump -u username -p mraentertainment mraentertainment.sql
--opt --verbose --max_allowed_packet=500M --hex-blob
--single_transaction --net_buffer_length=100M Enter password: **
-- Connecting to localhost...
-- Retrieving table structure for table albums...
-- Sending SELECT query...
...
-- Retrieving rows...
-- Retrieving table structure for table trackdata...
-- Sending SELECT query...
-- Retrieving rows...
mysqldump: Error 2013: Lost connection to MySQL server during query
when dumping table `trackdata` at row: 1
my.ini configuration file
[client]
port=3306
[mysql]
default-character-set=latin1
[mysqld]
log-bin=itd002-bin
server-id=1
port=3306
wait_timeout=86400
max_allowed_packet=100M
basedir=C:/Program Files/MySQL/MySQL Server 5.0/
datadir=C:/Program Files/MySQL/MySQL Server 5.0/Data/
default-character-set=latin1
default-storage-engine=INNODB
sql-mode=STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
max_connections=100
query_cache_size=0
table_cache=256
tmp_table_size=77M
thread_cache_size=8
#*** MyISAM Specific options
myisam_max_sort_file_size=100G
myisam_max_extra_sort_file_size=100G
myisam_sort_buffer_size=154M
key_buffer_size=130M
read_buffer_size=64K
read_rnd_buffer_size=256K
sort_buffer_size=256K
#skip-innodb
innodb_additional_mem_pool_size=6M
innodb_flush_log_at_trx_commit=1
innodb_log_buffer_size=3M
innodb_buffer_pool_size=252M
innodb_log_file_size=126M
innodb_thread_concurrency=8
Regards,
Hartleigh Burton
Resident Geek
MRA Entertainment Pty Ltd
5 Dividend St | Mansfield | QLD 4122 | Australia
Phone: (07) 3457 5041
Fax: (07) 3349 8806
Mobile: 0421 646 978
www.mraentertainment.com
Internal Virus Database was built: Never
Checked by MAC OSX... we don't get viruses!
--
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: mysqldump problem with large innodb tables...
Hi Dusan, You replied to a forum post of mine on mysql.com yeah? ;) I have tried adjusting the max_allowed_packet on both the server and client. Both are set to 1G now (apparently the highest value accepted) even though each row is no larger than 100M at very most. I am thinking this may have something to do with --extended-insert. So rather than having all of data in an extended insert I have tried disabling this feature with --extended-insert=0, --extended- insert=false, --skip-extended-insert (not all at once obviously)... am I doing this correctly? Mixed results when I search google for answers. I don't really care at this stage if backup/restore times are reduced with this feature disabled, as long as I can get an accurate backup. I also set --net_buffer_length=800M; in theory --extended-insert will only create queries up to this value, so if I keep it lower than the --max_allowed_packet value it should all be sweet. Still no cigar unfortunately. On 19/06/2007, at 7:08 PM, Dušan Pavlica wrote: Try to look for Lost connection error in MySQL manual and it can give your some hints like http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html Dusan Hartleigh Burton napsal(a): Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. If anyone can help me out with this problem the assistance is greatly appreciated. I have scoured google and various other sources and not found much information that has been useful to me. I hope I have enough info below... if more is required let me know. mysqldump example P:\mysqldump -u username -p mraentertainment mraentertainment.sql --opt --verbose --max_allowed_packet=500M --hex-blob --single_transaction --net_buffer_length=100M Enter password: ** -- Connecting to localhost... -- Retrieving table structure for table albums... -- Sending SELECT query... ... -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 my.ini configuration file [client] port=3306 [mysql] default-character-set=latin1 [mysqld] log-bin=itd002-bin server-id=1 port=3306 wait_timeout=86400 max_allowed_packet=100M basedir=C:/Program Files/MySQL/MySQL Server 5.0/ datadir=C:/Program Files/MySQL/MySQL Server 5.0/Data/ default-character-set=latin1 default-storage-engine=INNODB sql- mode=STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION max_connections=100 query_cache_size=0 table_cache=256 tmp_table_size=77M thread_cache_size=8 #*** MyISAM Specific options myisam_max_sort_file_size=100G myisam_max_extra_sort_file_size=100G myisam_sort_buffer_size=154M key_buffer_size=130M read_buffer_size=64K read_rnd_buffer_size=256K sort_buffer_size=256K #skip-innodb innodb_additional_mem_pool_size=6M innodb_flush_log_at_trx_commit=1 innodb_log_buffer_size=3M innodb_buffer_pool_size=252M innodb_log_file_size=126M innodb_thread_concurrency=8 Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql? [EMAIL PROTECTED] Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses!
Re: mysqldump problem with large innodb tables...
My backups use mysqldump, but they have always just worked. I would suggest you try to make a minimal test case that can reproduce the problem and submit it as a bug report, if possible. I'm not familiar with the error message off-hand, but the InnoDB manual is large and complete, so I'm sure it is covered in there. Baron Hartleigh Burton wrote: Ok... this error has just started popping up in my .err log file... 070618 14:31:10 InnoDB: ERROR: the age of the last checkpoint is 237821842, InnoDB: which exceeds the log group capacity 237813351. 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. 070618 14:39:17 InnoDB: ERROR: the age of the last checkpoint is 237829009, InnoDB: which exceeds the log group capacity 237813351. 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. On 18/06/2007, at 12:09 PM, Baron Schwartz wrote: I'm out of ideas right now. I don't actually use mysqldump that much and have never had this happen. Hopefully someone else on the mailing list can help, or perhaps you can try #mysql on Freenode IRC. Baron Hartleigh Burton wrote: No there is no indication of that at all. The server service appears to be in perfect order, does not drop/restart and my other applications continue to function without any interruption. It appears as if the mysqldump connection to the server is interrupted or maybe there is something in row 1 of `trackdata` that it does not like. This table contains a long blob field which at present does not contain any more than ~80MB per row. I also use the --hex-blob flag for mysqldump to try and get around any possible problems with exporting this data... I have no descriptive error messages anywhere and it is driving me nuts :| On 18/06/2007, at 11:27 AM, Baron Schwartz wrote: Is there any indication that the mysqldump crash is killing the server and causing it to restart? For example, ready for connections notifications just after you try a mysqldump? Hartleigh Burton wrote: H no there are no new errors in there. Nothing out of the ordinary thats for sure. Just notifications that MySQL has started and is accepting connections etc. :| On 18/06/2007, at 11:06 AM, Baron Schwartz wrote: How about in c:\Program Files\MySQL\MySQL Server 5.0\data\hostname.err? Cheers Baron Hartleigh Burton wrote: Hi Baron, There are no MySQL errors in the event viewer. On 18/06/2007, at 10:36 AM, Baron Schwartz wrote: Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. [snip] -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 You might be able to find more information about the precise error in the server's error logs. That will give us a better idea what might be wrong, if there is an error server-side, which seems likely to me. Baron Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! --MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! --MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia
mysqldump problem with large innodb tables...
Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. If anyone can help me out with this problem the assistance is greatly appreciated. I have scoured google and various other sources and not found much information that has been useful to me. I hope I have enough info below... if more is required let me know. mysqldump example P:\mysqldump -u username -p mraentertainment mraentertainment.sql --opt --verbose --max_allowed_packet=500M --hex-blob --single_transaction --net_buffer_length=100M Enter password: ** -- Connecting to localhost... -- Retrieving table structure for table albums... -- Sending SELECT query... ... -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 my.ini configuration file [client] port=3306 [mysql] default-character-set=latin1 [mysqld] log-bin=itd002-bin server-id=1 port=3306 wait_timeout=86400 max_allowed_packet=100M basedir=C:/Program Files/MySQL/MySQL Server 5.0/ datadir=C:/Program Files/MySQL/MySQL Server 5.0/Data/ default-character-set=latin1 default-storage-engine=INNODB sql- mode=STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION max_connections=100 query_cache_size=0 table_cache=256 tmp_table_size=77M thread_cache_size=8 #*** MyISAM Specific options myisam_max_sort_file_size=100G myisam_max_extra_sort_file_size=100G myisam_sort_buffer_size=154M key_buffer_size=130M read_buffer_size=64K read_rnd_buffer_size=256K sort_buffer_size=256K #skip-innodb innodb_additional_mem_pool_size=6M innodb_flush_log_at_trx_commit=1 innodb_log_buffer_size=3M innodb_buffer_pool_size=252M innodb_log_file_size=126M innodb_thread_concurrency=8 Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses!
Re: mysqldump problem with large innodb tables...
Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. [snip] -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 You might be able to find more information about the precise error in the server's error logs. That will give us a better idea what might be wrong, if there is an error server-side, which seems likely to me. Baron -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqldump problem with large innodb tables...
Hi Baron, There are no MySQL errors in the event viewer. On 18/06/2007, at 10:36 AM, Baron Schwartz wrote: Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. [snip] -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 You might be able to find more information about the precise error in the server's error logs. That will give us a better idea what might be wrong, if there is an error server-side, which seems likely to me. Baron Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses!
Re: mysqldump problem with large innodb tables...
How about in c:\Program Files\MySQL\MySQL Server 5.0\data\hostname.err? Cheers Baron Hartleigh Burton wrote: Hi Baron, There are no MySQL errors in the event viewer. On 18/06/2007, at 10:36 AM, Baron Schwartz wrote: Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. [snip] -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 You might be able to find more information about the precise error in the server's error logs. That will give us a better idea what might be wrong, if there is an error server-side, which seems likely to me. Baron Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqldump problem with large innodb tables...
H no there are no new errors in there. Nothing out of the ordinary thats for sure. Just notifications that MySQL has started and is accepting connections etc. :| On 18/06/2007, at 11:06 AM, Baron Schwartz wrote: How about in c:\Program Files\MySQL\MySQL Server 5.0\data \hostname.err? Cheers Baron Hartleigh Burton wrote: Hi Baron, There are no MySQL errors in the event viewer. On 18/06/2007, at 10:36 AM, Baron Schwartz wrote: Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. [snip] -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 You might be able to find more information about the precise error in the server's error logs. That will give us a better idea what might be wrong, if there is an error server-side, which seems likely to me. Baron Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql? [EMAIL PROTECTED] Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses!
Re: mysqldump problem with large innodb tables...
Is there any indication that the mysqldump crash is killing the server and causing it to restart? For example, ready for connections notifications just after you try a mysqldump? Hartleigh Burton wrote: H no there are no new errors in there. Nothing out of the ordinary thats for sure. Just notifications that MySQL has started and is accepting connections etc. :| On 18/06/2007, at 11:06 AM, Baron Schwartz wrote: How about in c:\Program Files\MySQL\MySQL Server 5.0\data\hostname.err? Cheers Baron Hartleigh Burton wrote: Hi Baron, There are no MySQL errors in the event viewer. On 18/06/2007, at 10:36 AM, Baron Schwartz wrote: Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. [snip] -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 You might be able to find more information about the precise error in the server's error logs. That will give us a better idea what might be wrong, if there is an error server-side, which seems likely to me. Baron Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! --MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqldump problem with large innodb tables...
No there is no indication of that at all. The server service appears to be in perfect order, does not drop/restart and my other applications continue to function without any interruption. It appears as if the mysqldump connection to the server is interrupted or maybe there is something in row 1 of `trackdata` that it does not like. This table contains a long blob field which at present does not contain any more than ~80MB per row. I also use the --hex-blob flag for mysqldump to try and get around any possible problems with exporting this data... I have no descriptive error messages anywhere and it is driving me nuts :| On 18/06/2007, at 11:27 AM, Baron Schwartz wrote: Is there any indication that the mysqldump crash is killing the server and causing it to restart? For example, ready for connections notifications just after you try a mysqldump? Hartleigh Burton wrote: H no there are no new errors in there. Nothing out of the ordinary thats for sure. Just notifications that MySQL has started and is accepting connections etc. :| On 18/06/2007, at 11:06 AM, Baron Schwartz wrote: How about in c:\Program Files\MySQL\MySQL Server 5.0\data \hostname.err? Cheers Baron Hartleigh Burton wrote: Hi Baron, There are no MySQL errors in the event viewer. On 18/06/2007, at 10:36 AM, Baron Schwartz wrote: Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. [snip] -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 You might be able to find more information about the precise error in the server's error logs. That will give us a better idea what might be wrong, if there is an error server-side, which seems likely to me. Baron Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! --MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql? [EMAIL PROTECTED] Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses!
Re: mysqldump problem with large innodb tables...
I'm out of ideas right now. I don't actually use mysqldump that much and have never had this happen. Hopefully someone else on the mailing list can help, or perhaps you can try #mysql on Freenode IRC. Baron Hartleigh Burton wrote: No there is no indication of that at all. The server service appears to be in perfect order, does not drop/restart and my other applications continue to function without any interruption. It appears as if the mysqldump connection to the server is interrupted or maybe there is something in row 1 of `trackdata` that it does not like. This table contains a long blob field which at present does not contain any more than ~80MB per row. I also use the --hex-blob flag for mysqldump to try and get around any possible problems with exporting this data... I have no descriptive error messages anywhere and it is driving me nuts :| On 18/06/2007, at 11:27 AM, Baron Schwartz wrote: Is there any indication that the mysqldump crash is killing the server and causing it to restart? For example, ready for connections notifications just after you try a mysqldump? Hartleigh Burton wrote: H no there are no new errors in there. Nothing out of the ordinary thats for sure. Just notifications that MySQL has started and is accepting connections etc. :| On 18/06/2007, at 11:06 AM, Baron Schwartz wrote: How about in c:\Program Files\MySQL\MySQL Server 5.0\data\hostname.err? Cheers Baron Hartleigh Burton wrote: Hi Baron, There are no MySQL errors in the event viewer. On 18/06/2007, at 10:36 AM, Baron Schwartz wrote: Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. [snip] -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 You might be able to find more information about the precise error in the server's error logs. That will give us a better idea what might be wrong, if there is an error server-side, which seems likely to me. Baron Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! --MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqldump problem with large innodb tables...
Ok... this error has just started popping up in my .err log file... 070618 14:31:10 InnoDB: ERROR: the age of the last checkpoint is 237821842, InnoDB: which exceeds the log group capacity 237813351. 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. 070618 14:39:17 InnoDB: ERROR: the age of the last checkpoint is 237829009, InnoDB: which exceeds the log group capacity 237813351. 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. On 18/06/2007, at 12:09 PM, Baron Schwartz wrote: I'm out of ideas right now. I don't actually use mysqldump that much and have never had this happen. Hopefully someone else on the mailing list can help, or perhaps you can try #mysql on Freenode IRC. Baron Hartleigh Burton wrote: No there is no indication of that at all. The server service appears to be in perfect order, does not drop/restart and my other applications continue to function without any interruption. It appears as if the mysqldump connection to the server is interrupted or maybe there is something in row 1 of `trackdata` that it does not like. This table contains a long blob field which at present does not contain any more than ~80MB per row. I also use the --hex-blob flag for mysqldump to try and get around any possible problems with exporting this data... I have no descriptive error messages anywhere and it is driving me nuts :| On 18/06/2007, at 11:27 AM, Baron Schwartz wrote: Is there any indication that the mysqldump crash is killing the server and causing it to restart? For example, ready for connections notifications just after you try a mysqldump? Hartleigh Burton wrote: H no there are no new errors in there. Nothing out of the ordinary thats for sure. Just notifications that MySQL has started and is accepting connections etc. :| On 18/06/2007, at 11:06 AM, Baron Schwartz wrote: How about in c:\Program Files\MySQL\MySQL Server 5.0\data \hostname.err? Cheers Baron Hartleigh Burton wrote: Hi Baron, There are no MySQL errors in the event viewer. On 18/06/2007, at 10:36 AM, Baron Schwartz wrote: Hi Hartleigh, Hartleigh Burton wrote: Hi All, I have a database which is currently at ~10GB in it's test phase. It is containing uncompressed audio and is expected to reach 1.5TB in no time at all. I am just running some backup tests and I have been having lots of problems creating an accurate backup. I have tried both MySQL Administrator mysqldump, both applications drop out on the same table, the table `trackdata` which contains ~9GB worth of data. There is no single row any larger than 50MB, most average around 40MB. Windows 2000 Server, MySQL v5.0.37-community-nt and all tables are InnoDB. [snip] -- Retrieving rows... -- Retrieving table structure for table trackdata... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `trackdata` at row: 1 You might be able to find more information about the precise error in the server's error logs. That will give us a better idea what might be wrong, if there is an error server-side, which seems likely to me. Baron Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! --MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql? [EMAIL PROTECTED] Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql? [EMAIL PROTECTED] Regards, Hartleigh Burton Resident Geek MRA Entertainment Pty Ltd 5 Dividend St | Mansfield | QLD 4122 | Australia Phone: (07) 3457 5041 Fax: (07) 3349 8806 Mobile: 0421 646 978 www.mraentertainment.com Internal Virus Database was built: Never Checked by MAC OSX... we don't get viruses!
mysqldump problem
hi all, I have got a problem with mysql and i want to uninstall it and then re-install it but the problem is how to recover my data.My mysqldump command is not working.Can i have any other procedure to recover my data like copying the folder of my database from the data folder and then making a backup.But when i tried i m getting the following error as * databasename.tablename doesn't exist* Can anyone give me the solution asap. Thanks and regards, venu
Re: mysqldump problem
On 2006-11-09 VenuGopal Papasani wrote: hi all, I have got a problem with mysql and i want to uninstall it and then re-install it but the problem is how to recover my data. This seldom solves problems. What problem do you have, maybe we can help without having you uninstall your server :) My mysqldump command is not working. hat does it do wrong? (hint: remember max_allowed_packet for big tables and use --opt). Can i have any other procedure to recover my data like copying the folder of my database from the data folder and then making a backup. If you are using MyISAM/ISAM/BDB it's safe to copy the tables *IF* the server is shutdown (else it could have data in memory that was not yet written to disk). But when i tried i m getting the following error as * databasename.tablename doesn't exist* Who gives you that error? /bin/cp? Or an SQL command? What does find /var/lib/mysql/ -ls and df -h say? bye, -christian- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqldump problem
VenuGopal Papasani wrote: hi all, I have got a problem with mysql and i want to uninstall it and then re-install it but the problem is how to recover my data.My mysqldump command is not working.Can i have any other procedure to recover my data like copying the folder of my database from the data folder and then making a backup.But when i tried i m getting the following error as * databasename.tablename doesn't exist* Can anyone give me the solution asap. Thanks and regards, venu Hi, May be i find a solution for you. I write a bash script for linux users to backup database and upload database it's very simple. If you want to try it please visit : www.witkey.org/vt.php and take it. ( Program Language: Turkish :) ) Cincerly, Onur Yerlikaya -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Fw: Error from mysqldump - problem solved
I've resolved my problem with mysqldump. I read the error message yet again
and it suddenly dawned on me what the problem might be. I made a slight
modification in my table name and, sure enough, the problem went away.
The problem lay in the fact that my table name was References. That's right,
the same word that is a keyword in the Foreign Key clause, as in Foreign
key (id) references tmp.foo(id) on delete restrict. Using References as a
table name had initially caused me grief when creating the table and when
defining foreign keys that used it as a primary table. I'd eventually gotten
past all those problems by putting backtics around each use of References
as a table name. It didn't occur to me until I finally reread the error
message this morning that the table name was biting me again within the
mysqldump command.
All I did was drop the References table then recreate the tables so that the
former References was now called Reference and everything worked
perfectly again. I can't believe I didn't see this right from the start. Oh
well, live and learn
I just thought I should follow up so that anyone following this thread now
or in the archives will know how it was resolved.
Rhino
- Original Message -
From: Rhino [EMAIL PROTECTED]
To: Rhino [EMAIL PROTECTED]; gerald_clark
[EMAIL PROTECTED]
Cc: mysql mysql@lists.mysql.com
Sent: Thursday, January 19, 2006 11:15 AM
Subject: Re: Error from mysqldump
Just as a followup to my own remarks, I've tried running my backup script
with the new syntax that Gerald suggested. I was going to wait for the
normal daily backup but I was eager to see if the new version would work
better so I just ran it from the command line.
Unfortunately, it came back with the same error. The new syntax is still
cleaner and I'm going to keep it but I'm back to square one in determining
why the mysqldump of this one database is giving me trouble.
Does anyone have any ideas?
Rhino
- Original Message -
From: Rhino [EMAIL PROTECTED]
To: gerald_clark [EMAIL PROTECTED]
Cc: mysql mysql@lists.mysql.com
Sent: Thursday, January 19, 2006 10:53 AM
Subject: Re: Error from mysqldump
- Original Message -
From: gerald_clark [EMAIL PROTECTED]
To: Rhino [EMAIL PROTECTED]
Cc: mysql mysql@lists.mysql.com
Sent: Thursday, January 19, 2006 9:30 AM
Subject: Re: Error from mysqldump
Rhino wrote:
I have an automated backup script that has been running daily for a
couple of years now. It has never given me trouble until the last two
days. For the last two days, I have been getting this message when
backing up my newest database:
/usr/bin/mysqldump: Got error: 1064: You have an error in your SQL
syntax. Check the manual that corresponds to your MySQL server version
for the right syntax to use near 'References READ /*!32311 LOCAL */' at
line 1 when using LOCK TABLES
This is the relevant portion of my backup script:
for ONE_DBNAME in `echo show databases | mysql -s -u
$USERID -p$PASSWORD`
do
echo
echo Backing up database $ONE_DBNAME;
/usr/bin/mysqldump --opt --verbose -u${USERID} -p${PASSWORD}
${ONE_DBNAME} -r
${BACKUP_PATH}/${ONE_DBNAME}.${BACKUP_TIMESTAMP}.sql
I would look here. This is a dangerous expansion. A space or ';' in any
of these variables my generate unwanted commands.
Use quotes around the argument to -r.
Try.
/usr/bin/mysqldump --opt --verbose -u${USERID} -p${PASSWORD}
${ONE_DBNAME} -r ${BACKUP_PATH}/${ONE_DBNAME}.${BACKUP_TIMESTAMP}.sql
or /usr/bin/mysqldump --opt --verbose -u${USERID} -p${PASSWORD}
${ONE_DBNAME} ${BACKUP_PATH}/${ONE_DBNAME}.${BACKUP_TIMESTAMP}.sql
Okay, fair enough, I've never claimed to be a bash expert ;-) I think
your proposed change is an improvement: it is clearer and easier to read.
I'll give this version a try for the next few days and see if it works
any better.
But I'm still not sure why this version might solve my problem. Wouldn't
an expansion issue cause problems for all of my databases, not just one?
I'm trying to understand why only one database is affected and why only
the newest one when the script has worked fine for many months with the
older databases.
echo Deleting these old backups for this database...
/usr/bin/find ${BACKUP_PATH} -mtime
+$NUMBER_OF_DAILY_BACKUPS_TO_KEEP -name $ONE_DBNAME'*' -print; #display
old backups (if any)
/usr/bin/find ${BACKUP_PATH} -mtime
+$NUMBER_OF_DAILY_BACKUPS_TO_KEEP -name $ONE_DBNAME'*' -exec rm '{}'
';' #delete old backups (if any)
done
I'm at a loss to see why I'm getting this error for only one database
when the exact same logic is applied for each of my databases and works
fine for all the others.
I've tried doing the backup manually from the command line and found
that I got the same error when I tried to backup the Maximal database
that way; a manual backup of another database worked fine.
The only idea I have that seems vaguely plausible is that there is
something internally
Re: MySQLDUMP Problem
On Thursday 18 August 2005 09:34, Carlos J Souza wrote: Sirs, When i use mysqldump on Version 4.1.x, all tables had a one record insert generated in script. When i use mysqldump on a 4.0.x version this problem dos not occurs. How to solve it? That's because extended inserts are on by default in 4.1.x. To get multiple inserts (usually slower) use a command like: mysqldump --skip-extended-insert mydatabase mydatabase.sql -- Jeff Shapiro listserv only address -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQLDUMP Problem
Sirs, When i use mysqldump on Version 4.1.x, all tables had a one record insert generated in script. When i use mysqldump on a 4.0.x version this problem dos not occurs. How to solve it? Regards For all Carlos J Souza -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Mysqldump Problem
Sirs, When i use mysqldump on Version 4.1.x, all tables had a one record insert generated in script. When i use mysqldump on a 4.0.x version this problem does not occurs. How to solve it? Regards For all Carlos J Souza -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysqldump Problem
Carlos J Souza [EMAIL PROTECTED] wrote on 08/18/2005 03:16:15 PM: Sirs, When i use mysqldump on Version 4.1.x, all tables had a one record insert generated in script. When i use mysqldump on a 4.0.x version this problem does not occurs. How to solve it? Regards For all Carlos J Souza I think that generating the INSERT statement (the 4.1.x behavior) should not be a problem. Can you try again to describe what it is you would like to do, how you are trying to do it, and what is not happening in the manner you desire? I can tell that English is not your native language. I usually do not make this suggestion (as this is an English mailing list) but there are several on the list that do speak Portuguese (and Spanish) so perhaps you could try describing your problem that way, too. Shawn Green Database Administrator Unimin Corporation - Spruce Pine
RE: Mysqldump Problem
Carlos J Souza wrote: Sirs, When i use mysqldump on Version 4.1.x, all tables had a one record insert generated in script. When i use mysqldump on a 4.0.x version this problem does not occurs. How to solve it? Not 100% sure what you are looking for, but try using --skip-extended-insert. -Ryan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysqldump Problem
I think what you are seeing is called the extended insert format. It's much faster to process a single large INSERT statement than several smaller ones. There are two things to remember: a) if you have a lot of data in your table, an extended insert statement may become too long to re-read into your server as a single chunk. You can tell mysqldump to create an extended insert statement in chunks of a certain size if you tell mysqldump just how big you want those chunks to be. Use the --max_allowed_packet= option to keep your extended inserts down to a certain maximum size. The largest useful packet is that which matches the max_allowed_packet variable value for the server receiving the data. Any larger than that and the restore will fail. b) you can disable the extended inserts completely if you run mysqldump with the --skip-extended-insert option To see all of the options supported by mysqldump, use the --help option like this: mysqldump --help And, one last thing, when responding to help from the list, please do not forget to CC the list. I could have been called away or unable to answer for an extended period of time and anyone else on the list could have helped in my place. Shawn Green Database Administrator Unimin Corporation - Spruce Pine Carlos J Souza [EMAIL PROTECTED] wrote on 08/18/2005 03:42:36 PM: Shawn, it sees that in the attached archive only one register was generated for each table of database. it is this that I am asking in the forum. Because with Mysql 4.0.x this does not happen. This only happens in Mysql 4.1 i use a follow sintax: mysqldump --host localhost --user root [databasename] c:\file.sql Regards Carlos J Souza On Thu, 18 Aug 2005 14:10:56 -0400, [EMAIL PROTECTED] wrote: Carlos J Souza [EMAIL PROTECTED] wrote on 08/18/2005 03:16:15 PM: Sirs, When i use mysqldump on Version 4.1.x, all tables had a one record insert generated in script. When i use mysqldump on a 4.0.x version this problem does not occurs. How to solve it? Regards For all Carlos J Souza I think that generating the INSERT statement (the 4.1.x behavior) should not be a problem. Can you try again to describe what it is you would like to do, how you are trying to do it, and what is not happening in the manner you desire? I can tell that English is not your native language. I usually do not make this suggestion (as this is an English mailing list) but there are several on the list that do speak Portuguese (and Spanish) so perhaps you could try describing your problem that way, too. Shawn Green Database Administrator Unimin Corporation - Spruce Pine [attachment siexwin.sql deleted by Shawn Green/Unimin]
Re: mysqldump problem
On 24 May 2004, at 6:05 pm, Gilbert Wu wrote: Hi All, The dump file is a 4Gytes text file. Could find an editor able to look at the content of the file. Hence, I had to write a little Perl program (something I haven't done for 5 years). I discovered the line that caused a syntax error whenever I tried to restore from the dump file. It looks something like: INSERT INTO TABLE2 VALUES (5,579,265,16,20020312,-438,191.789,191.789,5.5767e-006,5.5767e -006,0,0,0,-12086.6),(5,579,265,16,20020313, -438,157.242,157.242,4.5723e-006,4.5723e-006,0,0,0, -11892.7),(5,579,265,16,20020314,-438,-177.829,-177.829,-5.1788e-006, -5.1788e-006,0,0,0,-11829.3),(5,579,265,16,20020315,-438,-131.495, -131.495,-3.8387e-006,-3.8387e-006,0,0,0, -12012.6),(5,579,265,16,20020318,1,-133.587,-173.91,-4.7218e-006, -6.147e-006,47.0828,1.6642e-006,12290.1,-12135.1),(5UNLOCK TABLES; It seems like mysqldump gave up during the file generation and inserted UNLOCK TABLES; in the middle of the insertion block. Hence, the syntax error during restoration. Is this a mysqldump bug? Regards, Gilbert -Original Message- From: Gilbert Wu Sent: 24 May 2004 17:10 To: Brian Reichert Cc: [EMAIL PROTECTED] Subject: RE: mysqldump problem Sorry, I am running MySQL 4.0.17-nt on Windows 2000 Server. Consider the OS and filesystem as well (wheatever uyou _are_ using; you didn't tell us). Quotas? Limits by FS? getrlimit()? Would this by any chance be dumping to a disk formatted with the FAT32 filesystem? FAT32 files are limited to 2^32-1 bytes - i.e. 1 less than 4GB. Tim -- Dr Tim Cutts Informatics Systems Group Wellcome Trust Sanger Institute Hinxton, Cambridge, CB10 1SA, UK -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysqldump problem
Hi, I've been using mysqldump to backup my entire database. Every day, I restore the whole thing to my test/develop database by piping the large sql generated by mysqldump. All is well until the file size of the sql file reached about 4Gbytes. I wonder if there is a size limit to the database I can backup and restore? Many Thanks. Regards, Gilbert Wu [EMAIL PROTECTED] http://www.sabrefund.com/ http://www.sabrefund.com/ Sabre Fund Management Limited Windsor House 55 St James's Street London SW1A 1LA Tel +44 20 7316 2820 Fax +44 20 7316 0180 Authorized and Regulated by the FSA NOTICE: This e-mail and any attachment is confidential and may also be privileged. It is intended for the named recipient only. If you have received it in error, please contact the sender immediately by telephoning +44(0)207 316 2800. Any dissemination, distribution, copying or use of this communication without the permission of the sender is prohibited. There are risks in communicating by e-mail. E-mail may be susceptible to data corruption, delay, interception and unauthorised amendment and we do not accept liability for any such corruption, delay, interception or amendment or their consequences. Anyone who communicates with us by e-mail is taken to accept the risks in so doing. Furthermore the contents of an attachment to this e-mail may contain software viruses which could damage your computer system or data. While we have taken reasonable precautions to prevent the inclusion of viruses in e-mails and attachments, neither we nor the sender can accept any liability for any loss or damage sustained as a result of software viruses. You are strongly advised to carry out your own virus checking before opening any attachments.
Re: mysqldump problem
On Mon, May 24, 2004 at 03:07:17PM +0100, Gilbert Wu wrote: Hi, I've been using mysqldump to backup my entire database. Every day, I restore the whole thing to my test/develop database by piping the large sql generated by mysqldump. All is well until the file size of the sql file reached about 4Gbytes. I wonder if there is a size limit to the database I can backup and restore? Consider the OS and filesystem as well (wheatever uyou _are_ using; you didn't tell us). Quotas? Limits by FS? getrlimit()? Many Thanks. Regards, Gilbert Wu [EMAIL PROTECTED] http://www.sabrefund.com/ http://www.sabrefund.com/ -- Brian Reichert [EMAIL PROTECTED] 37 Crystal Ave. #303Daytime number: (603) 434-6842 Derry NH 03038-1713 USA BSD admin/developer at large -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: mysqldump problem
Sorry, I am running MySQL 4.0.17-nt on Windows 2000 Server. -Original Message- From: Brian Reichert [mailto:[EMAIL PROTECTED] Sent: 24 May 2004 15:42 To: Gilbert Wu Cc: [EMAIL PROTECTED] Subject: Re: mysqldump problem On Mon, May 24, 2004 at 03:07:17PM +0100, Gilbert Wu wrote: Hi, I've been using mysqldump to backup my entire database. Every day, I restore the whole thing to my test/develop database by piping the large sql generated by mysqldump. All is well until the file size of the sql file reached about 4Gbytes. I wonder if there is a size limit to the database I can backup and restore? Consider the OS and filesystem as well (wheatever uyou _are_ using; you didn't tell us). Quotas? Limits by FS? getrlimit()? Many Thanks. Regards, Gilbert Wu [EMAIL PROTECTED] http://www.sabrefund.com/ http://www.sabrefund.com/ -- Brian Reichert [EMAIL PROTECTED] 37 Crystal Ave. #303Daytime number: (603) 434-6842 Derry NH 03038-1713 USA BSD admin/developer at large -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: mysqldump problem
Hi All, The dump file is a 4Gytes text file. Could find an editor able to look at the content of the file. Hence, I had to write a little Perl program (something I haven't done for 5 years). I discovered the line that caused a syntax error whenever I tried to restore from the dump file. It looks something like: INSERT INTO TABLE2 VALUES (5,579,265,16,20020312,-438,191.789,191.789,5.5767e-006,5.5767e-006,0,0,0,-12086.6),(5,579,265,16,20020313,-438,157.242,157.242,4.5723e-006,4.5723e-006,0,0,0,-11892.7),(5,579,265,16,20020314,-438,-177.829,-177.829,-5.1788e-006,-5.1788e-006,0,0,0,-11829.3),(5,579,265,16,20020315,-438,-131.495,-131.495,-3.8387e-006,-3.8387e-006,0,0,0,-12012.6),(5,579,265,16,20020318,1,-133.587,-173.91,-4.7218e-006,-6.147e-006,47.0828,1.6642e-006,12290.1,-12135.1),(5UNLOCK TABLES; It seems like mysqldump gave up during the file generation and inserted UNLOCK TABLES; in the middle of the insertion block. Hence, the syntax error during restoration. Is this a mysqldump bug? Regards, Gilbert -Original Message- From: Gilbert Wu Sent: 24 May 2004 17:10 To: Brian Reichert Cc: [EMAIL PROTECTED] Subject: RE: mysqldump problem Sorry, I am running MySQL 4.0.17-nt on Windows 2000 Server. -Original Message- From: Brian Reichert [mailto:[EMAIL PROTECTED] Sent: 24 May 2004 15:42 To: Gilbert Wu Cc: [EMAIL PROTECTED] Subject: Re: mysqldump problem On Mon, May 24, 2004 at 03:07:17PM +0100, Gilbert Wu wrote: Hi, I've been using mysqldump to backup my entire database. Every day, I restore the whole thing to my test/develop database by piping the large sql generated by mysqldump. All is well until the file size of the sql file reached about 4Gbytes. I wonder if there is a size limit to the database I can backup and restore? Consider the OS and filesystem as well (wheatever uyou _are_ using; you didn't tell us). Quotas? Limits by FS? getrlimit()? Many Thanks. Regards, Gilbert Wu [EMAIL PROTECTED] http://www.sabrefund.com/ http://www.sabrefund.com/ -- Brian Reichert [EMAIL PROTECTED] 37 Crystal Ave. #303Daytime number: (603) 434-6842 Derry NH 03038-1713 USA BSD admin/developer at large -- 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]
mysqldump problem
I have a database setup for replication. I used mysqldump --opt db db.dmp to do the initial backup of the primary database (after doing a flush tables with read lock in a seperate session). I checked the dump file, and all drop table create table statements are in the file. When I did a restore to the second database with a mysql --on-database db db.dmp, it appears that the tables were not dropped and recreated. No errors were displayed during this process. After the restore, I was able to start replication, and replication ran fine, until it encountered an object which was not in the secondary database which was in the primary. The schema looks to be the old schema (pre database restore), and table drops/creates appear to have been done from the dump file. Any ideas why/how this would be? My dump file is about 14 Gig. IMPORTANT NOTICES: Confidential Information.The information contained in or attached to this e-mail may be confidential information subject to protection by law or terms of applicable confidentiality agreements, and is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you should destroy this message and notify the sender by reply email. smime.p7s Description: S/MIME cryptographic signature
Re: mysqldump problem
Joe Adams wrote: I have a database setup for replication. I used mysqldump --opt db db.dmp to do the initial backup of the primary database (after doing a flush tables with read lock in a seperate session). I checked the dump file, and all drop table create table statements are in the file. When I did a restore to the second database with a mysql --on-database db db.dmp, it appears that the tables were not dropped and recreated. No errors were displayed during this process. After the restore, I was able to start replication, and replication ran fine, until it encountered an object which was not in the secondary database which was in the primary. The schema looks to be the old schema (pre database restore), and table drops/creates appear to have been done from the dump file. Any ideas why/how this would be? My dump file is about 14 Gig. Joe: Did you make sure to do RESET MASTER/RESET SLAVE trick, or otherwise adjust the replication log coordinates for the slave to start at the right place? --one-database should not be necessary, and having it could possibly be triggering some weird bug or a poorly documented feature. mysql db dump.sql should be sufficiet to restore. P.S. If you are using MyISAM, binary snapshot would work better for this much data. For InnoDB, hotbackup utility is a good investment. -- Sasha Pachev Create online surveys at http://www.surveyz.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Mysqldump problem in output UTF-8 Char
I have a table create table friend( f_code int(7) not null AUTO_INCREMENT, c_name varchar(20), //Use to store Chinese Name e_name varchar(50) //use to store English Name ); in which table i set to use Charset (UTF-8). But When i use mysqlmysqldump -u myname -p mypwd telbookbook.txt, all string of table friend's c_name will become ?. any one face this promble before? any one can get me some suggest,please? ... http://ringtone.yahoo.com.hk/
re: Mysqldump problem in output UTF-8 Char
in which table i set to use Charset (UTF-8). But When i use mysqlmysqldump -u myname -p mypwd telbookbook.txt, all string of table friend's c_name will become ?. Have you tried: mysqldump --default-character-set=utf8 -u myname -p mypwd telbookbook.txt If that doesn't work, which version of MySQL are you using? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Mysqldump Problem
Hello Members I am using mysql 3.23.37 on NT. I am getting problem when i am using mysqldump on NT, dumpfile contains all table name in lowercase(i was having all tables name in uppercase). Now i added [mysqldump] set-variable = lower_case_table_names= 0 in my.cnf file.(I searched the mail archive and got this solution) But now i am getting error No variable match for: -O 'lower_case_table_names= 0' Then i checked allowed variable for mysqldump i found only two 1.max_allowed_packet 2.net_buffer_length Can anyone help me how to get rid of this case change problem. Thanks in advance. Damnish - 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: Mysqldump Problem
Damnish, Wednesday, May 01, 2002, 3:07:52 PM, you wrote: D I am using mysql 3.23.37 on NT. D I am getting problem when i am using mysqldump on NT, dumpfile contains all D table name in lowercase(i was having all tables name in uppercase). D Now i added D [mysqldump] D set-variable = lower_case_table_names= 0 D in my.cnf file.(I searched the mail archive and got this solution) D But now i am getting error D No variable match for: -O 'lower_case_table_names= 0' D Then i checked allowed variable for mysqldump i found only two D 1.max_allowed_packet D 2.net_buffer_length D Can anyone help me D how to get rid of this case change problem. lower_case_table_names is a variable for mysqld, not for mysqldump! So, you should set variable in [mysqld] section of my.cnf. If you have lower_case_table_names=1 how can you get table names in uppercase? D Thanks in advance. D Damnish -- For technical support contracts, goto https://order.mysql.com/ 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
RE: mysqldump problem
kaps, Sunday, March 31, 2002, 9:54:00 AM, you wrote: k i m fairly new to mySQL. I have to work on already set up live database k which can be managedwith phpAdmin system. k Now i was wondering how can i take a backup (dump) of the database with that k system? Use mysqldump utility: http://www.mysql.com/doc/m/y/mysqldump.html k kaps -- 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
mysqldump problem
Hello, When I try to get the remote dump of a database, I get the table structure without any failure but it is not able to get the table data. Has anyone of you came over to this problem before? Here is what I have tried: H:\c:\mysql\bin\mysqldump -T c:\mysql\batch\dump\new_dump -f -l -v -u username -ppassword -h 192.168.51.120 databasename -- Connecting to 192.168.51.120... -- Retrieving table structure for table employee... -- Sending SELECT query... c:\mysql\bin\mysqldump: Got error: 1: Can't create/write to file 'c:\mysql\batch\dump\new_dump\employee.txt' (Errcode: 2) when executing 'SELECT INTO OUTFILE' .. .. Regards Okan - 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: mysqldump problem
At 16:21 +0200 3/30/02, Okan CIMEN wrote: Hello, When I try to get the remote dump of a database, I get the table structure without any failure but it is not able to get the table data. Has anyone of you came over to this problem before? Here is what I have tried: -T requires that you have the FILE privilege, and you probably don't -T isn't that useful for a remote server, anyway. The *.txt files are written on the server host, not the client host. H:\c:\mysql\bin\mysqldump -T c:\mysql\batch\dump\new_dump -f -l -v -u username -ppassword -h 192.168.51.120 databasename -- Connecting to 192.168.51.120... -- Retrieving table structure for table employee... -- Sending SELECT query... c:\mysql\bin\mysqldump: Got error: 1: Can't create/write to file 'c:\mysql\batch\dump\new_dump\employee.txt' (Errcode: 2) when executing 'SELECT INTO OUTFILE' .. .. Regards Okan - 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: mysqldump problem
Dear Paul, I have full privileges on the database. mysql show grants for username- ; +--- --+ | Grants for username@% | +--- --+ | GRANT ALL PRIVILEGES ON *.* TO 'username'@'%' IDENTIFIED BY PASSWORD '5d60c9f55c18d05c' WITH GRANT OPTION | | GRANT ALL PRIVILEGES ON databasename.* TO 'username'@'%' WITH GRANT OPTION | +--- --+ And when I run the mysqldump, it creates the table structure files on my box, not at the server. Thanks for your answer Okan 2 rows in set (0.00 sec) - Original Message - From: Paul DuBois [EMAIL PROTECTED] To: Okan CIMEN [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, March 30, 2002 4:42 PM Subject: Re: mysqldump problem At 16:21 +0200 3/30/02, Okan CIMEN wrote: Hello, When I try to get the remote dump of a database, I get the table structure without any failure but it is not able to get the table data. Has anyone of you came over to this problem before? Here is what I have tried: -T requires that you have the FILE privilege, and you probably don't -T isn't that useful for a remote server, anyway. The *.txt files are written on the server host, not the client host. H:\c:\mysql\bin\mysqldump -T c:\mysql\batch\dump\new_dump -f -l -v -u username -ppassword -h 192.168.51.120 databasename -- Connecting to 192.168.51.120... -- Retrieving table structure for table employee... -- Sending SELECT query... c:\mysql\bin\mysqldump: Got error: 1: Can't create/write to file 'c:\mysql\batch\dump\new_dump\employee.txt' (Errcode: 2) when executing 'SELECT INTO OUTFILE' .. .. Regards Okan - 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: mysqldump problem
At 17:24 +0200 3/30/02, Okan CIMEN wrote: Dear Paul, I have full privileges on the database. FILE is a global privilege, not a database-specific privilege. mysql show grants for username- ; +--- --+ | Grants for username@% | +--- --+ | GRANT ALL PRIVILEGES ON *.* TO 'username'@'%' IDENTIFIED BY PASSWORD '5d60c9f55c18d05c' WITH GRANT OPTION | | GRANT ALL PRIVILEGES ON databasename.* TO 'username'@'%' WITH GRANT OPTION | +--- --+ And when I run the mysqldump, it creates the table structure files on my box, not at the server. Right. Those are the *.sql file. The data files (*.txt files) are created on the server -- which is why you need the FILE privilege. Yes, this is confusing, but that's how mysqldump behaves. Thanks for your answer Okan 2 rows in set (0.00 sec) - Original Message - From: Paul DuBois [EMAIL PROTECTED] To: Okan CIMEN [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, March 30, 2002 4:42 PM Subject: Re: mysqldump problem At 16:21 +0200 3/30/02, Okan CIMEN wrote: Hello, When I try to get the remote dump of a database, I get the table structure without any failure but it is not able to get the table data. Has anyone of you came over to this problem before? Here is what I have tried: -T requires that you have the FILE privilege, and you probably don't -T isn't that useful for a remote server, anyway. The *.txt files are written on the server host, not the client host. H:\c:\mysql\bin\mysqldump -T c:\mysql\batch\dump\new_dump -f -l -v -u username -ppassword -h 192.168.51.120 databasename -- Connecting to 192.168.51.120... -- Retrieving table structure for table employee... -- Sending SELECT query... c:\mysql\bin\mysqldump: Got error: 1: Can't create/write to file 'c:\mysql\batch\dump\new_dump\employee.txt' (Errcode: 2) when executing 'SELECT INTO OUTFILE' .. .. Regards Okan - 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: mysqldump problem
hi guys!! i m fairly new to mySQL. I have to work on already set up live database which can be managedwith phpAdmin system. Now i was wondering how can i take a backup (dump) of the database with that system? I have figured out how can i do it if i have to work on mySQL Server instead. Any help? Regards kaps - 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: mysqldump: problem/question
Weaver, Walt writes: I knew it. Nobody bothered to read my post. The original problem involved running a lightweight version of mysqldump in a simulated nanokernel environment with reduced power resources. The ultimate result, we hope, is to use it to record Quidditch matches being played in Afghanistan. Thanks, --Walt Weaver Bozeman, Montana, USA I hope you have found --quick option. Sorry, but what is Quidditch ?? -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ 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: mysqldump: problem/question
So what was the problem? Weaver, Walt wrote: WW: Okay, I know you guys have been wracking your brains for the last two days WW: trying to solve my problem of mysqldump running out of memory while dumping WW: a large table. WW: WW: I figured it out, so you can all go on with your lives. WW: WW: My copy of Paul DuBois' MySQL book came today and immediately solved my WW: problem. WW: WW: Cool book. Now I have something to do this weekend. WW: WW: Thanks, WW: --Walt Weaver WW: Bozeman, Montana WW: Oracle smart, MySQL dumb (for now) WW: WW: - WW: Before posting, please check: WW:http://www.mysql.com/manual.php (the manual) WW:http://lists.mysql.com/ (the list archive) WW: WW: To request this thread, e-mail [EMAIL PROTECTED] WW: To unsubscribe, e-mail [EMAIL PROTECTED] WW: Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php WW: -- sherzodR [EMAIL PROTECTED] use CGI::Session; - 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: mysqldump: problem/question
I knew it. Nobody bothered to read my post. The original problem involved running a lightweight version of mysqldump in a simulated nanokernel environment with reduced power resources. The ultimate result, we hope, is to use it to record Quidditch matches being played in Afghanistan. Thanks, --Walt Weaver Bozeman, Montana, USA -Original Message- From: sherzodR To: Weaver, Walt Cc: [EMAIL PROTECTED] Sent: 11/30/2001 3:14 AM Subject: re: mysqldump: problem/question So what was the problem? Weaver, Walt wrote: WW: Okay, I know you guys have been wracking your brains for the last two days WW: trying to solve my problem of mysqldump running out of memory while dumping WW: a large table. WW: WW: I figured it out, so you can all go on with your lives. WW: WW: My copy of Paul DuBois' MySQL book came today and immediately solved my WW: problem. WW: WW: Cool book. Now I have something to do this weekend. WW: WW: Thanks, WW: --Walt Weaver WW: Bozeman, Montana WW: Oracle smart, MySQL dumb (for now) WW: WW: - WW: Before posting, please check: WW:http://www.mysql.com/manual.php (the manual) WW:http://lists.mysql.com/ (the list archive) WW: WW: To request this thread, e-mail [EMAIL PROTECTED] WW: To unsubscribe, e-mail [EMAIL PROTECTED] WW: Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php WW: -- sherzodR [EMAIL PROTECTED] use CGI::Session; - 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: mysqldump: problem/question
Okay, I know you guys have been wracking your brains for the last two days trying to solve my problem of mysqldump running out of memory while dumping a large table. I figured it out, so you can all go on with your lives. My copy of Paul DuBois' MySQL book came today and immediately solved my problem. Cool book. Now I have something to do this weekend. Thanks, --Walt Weaver Bozeman, Montana Oracle smart, MySQL dumb (for now) - 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
mysqldump problem/question
Another newbie question: I'm trying to do a mysqldump of a fairly large, wide (two longblobs) table, and am running into memory problems. After running for some time the mysqldump process will die with an Out of memory (needed 8164 bytes) message. Is there a way to tell mysqldump to not cache everything in memory until it's finished? I've been reading the online documentation, tried the -q parm, but it didn't work. I haven't yet been able to find anything in the documentation that would indicate there's a way around this. If anyone has any ideas, I'm all ears! Thanks, --Walt Weaver Bozeman, Montana, USA - 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
mysqldump problem
Dump database: mysqldump -uroot -px -A -a -F -l --opt --quote-names -rc:/mysql/data/dump.sql Restore mysql -uroot -px c:/mysql/data/dump.sql I forgot to use --quote-names. -Q doesn't seem to work /Benny - 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
mysqldump problem
Hi The following example gives me a problem. I create a new database by sending the following SQL commands: create database dummy create table `Dummy Table` (`Dummy Time` timestamp(14) NOT NULL) When i run mysqldump with the parameters shown below mysqldump -uroot -pxx -A -a -F -l --opt -rc:/mysql/data/dump.sql I will get a dump file which look like the following section: / # MySQL dump 8.16 # # Host: localhostDatabase: # # Server version3.23.42-log # # Current Database: dummy # CREATE DATABASE /*!32312 IF NOT EXISTS*/ dummy; USE dummy; # # Table structure for table 'dummy table' # DROP TABLE IF EXISTS `dummy table`; CREATE TABLE dummy table ( Dummy Time timestamp(14) NOT NULL ) TYPE=MyISAM; # # Dumping data for table 'dummy table' # LOCK TABLES `dummy table` WRITE; UNLOCK TABLES; / As you can see drop table uses the ` character around dummy table, but don't use it in the create CREATE TABLE statement. The `character is also missing around the colum name Dummy Time. These two things make it difficult for me to restore the database from the dump file so I hope you can give me some advise. Best regards, RTX Telecom A/S Benny B. Simonsen BB/Project Engineer System Development RTX Telecom A/S Stroemmen 6 DK-9400 Noerresundby. Phone.: +45 96 32 23 00 Fax.: +45 96 32 23 10 E-mail: [EMAIL PROTECTED] Web: www.rtx.dk PS: I am using the win32 version 3.23.42 (mysqld-opt.exe installed as a service on a Win2K platform). I have the following two lines in my.cnf which is at c:\ [mysqld] log-bin - 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
mysqldump problem with Openserver 5.0.5
Description: When I try and run mysqldump, I get a core dump. How-To-Repeat: it repeats anytime I try and run mysqldump. Fix: I have not found a fix yet. Submitter-Id: submitter ID Originator:Phillip Porch Organization: Phillip P. Porch [EMAIL PROTECTED] NIC:PP1573 finger for http://www.theporch.com UTM - 16 514546E 3994565N GnuPG key MySQL support: none Synopsis: Core dump with mysqldump with Openserver 5.0.5 Severity: serious Priority: low Category: mysql Class: sw-bug Release: mysql-3.23.38 (Source distribution) Server: /usr/local/bin/mysqladmin Ver 8.20 Distrib 3.23.38, for pc-sco3.2v5.0.5 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 3.23.38-log Protocol version10 Connection Localhost via UNIX socket UNIX socket /tmp/mysql.sock Uptime: 11 min 14 sec Threads: 1 Questions: 104 Slow queries: 0 Opens: 53 Flush tables: 1 Open tables: 0 Queries per second avg: 0.154 Environment: System: SCO_SV sco 3.2 5.0.5 i386 Some paths: /usr/local/bin/perl /usr/local/bin/make /usr/local/bin/gmake /usr/local/bin/gcc /bin/cc GCC: Reading specs from /usr/local/lib/gcc-lib/i386-pc-sco3.2v5.0.5/2.95.2/specs gcc version 2.95.2 19991024 (release) Compilation info: CC='gcc' CFLAGS=' ' CXX='c++' CXXFLAGS='' LDFLAGS='' LIBC: lrwxrwxrwx 1 root root 35 Nov 19 1999 /lib/libc.a - /opt/K/SCO/unixds/5.1.1A/lib/libc.a lrwxrwxrwx 1 root root 36 Nov 19 1999 /lib/libc.so - /opt/K/SCO/unixds/5.1.1A/lib/libc.so lrwxrwxrwx 1 root root 39 Nov 19 1999 /usr/lib/libc.a - /opt/K/SCO/unixds/5.1.1A/usr/lib/libc.a lrwxrwxrwx 1 root root 40 Nov 19 1999 /usr/lib/libc.so - /opt/K/SCO/unixds/5.1.1A/usr/lib/libc.so lrwxrwxrwx 1 root root 41 Nov 19 1999 /usr/lib/libc.so.1 - /opt/K/SCO/Unix/5.0.5Eb/usr/lib/libc.so.1 Configure command: ./configure - 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
mysqldump problem in 3.23.38 with Openserver 5.0.5
I have compiled 3.23.38 without problems. I ran the test suite and mysqld passed all 117 tests (I think it was 117). mysql client works fine but I tried to use mysqldump and received a core dump (segmentation violation). I also receive this if I try and run mysqlshow. As far as I can tell, everything else is fine. Suggestions? - 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: mysqldump problem with Openserver 5.0.5
You need to use the following when you build mysql to use all options. CC=gcc CXX=gcc ./configure --prefix=/usr/local/mysql --enable-thread-safe-client --with-berkeley-db=./bdb --with-innodb Not that CXX is gcc and not the c++ compiler from SCO. Good Luck, -- Boyd Gerber [EMAIL PROTECTED] ZENEZ 3748 Valley Forge Road, Magna Utah 84044 Office 801-250-0795 FAX 801-250-7975 - 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
mysqldump problem?
Short version: mysqldump seems to produce a "KEY mid(mid)" statement, which mysql does not understand. Using KEY (mid) instead of KEY mid(mid) works, though. Is this a known problem? Is this an oversight by me? Long version: kk@lenz ~ $ cat /etc/SuSE-release SuSE Linux 7.1 (i386) VERSION = 7.1 including all updates from ftp.suse.com, running mysql select version() as version; +-+ | version | +-+ | 3.23.32-log | +-+ 1 row in set (0.01 sec) kk@lenz ~ $ mysqldump test_passwd dokumentation # MySQL dump 8.12 # # Host: localhostDatabase: test_passwd # # Server version3.23.32-log # # Table structure for table 'dokumentation' # CREATE TABLE dokumentation ( did int(11) NOT NULL default '0', mid int(11) NOT NULL default '0', beschreibung text, filename varchar(255) NOT NULL default '', mimetype varchar(255) NOT NULL default '', changed timestamp(14) NOT NULL, PRIMARY KEY (did), KEY mid(mid) ) TYPE=MyISAM; # # Dumping data for table 'dokumentation' # kk@lenz ~ $ mysql test_passwd Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 35 to server version: 3.23.32-log Type 'help;' or '\h' for help. Type '\c' to clear the buffer mysql drop table dokumentation; Query OK, 0 rows affected (0.00 sec) mysql CREATE TABLE dokumentation ( - did int(11) NOT NULL default '0', - mid int(11) NOT NULL default '0', - beschreibung text, - filename varchar(255) NOT NULL default '', - mimetype varchar(255) NOT NULL default '', - changed timestamp(14) NOT NULL, - PRIMARY KEY (did), - KEY mid(mid) - ) TYPE=MyISAM; ERROR 1064: You have an error in your SQL syntax near 'mid(mid) ) TYPE=MyISAM' at line 9 but mysql CREATE TABLE dokumentation ( - did int(11) NOT NULL default '0', - mid int(11) NOT NULL default '0', - beschreibung text, - filename varchar(255) NOT NULL default '', - mimetype varchar(255) NOT NULL default '', - changed timestamp(14) NOT NULL, - PRIMARY KEY (did), - KEY (mid) - ) TYPE=MyISAM; Query OK, 0 rows affected (0.01 sec) Kristian -- Kristian Khntopp, NetUSE AG Siemenswall, D-24107 Kiel Tel: +49 431 386 436 00, Fax: +49 431 386 435 99 - 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: mysqldump problem?
Kristian Khntopp wrote: Short version: mysqldump seems to produce a "KEY mid(mid)" statement, which mysql does not understand. Using KEY (mid) instead of KEY mid(mid) works, though. Is this a known problem? Is this an oversight by me? Ultrashort resolution: kris is stupid and mid is a reserved word in MySQL. Thanks, Kristian -- Kristian Khntopp, NetUSE AG Siemenswall, D-24107 Kiel Tel: +49 431 386 436 00, Fax: +49 431 386 435 99 - 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: mysqldump problem?
This seems to be a competability feater, so you can load it into db2, oracle etc. "Kristian Khntopp" [EMAIL PROTECTED]@mail.netuse.de on 03/16/2001 01:06:30 PM Sent by: [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: mysqldump problem? Short version: mysqldump seems to produce a "KEY mid(mid)" statement, which mysql does not understand. Using KEY (mid) instead of KEY mid(mid) works, though. Is this a known problem? Is this an oversight by me? Long version: kk@lenz ~ $ cat /etc/SuSE-release SuSE Linux 7.1 (i386) VERSION = 7.1 including all updates from ftp.suse.com, running mysql select version() as version; +-+ | version | +-+ | 3.23.32-log | +-+ 1 row in set (0.01 sec) kk@lenz ~ $ mysqldump test_passwd dokumentation # MySQL dump 8.12 # # Host: localhostDatabase: test_passwd # # Server version3.23.32-log # # Table structure for table 'dokumentation' # CREATE TABLE dokumentation ( did int(11) NOT NULL default '0', mid int(11) NOT NULL default '0', beschreibung text, filename varchar(255) NOT NULL default '', mimetype varchar(255) NOT NULL default '', changed timestamp(14) NOT NULL, PRIMARY KEY (did), KEY mid(mid) ) TYPE=MyISAM; # # Dumping data for table 'dokumentation' # kk@lenz ~ $ mysql test_passwd Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 35 to server version: 3.23.32-log Type 'help;' or '\h' for help. Type '\c' to clear the buffer mysql drop table dokumentation; Query OK, 0 rows affected (0.00 sec) mysql CREATE TABLE dokumentation ( - did int(11) NOT NULL default '0', - mid int(11) NOT NULL default '0', - beschreibung text, - filename varchar(255) NOT NULL default '', - mimetype varchar(255) NOT NULL default '', - changed timestamp(14) NOT NULL, - PRIMARY KEY (did), - KEY mid(mid) - ) TYPE=MyISAM; ERROR 1064: You have an error in your SQL syntax near 'mid(mid) ) TYPE=MyISAM' at line 9 but mysql CREATE TABLE dokumentation ( - did int(11) NOT NULL default '0', - mid int(11) NOT NULL default '0', - beschreibung text, - filename varchar(255) NOT NULL default '', - mimetype varchar(255) NOT NULL default '', - changed timestamp(14) NOT NULL, - PRIMARY KEY (did), - KEY (mid) - ) TYPE=MyISAM; Query OK, 0 rows affected (0.01 sec) Kristian -- Kristian Khntopp, NetUSE AG Siemenswall, D-24107 Kiel Tel: +49 431 386 436 00, Fax: +49 431 386 435 99 - 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: mysqldump problem?
It is a known problem, I saw a bug report go through about it a day or so ago. One workaround I found is to rename the key. I think the problem may have something to do with the name of the key also being column name or a special token. In my case, I had: int User, key User(User) and I changed it to int USer, key UserKey(User) ...and it fixed the problem. So, you might try key midkey(mid) -bill At 01:06 PM 3/16/2001 +0100, Kristian Khntopp wrote: Short version: mysqldump seems to produce a "KEY mid(mid)" statement, which mysql does not understand. Using KEY (mid) instead of KEY mid(mid) works, though. Is this a known problem? Is this an oversight by me? Long version: kk@lenz ~ $ cat /etc/SuSE-release SuSE Linux 7.1 (i386) VERSION = 7.1 including all updates from ftp.suse.com, running mysql select version() as version; +-+ | version | +-+ | 3.23.32-log | +-+ 1 row in set (0.01 sec) kk@lenz ~ $ mysqldump test_passwd dokumentation # MySQL dump 8.12 # # Host: localhostDatabase: test_passwd # # Server version3.23.32-log # # Table structure for table 'dokumentation' # CREATE TABLE dokumentation ( did int(11) NOT NULL default '0', mid int(11) NOT NULL default '0', beschreibung text, filename varchar(255) NOT NULL default '', mimetype varchar(255) NOT NULL default '', changed timestamp(14) NOT NULL, PRIMARY KEY (did), KEY mid(mid) ) TYPE=MyISAM; # # Dumping data for table 'dokumentation' # kk@lenz ~ $ mysql test_passwd Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 35 to server version: 3.23.32-log Type 'help;' or '\h' for help. Type '\c' to clear the buffer mysql drop table dokumentation; Query OK, 0 rows affected (0.00 sec) mysql CREATE TABLE dokumentation ( - did int(11) NOT NULL default '0', - mid int(11) NOT NULL default '0', - beschreibung text, - filename varchar(255) NOT NULL default '', - mimetype varchar(255) NOT NULL default '', - changed timestamp(14) NOT NULL, - PRIMARY KEY (did), - KEY mid(mid) - ) TYPE=MyISAM; ERROR 1064: You have an error in your SQL syntax near 'mid(mid) ) TYPE=MyISAM' at line 9 but mysql CREATE TABLE dokumentation ( - did int(11) NOT NULL default '0', - mid int(11) NOT NULL default '0', - beschreibung text, - filename varchar(255) NOT NULL default '', - mimetype varchar(255) NOT NULL default '', - changed timestamp(14) NOT NULL, - PRIMARY KEY (did), - KEY (mid) - ) TYPE=MyISAM; Query OK, 0 rows affected (0.01 sec) Kristian -- Kristian Khntopp, NetUSE AG Siemenswall, D-24107 Kiel Tel: +49 431 386 436 00, Fax: +49 431 386 435 99 - 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: mysqldump problem?
[EMAIL PROTECTED] wrote: This seems to be a competability feater, so you can load it into db2, oracle etc. But not into MySQL - great idea. :-) Kristian -- Kristian Khntopp, NetUSE AG Siemenswall, D-24107 Kiel Tel: +49 431 386 436 00, Fax: +49 431 386 435 99 - 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: mysqldump problem?
"Kristian Khntopp" [EMAIL PROTECTED]@mail.netuse.de on 03/16/2001 02:02:28 PM ?Sent by: [EMAIL PROTECTED] ?To: [EMAIL PROTECTED] ?cc: [EMAIL PROTECTED] ?Subject: Re: mysqldump problem? ? ? ?[EMAIL PROTECTED] wrote: ? This seems to be a competability feater, so you can load it into db2, ? oracle etc. ? ?"Kristian Khntopp" [EMAIL PROTECTED] ?But not into MySQL - great idea. :-) ? ?Kristian ? ?-- ?Kristian Khntopp, NetUSE AG Siemenswall, D-24107 Kiel ?Tel: +49 431 386 436 00, Fax: +49 431 386 435 99 It's not an idea it is reality if IBM or ORACLE find a bug (wanze) (: -( cj - 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: newbie mysqldump problem, SOLVED!
Doug Poland wrote: Hi, I'm having a dickens of a time getting mysqldump to work. No matter what I enter, mysqldump says... /usr/local/mysql/bin/mysqldump: option `--databases' doesn't allow an argument The problem was the ~/.my.cnf file. I took out the database=... line and mysqldump worked fine. Thanks for the help! -- Regards, Doug - 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
newbie mysqldump problem
Hi, I'm having a dickens of a time getting mysqldump to work. No matter what I enter, mysqldump says... /usr/local/mysql/bin/mysqldump: option `--databases' doesn't allow an argument I've perused the list archives and looked at the manual. It should work but doesn't. What am I doing wrong? mysql ver 11.12 distrib 3.23.32 mysqldump ver 8.12 distrib 3.23.32 -- Regards, Doug - 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: newbie mysqldump problem
mysqldump --databases db1 db2 db3 ... Note, these are complete databases, NOT tables. to try it do: mysqldump --databases mysql Doug Poland wrote: Hi, I'm having a dickens of a time getting mysqldump to work. No matter what I enter, mysqldump says... /usr/local/mysql/bin/mysqldump: option `--databases' doesn't allow an argument I've perused the list archives and looked at the manual. It should work but doesn't. What am I doing wrong? mysql ver 11.12 distrib 3.23.32 mysqldump ver 8.12 distrib 3.23.32 -- Regards, Doug - 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: newbie mysqldump problem
Well, I am running 3.23.33, and it works for me. Doug Poland wrote: On Thu, Mar 08, 2001 at 03:03:43PM -0600, Gerald L. Clark wrote: mysqldump --databases db1 db2 db3 ... Note, these are complete databases, NOT tables. to try it do: mysqldump --databases mysql I've tried that. But I tried it again anyway. This is a screen copy... admin:~$ /usr/local/mysql/bin/mysqldump --databases mysql /usr/local/mysql/bin/mysqldump: option `--databases' doesn't allow an argument /usr/local/mysql/bin/mysqldump Ver 8.12 Distrib 3.23.32, for pc-linux-gnu (i686) By Igor Romanenko, Monty, Jani Sinisa This software comes with ABSOLUTELY NO WARRANTY. This is free software, ... ... blah, blah, blah... ... Doug Poland wrote: Hi, I'm having a dickens of a time getting mysqldump to work. No matter what I enter, mysqldump says... /usr/local/mysql/bin/mysqldump: option `--databases' doesn't allow an argument I've perused the list archives and looked at the manual. It should work but doesn't. What am I doing wrong? mysql ver 11.12 distrib 3.23.32 mysqldump ver 8.12 distrib 3.23.32 -- Regards, Doug - 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 -- Regards, Doug - 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: newbie mysqldump problem
On Thu, Mar 08, 2001 at 03:33:54PM -0600, Gerald L. Clark wrote: Well, I am running 3.23.33, and it works for me. I'm working via ssh on an ISP's host. I wonder if there are permissions that have to be set in order to run mysqldump. Out of curiosity, I tried it on another ISP running MySQL and I have the same result :( However, on my local box, it works just fine. Anyone know what's going on? -- Regards, Doug Doug Poland wrote: On Thu, Mar 08, 2001 at 03:03:43PM -0600, Gerald L. Clark wrote: mysqldump --databases db1 db2 db3 ... Note, these are complete databases, NOT tables. to try it do: mysqldump --databases mysql I've tried that. But I tried it again anyway. This is a screen copy... admin:~$ /usr/local/mysql/bin/mysqldump --databases mysql /usr/local/mysql/bin/mysqldump: option `--databases' doesn't allow an argument /usr/local/mysql/bin/mysqldump Ver 8.12 Distrib 3.23.32, for pc-linux-gnu (i686) By Igor Romanenko, Monty, Jani Sinisa This software comes with ABSOLUTELY NO WARRANTY. This is free software, ... ... blah, blah, blah... ... Doug Poland wrote: Hi, I'm having a dickens of a time getting mysqldump to work. No matter what I enter, mysqldump says... /usr/local/mysql/bin/mysqldump: option `--databases' doesn't allow an argument I've perused the list archives and looked at the manual. It should work but doesn't. What am I doing wrong? mysql ver 11.12 distrib 3.23.32 mysqldump ver 8.12 distrib 3.23.32 -- Regards, Doug - 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
