Hi ed, all!

ed wrote:
> I have recently noticed I can not access a PHP application's data files,
> and the errors I am getting seem to show that a recent update of the
> distro (mandriva) no longer supports innodb, and this may be a reason

Which version were you using before, and which one are you using now?


> (if this is not some sort of "catchall" error). I would like to know how
> to add innodb plugin back into my mysql, or to convert the data to a
> usable format. I would be pleased with a pointer to the correct rtfd
> location.

>From your output, I'd say they removed or unconfigured some parts in the
source before creating binaries.
(If your previous version was taken from the same source, they did an
incompatible change IMNSHO, and I hope they did give a thorough warning.
If not, you should raise a complaint.)

> 
> 
> I guess wordwrap is going to mess this up;
> 
> 
> mysql> show engines ;
> +------------+---------+-----------------------------------------------------------+--------------+------+------------+
> 
> | Engine     | Support | Comment                                      |
> Transactions | XA   | Savepoints |
> +------------+---------+-----------------------------------------------------------+--------------+------+------------+
> 
> | MRG_MYISAM | YES | Collection of identical MyISAM tables | NO  | NO  
> | NO  |
> | CSV                 | YES     | CSV storage engine    | NO   |
> NO         |
> | MEMORY         | YES     | Hash based, stored in memory, useful for
> temporary tables | NO           | NO   | NO         |
> | MyISAM           | DEFAULT | Default engine as of MySQL 3.23 with
> great performance    | NO           | NO   | NO         |
> +------------+---------+-----------------------------------------------------------+--------------+------+------------+
> 
> 
> show plugins;
> +------------+--------+----------------+---------+---------+
> | Name       | Status | Type           | Library | License |
> +------------+--------+----------------+---------+---------+
> | binlog     | ACTIVE | STORAGE ENGINE | NULL    | GPL    |
> | partition  | ACTIVE | STORAGE ENGINE | NULL    | GPL   |
> | CSV        | ACTIVE | STORAGE ENGINE | NULL    | GPL    |
> | MEMORY | ACTIVE | STORAGE ENGINE|NULL |GPL         |
> | MyISAM  | ACTIVE | STORAGE ENGINE | NULL| GPL|
> | MRG_MYISAM | ACTIVE | STORAGE ENGINE | NULL    | GPL     |


This is what "show engines" and "show plugins" report in my test build
of post-5.1.57 (complete sources):

  ===== ENGINES =====
  Engine  Support Comment Transactions    XA      Savepoints
  ndbcluster      NO      Clustered, fault-tolerant tables        NULL
  NULL    NULL
  MRG_MYISAM      YES     Collection of identical MyISAM tables   NO
  NO      NO
  BLACKHOLE       YES     /dev/null storage engine (anything you write
to it disappears)  NO      NO      NO
  CSV     YES     CSV storage engine      NO      NO      NO
  MEMORY  YES     Hash based, stored in memory, useful for temporary
tables       NO      NO      NO
  FEDERATED       NO      Federated MySQL storage engine  NULL    NULL
  NULL
  ARCHIVE YES     Archive storage engine  NO      NO      NO
  InnoDB  YES     Supports transactions, row-level locking, and foreign
keys      YES     YES     YES
  MyISAM  DEFAULT Default engine as of MySQL 3.23 with great performance
 NO      NO      NO

  ===== PLUGINS =====
  Name    Status  Type    Library License
  binlog  ACTIVE  STORAGE ENGINE  NULL    GPL
  partition       ACTIVE  STORAGE ENGINE  NULL    GPL
  ARCHIVE ACTIVE  STORAGE ENGINE  NULL    GPL
  BLACKHOLE       ACTIVE  STORAGE ENGINE  NULL    GPL
  CSV     ACTIVE  STORAGE ENGINE  NULL    GPL
  FEDERATED       DISABLED        STORAGE ENGINE  NULL    GPL
  MEMORY  ACTIVE  STORAGE ENGINE  NULL    GPL
  InnoDB  ACTIVE  STORAGE ENGINE  NULL    GPL
  MRG_MYISAM      ACTIVE  STORAGE ENGINE  NULL    GPL
  MyISAM  ACTIVE  STORAGE ENGINE  NULL    GPL
  ndbcluster      DISABLED        STORAGE ENGINE  NULL    GPL

I don't think there is a way to add those missing parts back to your
current binaries.

If you have tables using the InnoDB engine, I see these approaches you
could take:

1) Go back to the version you used previously.
   You have a full system backup, I trust ?

2) Build from source.

3) Use other binary packages, like those available directly from MySQL
   (now: Oracle).

> 
> 
> [[...]]

HTH,
Joerg

-- 
Joerg Bruehe,  MySQL Build Team,  joerg.bru...@oracle.com
ORACLE Deutschland B.V. & Co. KG,   Komturstrasse 18a,   D-12099 Berlin
Geschaeftsfuehrer: Juergen Kunz, Marcel v.d. Molen, Alexander v.d. Ven
Amtsgericht Muenchen: HRA 95603

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=arch...@jab.org

Reply via email to