ing
the problem.
Thanks,
Steve Williams
-Original Message-
From: dan orlic [mailto:[EMAIL PROTECTED]
Sent: Friday, February 27, 2004 3:52 PM
To: Steve Williams
Cc: [EMAIL PROTECTED]
Subject: Re: InnoDB, mysqldump/mysql timeout dropping table (disaster
recovery)
perhaps you would get a better re
M
To: Steve Williams
Cc: [EMAIL PROTECTED]
Subject: Re: InnoDB, mysqldump/mysql timeout dropping table (disaster
recovery)
perhaps you would get a better response from doing scp... which runs
over ssh... or doing the mysqldump in a cron job, so it will
already be complete for transport by ssh. I st
prefer to just figure out which timeout is causing
> the problem.
>
> Thanks,
> Steve Williams
>
> -Original Message-
> From: dan orlic [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 27, 2004 3:52 PM
> To: Steve Williams
> Cc: [EMAIL PROTECTED]
> Subject: Re:
orlic [mailto:[EMAIL PROTECTED]
Sent: Friday, February 27, 2004 3:52 PM
To: Steve Williams
Cc: [EMAIL PROTECTED]
Subject: Re: InnoDB, mysqldump/mysql timeout dropping table (disaster
recovery)
perhaps you would get a better response from doing scp... which runs
over ssh... or doing the mysqldump
perhaps you would get a better response from doing scp... which runs
over ssh... or doing the mysqldump in a cron job, so it will
already be complete for transport by ssh. I still think scp is the more
proper way to go.
dan orlic
Steve Williams wrote:
Hi,
We have a (pre-existing) disaster re
Rafal Kedziorski <[EMAIL PROTECTED]> wrote:
>
> we have problems with import our dumped InnoDB tables.
>
> We get this error message:
>
> "Can't create table '.\mmcms_test\media_lock.frm' (errno: 150)"
>
> My tables which will be referenced by foreign keys will be dumped in the
> inncorect ord
