SEO

Hi Everyone,

I have some problems with raw mysql data such as MYD MYI frm files. I
got some files from my friend and he does not know which version use
those files. I have installed 3 different mysql version but i still
get "....was created with a different version of MySQL and cannot be
read" error. How can i determine version or convert to sql files?

Thanks from now on,

Serdar Sahin

Beyza wrote:
> Hi Everyone,
>
> I have some problems with raw mysql data such as MYD MYI frm files. I
> got some files from my friend and he does not know which version use
> those files. I have installed 3 different mysql version but i still
> get "....was created with a different version of MySQL and cannot be
> read" error. How can i determine version or convert to sql files?
>
> Thanks from now on,
>
> Serdar Sahin
>

In general you can only use the files themselves if the version and OS
are exactly the same. There may be some exceptions, but don't count on it.

Have your friend export the database(s) instead. Then you can import
them. Otherwise you'll have to find out from your friend exactly which
version and os he is using.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

Its better you ask the sql dump instead the raw data. The MyIsam raw
data is transferable. If you got MyIsam raw data you can use at any
version server.

--
http://ascii.mastervb.net -- ASCII Art Generator
http://www.mastervb.net/phpbooks -- Best php/mysql books

On Feb 13, 6:52 am, "Beyza" <anlamar...@gmail.com> wrote:
> Hi Everyone,
>
> I have some problems with raw mysql data such as MYD MYI frm files. I
> got some files from my friend and he does not know which version use
> those files. I have installed 3 different mysql version but i still
> get "....was created with a different version of MySQL and cannot be
> read" error. How can i determine version or convert to sql files?
>
> Thanks from now on,
>
> Serdar Sahin

Jerry Stuckle <jstucklex@attglobal.net> wrote:
> Beyza wrote:
>> Hi Everyone,
>>
>> I have some problems with raw mysql data such as MYD MYI frm files. I
>> got some files from my friend and he does not know which version use
>> those files. I have installed 3 different mysql version but i still
>> get "....was created with a different version of MySQL and cannot be
>> read" error. How can i determine version or convert to sql files?
>
> In general you can only use the files themselves if the version and OS
> are exactly the same.

No. And No.

> There may be some exceptions, but don't count on it.

It is one of the features of MyISAM that data is stored platform
independent. Also MyISAM is backwards compatible. Newer Server can
always read the older versions. There may be issues with indexes,
but reading, especially exporting data should always work.

Table version is in the .frm file normally.
Here: http://dev.mysql.com/doc/internals/en/index.html
is some background information.


So to use an unknown MyISAM table,
- get latest MySQL server
- run myisamchk on the table, if that succedds
- put table in datadir and access it


XL
--
Axel Schwenke, Support Engineer, MySQL AB

Online User Manual: http://dev.mysql.com/doc/refman/5.0/en/
MySQL User Forums: http://forums.mysql.com/

Axel Schwenke wrote:
> Jerry Stuckle <jstucklex@attglobal.net> wrote:
>> Beyza wrote:
>>> Hi Everyone,
>>>
>>> I have some problems with raw mysql data such as MYD MYI frm files. I
>>> got some files from my friend and he does not know which version use
>>> those files. I have installed 3 different mysql version but i still
>>> get "....was created with a different version of MySQL and cannot be
>>> read" error. How can i determine version or convert to sql files?
>> In general you can only use the files themselves if the version and OS
>> are exactly the same.
>
> No. And No.
>
>> There may be some exceptions, but don't count on it.
>
> It is one of the features of MyISAM that data is stored platform
> independent. Also MyISAM is backwards compatible. Newer Server can
> always read the older versions. There may be issues with indexes,
> but reading, especially exporting data should always work.
>
> Table version is in the .frm file normally.
> Here: http://dev.mysql.com/doc/internals/en/index.html
> is some background information.
>
>
> So to use an unknown MyISAM table,
> - get latest MySQL server
> - run myisamchk on the table, if that succedds
> - put table in datadir and access it
>
>
> XL
> --
> Axel Schwenke, Support Engineer, MySQL AB
>
> Online User Manual: http://dev.mysql.com/doc/refman/5.0/en/
> MySQL User Forums: http://forums.mysql.com/

Axel,

It's a good concept. But it doesn't always work in practice.

Export/Import always works. I've often had problems with copying the
files, especially between OS's and versions.

Now I understand when you go down in version it might not work. But
going to later versions doesn't always work, either.

Backup/restore always works (except for things like changes in the
password algorithm).

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

Hi again,

Thanks for your response guys..

I have tried to install many versions (including latest alpha, beta,
stable and old versions) but still get that error and do not know how
can i solve. Even i have used mysql recovery program but nothing
changed.

I think better to find sql export, will try..

Thanks a lot..

Serdar Sahin

On Feb 13, 1:35 pm, Jerry Stuckle <jstuck...@attglobal.net> wrote:
> Axel Schwenke wrote:
> > Jerry Stuckle <jstuck...@attglobal.net> wrote:
> >> Beyza wrote:
> >>> Hi Everyone,
>
> >>> I have some problems with raw mysql data such as MYD MYI frm files. I
> >>> got some files from my friend and he does not know which version use
> >>> those files. I have installed 3 different mysql version but i still
> >>> get "....was created with a different version of MySQL and cannot be
> >>> read" error. How can i determine version or convert to sql files?
> >> In general you can only use the files themselves if the version and OS
> >> are exactly the same.
>
> > No. And No.
>
> >> There may be some exceptions, but don't count on it.
>
> > It is one of the features of MyISAM that data is stored platform
> > independent. Also MyISAM is backwards compatible. Newer Server can
> > always read the older versions. There may be issues with indexes,
> > but reading, especially exporting data should always work.
>
> > Table version is in the .frm file normally.
> > Here:http://dev.mysql.com/doc/internals/en/index.html
> > is some background information.
>
> > So to use an unknown MyISAM table,
> > - get latest MySQL server
> > - run myisamchk on the table, if that succedds
> > - put table in datadir and access it
>
> > XL
> > --
> > Axel Schwenke, Support Engineer, MySQL AB
>
> > Online User Manual:http://dev.mysql.com/doc/refman/5.0/en/
> > MySQL User Forums: http://forums.mysql.com/
>
> Axel,
>
> It's a good concept. But it doesn't always work in practice.
>
> Export/Import always works. I've often had problems with copying the
> files, especially between OS's and versions.
>
> Now I understand when you go down in version it might not work. But
> going to later versions doesn't always work, either.
>
> Backup/restore always works (except for things like changes in the
> password algorithm).
>
> --
> ==================
> Remove the "x" from my email address
> Jerry Stuckle
> JDS Computer Training Corp.
> jstuck...@attglobal.net
> ==================

Jerry Stuckle <jstucklex@attglobal.net> wrote:
> Axel Schwenke wrote:
>>
>> It is one of the features of MyISAM that data is stored platform
>> independent. Also MyISAM is backwards compatible. Newer Server can
>> always read the older versions. There may be issues with indexes,
>> but reading, especially exporting data should always work.

> It's a good concept. But it doesn't always work in practice.
> Export/Import always works. I've often had problems with copying the
> files, especially between OS's and versions.

Since the platform independence is an important feature of MyISAM, I
would like to know the details.

> Now I understand when you go down in version it might not work. But
> going to later versions doesn't always work, either.

There may be problems if you try to open files from a *very* old MySQL
version on a recent server. However, for upgrading MySQL you usually
don't need to unload/load your data but just upgrade the executables
and run mysql_upgrade (that uses myisamchk behind the scenes).

> Backup/restore always works (except for things like changes in the
> password algorithm).

ACK on that. SQL dumps are better in most cases.


XL
--
Axel Schwenke, Support Engineer, MySQL AB

Online User Manual: http://dev.mysql.com/doc/refman/5.0/en/
MySQL User Forums: http://forums.mysql.com/

Axel Schwenke wrote:
> Jerry Stuckle <jstucklex@attglobal.net> wrote:
>> Axel Schwenke wrote:
>>> It is one of the features of MyISAM that data is stored platform
>>> independent. Also MyISAM is backwards compatible. Newer Server can
>>> always read the older versions. There may be issues with indexes,
>>> but reading, especially exporting data should always work.
>
>> It's a good concept. But it doesn't always work in practice.
>> Export/Import always works. I've often had problems with copying the
>> files, especially between OS's and versions.
>
> Since the platform independence is an important feature of MyISAM, I
> would like to know the details.
>

I wish I could give you exact versions, but I can't - it's been close to
a year ago that I had a customer with this problem. But they were
trying to go from a 3.x version to 4.1.x. Copying their files over
didn't work (yes, the MySQL was down when they tried). But backing up
and restoring the database worked fine. IIRC, one system was linux and
the other Windows, but I'm not sure which was which (or even if I'm
correct on this). And I'm sure I told them to FTP the files in binary
mode (just because I've seen that screw things up too often).

I never reported it because they didn't want to spend any time
troubleshooting the problem - they just wanted it to work. I didn't
push it because I wouldn't necessarily expect it to work.

Sorry I don't have more details - but as I said, it's been quite a while.

>> Now I understand when you go down in version it might not work. But
>> going to later versions doesn't always work, either.
>
> There may be problems if you try to open files from a *very* old MySQL
> version on a recent server. However, for upgrading MySQL you usually
> don't need to unload/load your data but just upgrade the executables
> and run mysql_upgrade (that uses myisamchk behind the scenes).
>
>> Backup/restore always works (except for things like changes in the
>> password algorithm).
>
> ACK on that. SQL dumps are better in most cases.
>
>
> XL
> --
> Axel Schwenke, Support Engineer, MySQL AB
>
> Online User Manual: http://dev.mysql.com/doc/refman/5.0/en/
> MySQL User Forums: http://forums.mysql.com/


--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================