Hi!
- Original Message -
From: ""Sp.Raja"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Tuesday, July 27, 2004 5:52 PM
Subject: Re: Innodb assertion failure after binary backup-restore
> Thanks for your replies.
>
> Now I have three w
UNLOCK TABLES
Do you think #3 will work?
Regards,
Sp.Raja
> Original Message
> From: "Heikki Tuuri" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Tue, Jul-27-2004 6:24 PM
> Subject: Re: Innodb assertion failure after binary backup-restore
>
Sp.Raja
> Original Message
> From: "Heikki Tuuri" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Tue, Jul-27-2004 6:24 PM
> Subject: Re: Innodb assertion failure after binary backup-restore
>
> Hi!
>
> sync will not help.
>
&
In article <[EMAIL PROTECTED]>,
"Sp.Raja" <[EMAIL PROTECTED]> writes:
> Hi,
> I was able to solve this by calling sync command, as my previous mail say.
> Do you mean to say this will not work regardless of the whether we
> sync or not??
If it happens to work, then only by incident. I wouldn't r
are flushed ??
Thanks for your reply.
Thanks,
Sp.Raja
> Original Message
> From: "Heikki Tuuri" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Tue, Jul-27-2004 1:05 PM
> Subject: Re: Innodb assertion failure after binary backup-restore
&g
age
> From: "Heikki Tuuri" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Tue, Jul-27-2004 1:05 PM
> Subject: Re: Innodb assertion failure after binary backup-restore
>
> Hi!
>
> That method will not work. InnoDB must be quiet long enoug
Hi!
That method will not work. InnoDB must be quiet long enough so that it has
time to flush all the contents of the buffer pool to the data files.
Best regards,
Heikki Tuuri
Innobase Oy
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB
-23-2004 8:03 PM
> Subject: Re: Innodb assertion failure after binary backup-restore
>
> In some cases mysql crashes while restore is trying to destroy
> persistent databases and mysql.err says
>
> 000121 21:02:23 InnoDB: Database was not shut down normally.
> InnoDB: Starting r
In some cases mysql crashes while restore is trying to destroy persistent databases
and mysql.err says
000121 21:02:23 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 867418
In
