List:MySQL on Win32« Previous MessageNext Message »
From:Jorge Bastos Date:September 13 2006 5:20pm
Subject:Fw: MySQLDump
View as plain text  
what's the error number?
with that we can see what's the problem, if that number os listed



----- Original Message ----- 
From: "Melissa Dougherty" <melissa@stripped>
To: "Mikhail Berman" <mberman@stripped>; "Michael Louie Loria" 
<mlloria@stripped>; <win32@stripped>
Sent: Wednesday, September 13, 2006 6:21 PM
Subject: Re: MySQLDump


> My script is setup that way....  Here is what's in my script.
>
> mysqldump --opt --all-databases --flush-logs --verbose -u 
> root -psapwd --result-file=c:\dump.sql
>
> All tables dump successfully except the table with the longtext column.
>
> Melissa
>
>
> ----- Original Message ----- 
> From: "Mikhail Berman" <mberman@stripped>
> To: "Melissa Dougherty" <melissa@stripped>; "Michael Louie Loria" 
> <mlloria@stripped>; <win32@stripped>
> Sent: Wednesday, September 13, 2006 11:05 AM
> Subject: RE: MySQLDump
>
>
> Well,
>
> I would think that would be the problem.
>
> The proper command would be
>
> $mysqldump -u user -pyourpwd test > test.sql, where
>
> "-u user" is you user name
> "-pyoupwd" is you password. This is not a mistake MySQL requires when
> one use "-p" not "--password" to have password entered in the format
> presented, meaning no spaces between "-p" and actual password.
> "test" - would be a database name
>
>
> Mikhail Berman
>
> -----Original Message-----
> From: Melissa Dougherty [mailto:melissa@stripped]
> Sent: Wednesday, September 13, 2006 10:55 AM
> To: Mikhail Berman; Michael Louie Loria; win32@stripped
> Subject: Re: MySQLDump
>
> The -p switch is for the password.
>
>
> ----- Original Message -----
> From: "Mikhail Berman" <mberman@stripped>
> To: "Michael Louie Loria" <mlloria@stripped>;
> <win32@stripped>
> Sent: Wednesday, September 13, 2006 9:42 AM
> Subject: RE: MySQLDump
>
>
> Hi Melissa,
>
> Could you tell me, what is the meaning of the "- p" switch at the end of
> your command?
>
> I am dumping tables larger than 320MB. I have a range of tables up to
> 613MB and I am able to dump them, only difference I can see is that we
> are in Unix you seems to be running Windows.
>
> Best,
>
> Mikhail Berman
>
> -----Original Message-----
> From: Michael Louie Loria [mailto:mlloria@stripped]
> Sent: Tuesday, September 12, 2006 9:55 PM
> To: win32@stripped
> Subject: Re: MySQLDump
>
>> Subject: MySQLDump
>> From: "Melissa Dougherty"
>> Date: Thu, 7 Sep 2006 12:37:46 -0400
>>
>> Does anyone use MySQLdump to export data from their db?  I'm having an
> issue dumping a table that's about 320M.  I get connection lost errors
> and have never successfully dumped the table.
>>
>> My goal was to have an another method of recovery if there was data
> failure.... do you user/developer error.  I'm an Oracle DBA and was
> trying to find something like the Oracle export.
>>
>> Any suggestions?
>>
>>
>> Melissa
>
> I use mysqldump to export data but not with that size. I don't know if
> there is a limitation to the size mysqldump can export. You could check
> the documentation.
>
>
> Here's my command.
> $mysqldump -u user test > test.sql -p
>
>
> try mysqldump with no other users connecting to the database. if it
> succeeds, probably locking issues.
>
> you could also try mysqldump from the localhost. if it succeeds,
> probably network congestion or others.
>
>
> -- 
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe:
> http://lists.mysql.com/win32?unsub=1
>
>
>
>
> -- 
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: 
> http://lists.mysql.com/win32?unsub=1
>
> 

Thread
Fw: MySQLDumpJorge Bastos13 Sep
  • Re: MySQLDumpMelissa Dougherty13 Sep
RE: MySQLDumpPaulo Urcid Pliego13 Sep
  • Re: MySQLDumpMelissa Dougherty14 Sep
Re: MySQLDumpdpgirago14 Sep
  • Re: MySQLDumpMelissa Dougherty14 Sep
Re: MySQLDumpdpgirago14 Sep
RE: MySQLDumpMikhail Berman14 Sep
  • Re: MySQLDumpMelissa Dougherty15 Sep
Re: MySQLDumpMelissa Dougherty19 Sep