Last Updated: Feb 13, 2008
MySQL has a unique pluggable storage engine architecture which provides the flexibility to support multiple storage engines. These storage engines act as handlers for different table types. Thus MySQL storage engines include both those that handle transaction-safe tables and those that handle non-transaction-safe tables along with many others. MySQL does this through their Pluggable Storage Engine Architecture. Thus users of MySQL can choose from a portfolio of purpose-built storage engines that are optimized for specific application domains. For more information see:
http://dev.mysql.com/doc/refman/5.1/en/storage-engines.html
http://dev.mysql.com/doc/refman/5.1/en/faqs-storage-engines.html
Is DB2 for i the same as the DB2 database on other systems? Where can I learn more?
No, DB2 is a family of databases with certain similarities as well as differences. IBM DB2 for i is a distinct product within the DB2 familiy. DB2 for i is the database that runs on the IBM i operating system on IBM Power Systems.
http://www-03.ibm.com/systems/i/software/db2/index.html
What is IBM i?
IBM i (previously known as i5/OS and OS/400) is an operating system. It is an integrated, easy to use environment that was designed by IBM for efficient, resilient business processing. DB2 is an integrated component within the i operating system. They cannot be decoupled. http://www-03.ibm.com/systems/i/
Is IBM i the operating system that runs on systems formerly known as the AS/400, iSeries, and System i?
Yes. http://www.redbooks.ibm.com/redpieces/abstracts/ga195486.html
What servers support IBM i?
IBM Power Systems run the IBM i operating system. This POWER processor-based servers also run AIX, IBM’s UNIX operating system, and Linux. The MySQL i DB2 Storage engine is only supported with IBM i.
What is the IBMDB2I Storage Engine for MySQL?
IBM i and DB2 represents a very specific storage domain. IBM i systems make heavy use of DB2 for data storage. The IBMDB2I Storage Engine allows users to create MySQL tables with a DB2 format type. This engine is included in MySQL for i installation by default. Then to use, the storage engine must be enabled.
Is the IBMDB2I Storage Engine an “adapter” that enables MySQL to talk to DB2 for i database?
Yes, you can think of it that way. DB2 tables on i can still be accessed directly from the system or via the IBMDB2I storage engine.
Does this mean that MySQL now understands the DB2 SQL-dialect, DB2 Stored Procedures, etc?
No, MySQL does not understand the DB2 SQL-dialect.
When using MySQL with the IBMDB2I Storage engine, you will still use MySQL commands based on the SQL language style that is selected within MySQL and not the DB2 style. Most of the MySQL database features defined from the MySQL perspective (for example triggers, stored procedures, views, etc.) are not observed in DB2 and vice versa. For more information the IBM Redbook URL.
Which versions of IBM i are supported by MySQL?
See http://www.mysql.com/support/supportedplatforms/enterprise.html
Can I access the MySQL Server on MySQL remotely using MySQL connectors and clients with languages such as C, C++, Java, PHP, Python, Ruby, etc?
Yes. The MySQL Server (mysqld) running on IBM i is accessible from client programs on the network just as it is on other MySQL supported platforms.
Can I develop MySQL Applications local to IBM i using C, C++, Java, PHP, Python, Ruby, etc?
Specifically PHP is the development bright spot on IBM i. The MySQL Database Server, along with PHP, in IBM i provides an open-community supported Web development and deployment stack, call the iAMP stack. The iAMP stack, which includes IBM i, Apache, MySQL, and PHP.
Are there any special benefits to using the IBMDB2I Storage Engine, rather than MyISAM or InnoDB?
Yes. There are several advantages. One of the most compelling advantages is the IBMDB2I Storage Engine stores the data in native DB2 format. Data in the DB2 format can be accessed either via MySQL or native i applications.
Data can be easily converted from a MySQL native storage engine into a DB2 data store. This makes it more convenient for other IBM i applications to access and exchange data with MySQL tables in a simple manner through DB2 for i native and SQL interfaces.
Does the IBM i platform restrict you to only the IBMDB2I Storage Engine for MySQL?
No. You can run other storage engines and running the DB2 for i Storage Engine is optional.
Does the IBM i platform allow you to continue using the tradition MySQL Storage Engines (MyISAM, InnoDB)?
Yes, running MySQL on i lets end-users use other MySQL storage engines. By default the IBMDB2I storage engine is disabled. To enable it see URL. ed
Within a particular application, are there any benefits to mix-n-match MyISAM, InnoDB, and the IBMDB2I Storage Engine?
Yes, each storage engine has its own specialized characteristics and features. Thus, depending on the needs of your application, you may benefit from using several different engines within your database. http://dev.mysql.com/doc/refman/5.1/en/pluggable-storage-overview.html
I have MySQL applications that use MyISAM and InnoDB. I can deploy these on any platform (e.g. Linux, Unix, MacOS, Windows). If I use the IBMDB2I Storage Engine, will I still be able to deploy my applications to all those platforms?
No. Since IBMDB2I Storage Engine is only available on IBM System I, any application that uses IBMDB2I Storage Engine must run on IBM System i.
Has IBM open sourced DB2 under the GPL license?
No. Please contact IBM about DB2.
Is the source code for IBMDB2I Storage Engine available?
Yes. The source code for the IBMDB2I Storage Engine is available under a IBM "GPL compatible" license. However, this storage engine acts as an “adapter” that enables MySQL to talk to the DB2 for i DB2. It is not the source code for DB2 itself.
Is the source code available at Launchpad.net (with the rest of MySQL source)?
Yes.
Who is responsible for development and bug-fixes for the IBMDB2I Storage Engine?
MySQL and IBM are responsible for development and bug-fixes for the IBMDB2I Storage Engine.
Where can I submit bug-reports?
Please report bugs to http://bugs.mysql.com/

