Hi John,
The data files will give you some informations like log_file_size, mutliple
tablespace is being used or not. Although my.cnf can help you a lot. With
the above information, use it with newer version of mysql.
Krishna
On Wed, Jan 20, 2010 at 3:02 PM, Johny Brawo wrote:
> Hello!
>
> I g
Hi Johny
Do you have the my.cnf configuration file ?? that can simplify things.
Carlos
On 1/20/2010 3:32 AM, Johny Brawo wrote:
Hello!
I got all data files (ibdata1, ib_logfile, etc) recovevered from mine
old Debian 3.1 box (and i dont know MySQL version :( ). I want to get
that DB running a
Hello!
I got all data files (ibdata1, ib_logfile, etc) recovevered from mine
old Debian 3.1 box (and i dont know MySQL version :( ). I want to get
that DB running again.
Can i copy these files to newer version of MySQL, and if i can - how?
Any commands, any parameters?
--
MySQL General Mailing L
Jeremy Zawodny wrote:
My question is: should I trust my data now?
Yes. InnoDB is fully ACID compliant.
So anyway, should I bother with a restore? What's the chance of having
data corrupted / missing after a power 'failure' and recovery as above?
The on
lesystem.
>
> The XFS recovery proceeded without any complaints.
> The InnoDB recovery also seemed to go smoothly ( great work by the way ):
>
> 040506 9:38:41 InnoDB: Database was not shut down normally.
> InnoDB: Starting recovery from log files...
> InnoDB: Starting lo
Hi all.
My boss just pulled the power on our MySQL server.
Yes, I've already thanked him.
It's a 4.0.18 server, with MyISAM tables and InnoDB tables, running on
a 2.6.5 kernel and XFS filesystem.
The XFS recovery proceeded without any complaints.
The InnoDB recovery also se
Hi,
I have been backing up via the dubious method of copying the database data folder onto
another machine where it is properly backed up onto DLT.
(yes, I know I should have used mysqldump!)
Recovering some tables today I copied the files back into their position (including the ibdata1 file and
Benoit,
- Original Message -
From: "Benoit St-Jean" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Friday, March 21, 2003 4:54 AM
Subject: Stopping InnoDb recovery and fixed columns
> I recently had a bad experience with a "feature" of
> Inn
I recently had a bad experience with a "feature" of
InnoDb. Whenever the server crashes, on the next
startup InnoDb detects that the server ended
abnormally and performs a
repair/rollback/magic/whatever before allowing you to
connect to the server.
Unfortunately, I had to create an index on a 45
m
Heikki Tuuri wrote:
log files are as important a part of a database as ibdata files.
Trust me, I know; they didn't get backed up I've realized too late
though ...
You can try using some dummy log files from another installation and set
force recovery to 6 to skip the log scan.
... what's
Michael,
- Original Message -
From: "Michael T. Babcock" <[EMAIL PROTECTED]>
To: "Heikki Tuuri" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, November 07, 2002 4:36 PM
Subject: Re: InnoDB recovery
> Heikki Tuuri wrote:
>
>
Heikki Tuuri wrote:
if you have on tape old images of ibdata files and ib_logfile's, you can try
crash recovery from them, possibly using innodb_force_recovery=6.
Unfortunately, as mentionned, I only have the data files on tape, no log
files.
Are the data files 'dumpable' ??
SQL
--
Michae
Michael,
- Original Message -
From: ""Michael T. Babcock"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Tuesday, November 05, 2002 6:00 PM
Subject: InnoDB recovery
> I have a table that accidentally had a query run on it that NULL'd a
&
I have a table that accidentally had a query run on it that NULL'd a
certain field of the entire table. I have the data on old versions of
the binary table files from backup tapes, but have no idea how to get
this information out of those old binary table files. I unfortunately
don't have the
Bonjour,
I've rebooted my server with "sync;sync;reboot". It seems that
Mysql/InnoDB did not have enough time for shutting down properly
because when the server restarted I had these messages in the error
log of Mysql :
InnoDB: Doing recovery: scanned up to log sequence number
15 matches
Mail list logo
