Importing raw MySQL files

2006-04-17 Thread Christopher Beale

Hi everyone.

I used to run mysql on a local server here, which has some databases 
which are very important to me on it. The server was running mysql on 
Arch Linux, but unfortunatly this crashed, I was not able to rebuild the 
operating system but I was able to recover the raw database files off of 
the hard disk. Is there a way of importing these to my MySQL 3.2 server? 
(I beleive that Arch Linux was running 5.0). I have tried simply placing 
them in the mysql database folder but I get errors such as Incorrect 
information in file: './my0007/ee_pm.frm... when I try and perform any 
operations in PhpMyAdmin.


Any help would be appreciated as I do not want to have to rebuilt the 
databases from scratch/


Cheers
Chris

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



RE: Importing raw MySQL files

2006-04-17 Thread Logan, David (SST - Adelaide)
Hi Chris,

Looks like you may have to either upgrade your current server to the
version the Arch Linux was running or install a second temp server of
that version, export the databases and then import them into the ver 3.2
server.

Personally, I'd look closely at upgrading if at all possible.

Regards


---
** _/ **  David Logan 
***   _/ ***  ITO Delivery Specialist - Database
*_/*  Hewlett-Packard Australia Ltd
_/_/_/  _/_/_/    E-Mail: [EMAIL PROTECTED]
   _/  _/  _/  _/     Desk:   +618 8408 4273
  _/  _/  _/_/_/  Mobile: 0417 268 665
*_/   **
**  _/    Postal: 148 Frome Street,
   _/ **  Adelaide SA 5001
  Australia 
invent   
---

-Original Message-
From: Christopher Beale [mailto:[EMAIL PROTECTED] 
Sent: Monday, 17 April 2006 7:46 PM
To: mysql@lists.mysql.com
Subject: Importing raw MySQL files

Hi everyone.

I used to run mysql on a local server here, which has some databases 
which are very important to me on it. The server was running mysql on 
Arch Linux, but unfortunatly this crashed, I was not able to rebuild the

operating system but I was able to recover the raw database files off of

the hard disk. Is there a way of importing these to my MySQL 3.2 server?

(I beleive that Arch Linux was running 5.0). I have tried simply placing

them in the mysql database folder but I get errors such as Incorrect 
information in file: './my0007/ee_pm.frm... when I try and perform any 
operations in PhpMyAdmin.

Any help would be appreciated as I do not want to have to rebuilt the 
databases from scratch/

Cheers
Chris

-- 
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: Importing raw MySQL files

2006-04-17 Thread Dan Buettner

Hi everyone.

I used to run mysql on a local server here, which has some databases 
which are very important to me on it. The server was running mysql 
on Arch Linux, but unfortunatly this crashed, I was not able to 
rebuild the operating system but I was able to recover the raw 
database files off of the hard disk. Is there a way of importing 
these to my MySQL 3.2 server? (I beleive that Arch Linux was running 
5.0). I have tried simply placing them in the mysql database folder 
but I get errors such as Incorrect information in file: 
'./my0007/ee_pm.frm... when I try and perform any operations in 
PhpMyAdmin.


Any help would be appreciated as I do not want to have to rebuilt 
the databases from scratch/


Cheers
Chris



Chris, you may be in luck.  MySQL MyISAM table files are binary 
compatible across platforms.  That is to say that database table 
files from Arch Linux will work fine on Mac, Solaris, Windows, etc., 
without modification.  I'm not as familiar with InnoDB tablespaces 
but they may work as well.  Definitely try this with a copy of your 
files, not the originals.


In all likelihood you need to update to at least the same version of 
the server software you were running on the now-crashed server.  In 
other words, if you update to 5.0.x and place the table files in the 
proper path, you should be OK.


MySQL 3.2 is a very old version and likely simply isn't compatible 
with tables created in 5.0.  If the situation were reversed (you had 
a 3.2 server that crashed and you wanted to bring the tables into 
5.0) that might work fine.


Hope this helps,
Dan


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]