Re: InnoDB problems under 5.1.9
Thanks for the tip. Simple problem, my innodb data file was created with the default my.cnf. When I started it with the large_table version, it used different innodb table space size. Therefore would not start :) Cheers, Ben Dan Buettner wrote: Ben, looks like you've either got it disabled in my.cnf or with a startup flag, or you've not set all the needed options for InnoDB. See http://dev.mysql.com/doc/refman/5.0/en/mysqld-max.html, near the bottom of the page it explains what DISABLED means and refers you to the error log for messages. Dan Ben Clewett wrote: Hi Dan, This is what I have. What does this mean with regards to InnoDB? ++--++--+-++ | Engine | Support | Comment | Transactions | XA | Savepoints | ++--++--+-++ | CSV| YES | CSV storage engine | NO | NO | NO | | MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO | NO | NO | | MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO | | InnoDB | DISABLED | Supports transactions, row-level locking, and foreign keys | YES | YES | YES| | BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) | NO | NO | NO | | MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | NO | NO | NO | | BerkeleyDB | DISABLED | Supports transactions and page-level locking | YES | NO | YES| | ARCHIVE| YES | Archive storage engine | NO | NO | NO | ++--++--+-++ Thanks, Dan Buettner wrote: Ben, what does SHOW ENGINES show you? It should list all known storage engines and indicate whether your MySQL install supports it or not. Here's mine (5.0.21) for comparison; I was able to create a test table as InnoDB and the SHOW CREATE showed it as InnoDB: -> show engines; ++-++ | Engine | Support | Comment | ++-++ | MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | | MEMORY | YES | Hash based, stored in memory, useful for temporary tables | | InnoDB | YES | Supports transactions, row-level locking, and foreign keys | | BerkeleyDB | NO | Supports transactions and page-level locking | | BLACKHOLE | NO | /dev/null storage engine (anything you write to it disappears) | | EXAMPLE| NO | Example storage engine | | ARCHIVE| YES | Archive storage engine | | CSV| NO | CSV storage engine | | ndbcluster | NO | Clustered, fault-tolerant, memory-based tables | | FEDERATED | NO | Federated MySQL storage engine | | MRG_MYISAM | YES | Collection of identical MyISAM tables | | ISAM | NO | Obsolete storage engine | ++-++ 12 rows in set (0.00 sec) Ben Clewett wrote: Hi Gerald, I am sure I don't have this in my my.cfg. I am using the supplied 'large table' my.cfg. The *only* innodb option I have is the command line parameter to mysqld: --innodb If anybody has any other options about how to get innodb working in 5.1.9, I'd be very interested! Thanks for the advise, Ben gerald_clark wrote: Ben Clewett wrote: Dear MySQL, I've installed 5.1.9 from source on a SUSE 10 box. But I can't get InnoDB tables respected. I have used the correct compilation flag (--with-innodb). SHOW VARIABLES; lists all the usual innodb variables. The innodb table space has been created in ~/var/ibdata1. But if I enter: CREATE TABLE a ( a int NOT NULL PRIMARY KEY ) ENGINE=InnoDB; SHOW CREATE TABLE a; CREATE TABLE `a` ( `a` int(10) NOT NULL PRIMARY KEY ) ENGINE=MyISAM As you can see, an InnoDB has become an MyISAM and will be stored in ~/var/test/a.* I am using the large table .cnf file. Everything else is much as default. Can anybody help me? Regards, Ben make sure you don't have skip--innodb in your my.cnf file. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB problems under 5.1.9
Thanks for the excellent reference, this gives me a lot to go on. My server is in bits at the moment, I'll let you know when it's up again! Ben Dan Buettner wrote: Ben, looks like you've either got it disabled in my.cnf or with a startup flag, or you've not set all the needed options for InnoDB. See http://dev.mysql.com/doc/refman/5.0/en/mysqld-max.html, near the bottom of the page it explains what DISABLED means and refers you to the error log for messages. Dan Ben Clewett wrote: Hi Dan, This is what I have. What does this mean with regards to InnoDB? ++--++--+-++ | Engine | Support | Comment | Transactions | XA | Savepoints | ++--++--+-++ | CSV| YES | CSV storage engine | NO | NO | NO | | MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO | NO | NO | | MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO | | InnoDB | DISABLED | Supports transactions, row-level locking, and foreign keys | YES | YES | YES| | BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) | NO | NO | NO | | MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | NO | NO | NO | | BerkeleyDB | DISABLED | Supports transactions and page-level locking | YES | NO | YES| | ARCHIVE| YES | Archive storage engine | NO | NO | NO | ++--++--+-++ Thanks, Dan Buettner wrote: Ben, what does SHOW ENGINES show you? It should list all known storage engines and indicate whether your MySQL install supports it or not. Here's mine (5.0.21) for comparison; I was able to create a test table as InnoDB and the SHOW CREATE showed it as InnoDB: -> show engines; ++-++ | Engine | Support | Comment | ++-++ | MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | | MEMORY | YES | Hash based, stored in memory, useful for temporary tables | | InnoDB | YES | Supports transactions, row-level locking, and foreign keys | | BerkeleyDB | NO | Supports transactions and page-level locking | | BLACKHOLE | NO | /dev/null storage engine (anything you write to it disappears) | | EXAMPLE| NO | Example storage engine | | ARCHIVE| YES | Archive storage engine | | CSV| NO | CSV storage engine | | ndbcluster | NO | Clustered, fault-tolerant, memory-based tables | | FEDERATED | NO | Federated MySQL storage engine | | MRG_MYISAM | YES | Collection of identical MyISAM tables | | ISAM | NO | Obsolete storage engine | ++-++ 12 rows in set (0.00 sec) Ben Clewett wrote: Hi Gerald, I am sure I don't have this in my my.cfg. I am using the supplied 'large table' my.cfg. The *only* innodb option I have is the command line parameter to mysqld: --innodb If anybody has any other options about how to get innodb working in 5.1.9, I'd be very interested! Thanks for the advise, Ben gerald_clark wrote: Ben Clewett wrote: Dear MySQL, I've installed 5.1.9 from source on a SUSE 10 box. But I can't get InnoDB tables respected. I have used the correct compilation flag (--with-innodb). SHOW VARIABLES; lists all the usual innodb variables. The innodb table space has been created in ~/var/ibdata1. But if I enter: CREATE TABLE a ( a int NOT NULL PRIMARY KEY ) ENGINE=InnoDB; SHOW CREATE TABLE a; CREATE TABLE `a` ( `a` int(10) NOT NULL PRIMARY KEY ) ENGINE=MyISAM As you can see, an InnoDB has become an MyISAM and will be stored in ~/var/test/a.* I am using the large table .cnf file. Everything else is much as default. Can anybody help me? Regards, Ben make sure you don't have skip--innodb in your my.cnf file. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB problems under 5.1.9
Ben, looks like you've either got it disabled in my.cnf or with a startup flag, or you've not set all the needed options for InnoDB. See http://dev.mysql.com/doc/refman/5.0/en/mysqld-max.html, near the bottom of the page it explains what DISABLED means and refers you to the error log for messages. Dan Ben Clewett wrote: Hi Dan, This is what I have. What does this mean with regards to InnoDB? ++--++--+-++ | Engine | Support | Comment | Transactions | XA | Savepoints | ++--++--+-++ | CSV| YES | CSV storage engine | NO | NO | NO | | MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO | NO | NO | | MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO | | InnoDB | DISABLED | Supports transactions, row-level locking, and foreign keys | YES | YES | YES| | BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) | NO | NO | NO | | MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | NO | NO | NO | | BerkeleyDB | DISABLED | Supports transactions and page-level locking | YES | NO | YES| | ARCHIVE| YES | Archive storage engine | NO | NO | NO | ++--++--+-++ Thanks, Dan Buettner wrote: Ben, what does SHOW ENGINES show you? It should list all known storage engines and indicate whether your MySQL install supports it or not. Here's mine (5.0.21) for comparison; I was able to create a test table as InnoDB and the SHOW CREATE showed it as InnoDB: -> show engines; ++-++ | Engine | Support | Comment | ++-++ | MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | | MEMORY | YES | Hash based, stored in memory, useful for temporary tables | | InnoDB | YES | Supports transactions, row-level locking, and foreign keys | | BerkeleyDB | NO | Supports transactions and page-level locking | | BLACKHOLE | NO | /dev/null storage engine (anything you write to it disappears) | | EXAMPLE| NO | Example storage engine | | ARCHIVE| YES | Archive storage engine | | CSV| NO | CSV storage engine | | ndbcluster | NO | Clustered, fault-tolerant, memory-based tables | | FEDERATED | NO | Federated MySQL storage engine | | MRG_MYISAM | YES | Collection of identical MyISAM tables | | ISAM | NO | Obsolete storage engine | ++-++ 12 rows in set (0.00 sec) Ben Clewett wrote: Hi Gerald, I am sure I don't have this in my my.cfg. I am using the supplied 'large table' my.cfg. The *only* innodb option I have is the command line parameter to mysqld: --innodb If anybody has any other options about how to get innodb working in 5.1.9, I'd be very interested! Thanks for the advise, Ben gerald_clark wrote: Ben Clewett wrote: Dear MySQL, I've installed 5.1.9 from source on a SUSE 10 box. But I can't get InnoDB tables respected. I have used the correct compilation flag (--with-innodb). SHOW VARIABLES; lists all the usual innodb variables. The innodb table space has been created in ~/var/ibdata1. But if I enter: CREATE TABLE a ( a int NOT NULL PRIMARY KEY ) ENGINE=InnoDB; SHOW CREATE TABLE a; CREATE TABLE `a` ( `a` int(10) NOT NULL PRIMARY KEY ) ENGINE=MyISAM As you can see, an InnoDB has become an MyISAM and will be stored in ~/var/test/a.* I am using the large table .cnf file. Everything else is much as default. Can anybody help me? Regards, Ben make sure you don't have skip--innodb in your my.cnf file. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB problems under 5.1.9
Hi Dan, This is what I have. What does this mean with regards to InnoDB? ++--++--+-++ | Engine | Support | Comment | Transactions | XA | Savepoints | ++--++--+-++ | CSV| YES | CSV storage engine | NO | NO | NO | | MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO | NO | NO | | MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO | | InnoDB | DISABLED | Supports transactions, row-level locking, and foreign keys | YES | YES | YES| | BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) | NO | NO | NO | | MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | NO | NO | NO | | BerkeleyDB | DISABLED | Supports transactions and page-level locking | YES | NO | YES| | ARCHIVE| YES | Archive storage engine | NO | NO | NO | ++--++--+-++ Thanks, Dan Buettner wrote: Ben, what does SHOW ENGINES show you? It should list all known storage engines and indicate whether your MySQL install supports it or not. Here's mine (5.0.21) for comparison; I was able to create a test table as InnoDB and the SHOW CREATE showed it as InnoDB: -> show engines; ++-++ | Engine | Support | Comment | ++-++ | MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | | MEMORY | YES | Hash based, stored in memory, useful for temporary tables | | InnoDB | YES | Supports transactions, row-level locking, and foreign keys | | BerkeleyDB | NO | Supports transactions and page-level locking | | BLACKHOLE | NO | /dev/null storage engine (anything you write to it disappears) | | EXAMPLE| NO | Example storage engine | | ARCHIVE| YES | Archive storage engine | | CSV| NO | CSV storage engine | | ndbcluster | NO | Clustered, fault-tolerant, memory-based tables | | FEDERATED | NO | Federated MySQL storage engine | | MRG_MYISAM | YES | Collection of identical MyISAM tables | | ISAM | NO | Obsolete storage engine | ++-++ 12 rows in set (0.00 sec) Ben Clewett wrote: Hi Gerald, I am sure I don't have this in my my.cfg. I am using the supplied 'large table' my.cfg. The *only* innodb option I have is the command line parameter to mysqld: --innodb If anybody has any other options about how to get innodb working in 5.1.9, I'd be very interested! Thanks for the advise, Ben gerald_clark wrote: Ben Clewett wrote: Dear MySQL, I've installed 5.1.9 from source on a SUSE 10 box. But I can't get InnoDB tables respected. I have used the correct compilation flag (--with-innodb). SHOW VARIABLES; lists all the usual innodb variables. The innodb table space has been created in ~/var/ibdata1. But if I enter: CREATE TABLE a ( a int NOT NULL PRIMARY KEY ) ENGINE=InnoDB; SHOW CREATE TABLE a; CREATE TABLE `a` ( `a` int(10) NOT NULL PRIMARY KEY ) ENGINE=MyISAM As you can see, an InnoDB has become an MyISAM and will be stored in ~/var/test/a.* I am using the large table .cnf file. Everything else is much as default. Can anybody help me? Regards, Ben make sure you don't have skip--innodb in your my.cnf file. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB problems under 5.1.9
Ben, what does SHOW ENGINES show you? It should list all known storage engines and indicate whether your MySQL install supports it or not. Here's mine (5.0.21) for comparison; I was able to create a test table as InnoDB and the SHOW CREATE showed it as InnoDB: -> show engines; ++-++ | Engine | Support | Comment | ++-++ | MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | | MEMORY | YES | Hash based, stored in memory, useful for temporary tables | | InnoDB | YES | Supports transactions, row-level locking, and foreign keys | | BerkeleyDB | NO | Supports transactions and page-level locking | | BLACKHOLE | NO | /dev/null storage engine (anything you write to it disappears) | | EXAMPLE| NO | Example storage engine | | ARCHIVE| YES | Archive storage engine | | CSV| NO | CSV storage engine | | ndbcluster | NO | Clustered, fault-tolerant, memory-based tables | | FEDERATED | NO | Federated MySQL storage engine | | MRG_MYISAM | YES | Collection of identical MyISAM tables | | ISAM | NO | Obsolete storage engine | ++-++ 12 rows in set (0.00 sec) Ben Clewett wrote: Hi Gerald, I am sure I don't have this in my my.cfg. I am using the supplied 'large table' my.cfg. The *only* innodb option I have is the command line parameter to mysqld: --innodb If anybody has any other options about how to get innodb working in 5.1.9, I'd be very interested! Thanks for the advise, Ben gerald_clark wrote: Ben Clewett wrote: Dear MySQL, I've installed 5.1.9 from source on a SUSE 10 box. But I can't get InnoDB tables respected. I have used the correct compilation flag (--with-innodb). SHOW VARIABLES; lists all the usual innodb variables. The innodb table space has been created in ~/var/ibdata1. But if I enter: CREATE TABLE a ( a int NOT NULL PRIMARY KEY ) ENGINE=InnoDB; SHOW CREATE TABLE a; CREATE TABLE `a` ( `a` int(10) NOT NULL PRIMARY KEY ) ENGINE=MyISAM As you can see, an InnoDB has become an MyISAM and will be stored in ~/var/test/a.* I am using the large table .cnf file. Everything else is much as default. Can anybody help me? Regards, Ben make sure you don't have skip--innodb in your my.cnf file. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB problems under 5.1.9
Hi Gerald, I am sure I don't have this in my my.cfg. I am using the supplied 'large table' my.cfg. The *only* innodb option I have is the command line parameter to mysqld: --innodb If anybody has any other options about how to get innodb working in 5.1.9, I'd be very interested! Thanks for the advise, Ben gerald_clark wrote: Ben Clewett wrote: Dear MySQL, I've installed 5.1.9 from source on a SUSE 10 box. But I can't get InnoDB tables respected. I have used the correct compilation flag (--with-innodb). SHOW VARIABLES; lists all the usual innodb variables. The innodb table space has been created in ~/var/ibdata1. But if I enter: CREATE TABLE a ( a int NOT NULL PRIMARY KEY ) ENGINE=InnoDB; SHOW CREATE TABLE a; CREATE TABLE `a` ( `a` int(10) NOT NULL PRIMARY KEY ) ENGINE=MyISAM As you can see, an InnoDB has become an MyISAM and will be stored in ~/var/test/a.* I am using the large table .cnf file. Everything else is much as default. Can anybody help me? Regards, Ben make sure you don't have skip--innodb in your my.cnf file. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB problems under 5.1.9
Hi Gerald, I am sure I don't have this in my my.cfg. I am using the supplied 'large table' my.cfg. The *only* innodb option I have is the command line parameter to mysqld: --innodb If anybody has any other options about how to get innodb working in 5.1.9, I'd be very interested! Thanks for the advise, Ben gerald_clark wrote: Ben Clewett wrote: Dear MySQL, I've installed 5.1.9 from source on a SUSE 10 box. But I can't get InnoDB tables respected. I have used the correct compilation flag (--with-innodb). SHOW VARIABLES; lists all the usual innodb variables. The innodb table space has been created in ~/var/ibdata1. But if I enter: CREATE TABLE a ( a int NOT NULL PRIMARY KEY ) ENGINE=InnoDB; SHOW CREATE TABLE a; CREATE TABLE `a` ( `a` int(10) NOT NULL PRIMARY KEY ) ENGINE=MyISAM As you can see, an InnoDB has become an MyISAM and will be stored in ~/var/test/a.* I am using the large table .cnf file. Everything else is much as default. Can anybody help me? Regards, Ben make sure you don't have skip--innodb in your my.cnf file. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB problems under 5.1.9
Ben Clewett wrote: Dear MySQL, I've installed 5.1.9 from source on a SUSE 10 box. But I can't get InnoDB tables respected. I have used the correct compilation flag (--with-innodb). SHOW VARIABLES; lists all the usual innodb variables. The innodb table space has been created in ~/var/ibdata1. But if I enter: CREATE TABLE a ( a int NOT NULL PRIMARY KEY ) ENGINE=InnoDB; SHOW CREATE TABLE a; CREATE TABLE `a` ( `a` int(10) NOT NULL PRIMARY KEY ) ENGINE=MyISAM As you can see, an InnoDB has become an MyISAM and will be stored in ~/var/test/a.* I am using the large table .cnf file. Everything else is much as default. Can anybody help me? Regards, Ben make sure you don't have skip--innodb in your my.cnf file. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB problems under 5.1.9
Very very odd. I am compiling with the --use-innodb option. I am starting mysqld with the --innodb option. The table space is created for innodb. But SHOW ENGINE shows InnoDB = DISABLED. There are relevant no errors in the .err file. Thanks for sending me your compilation options. I'll give those a go and see what happens... Regards, Ben. Logan, David (SST - Adelaide) wrote: Hi Ben, I thought the InnoDB engine was included without having to set a ./configure option. On my latest build (admittedly a 5.0.18 one) InnoDB was enabled without setting any ./configure option. My options were hambone /usr/dev/src/mysql-5.0.18 $ cat ../../build_scripts/mysql-5.0.18 #!/bin/bash ./configure \ --prefix=/usr/local/mysql-5.0.18 \ --enable-thread-safe-client \ --with-unix-socket-path=/tmp \ --with-openssl \ --with-example-storage-engine \ --with-archive-storage-engine \ --with-csv-storage-engine \ --with-blackhole-storage-engine \ --with-ndbcluster \ --with-ndb-test \ --with-ndb-port=3510 \ --with-ndb-port-base=3710 \ --with-federated-storage-engine This worked fine. If I get time later, I may give it a punt with your version. Sorry I can't be of more help. 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: Ben Clewett [mailto:[EMAIL PROTECTED] Sent: Tuesday, 23 May 2006 5:50 PM To: Logan, David (SST - Adelaide) Cc: mysql@lists.mysql.com Subject: Re: InnoDB problems under 5.1.9 Logan, David (SST - Adelaide) wrote: Hi Ben, Try doing SHOW ENGINES; Here: (pertinent cols only) ++--+--+-++ | Engine | Support | Transactions | XA | Savepoints | ++--+--+-++ | CSV| YES | NO | NO | NO | | MEMORY | YES | NO | NO | NO | | MRG_MYISAM | YES | NO | NO | NO | | InnoDB | DISABLED | YES | YES | YES| | BLACKHOLE | YES | NO | NO | NO | | MyISAM | DEFAULT | NO | NO | NO | | BerkeleyDB | DISABLED | YES | NO | YES| | ARCHIVE| YES | NO | NO | NO | ++--+--+-++ Ok, now I believe this does mean I have compiled the InnoDB. Just to save me trawling though the manual, can you tell me how I should enable InnoDB? Thanks for the info! Ben and see what it says. It should say InnoDB is supported, if not then it hasn't compiled in. 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: Ben Clewett [mailto:[EMAIL PROTECTED] Sent: Tuesday, 23 May 2006 4:57 PM To: mysql@lists.mysql.com Subject: InnoDB problems under 5.1.9 Dear MySQL, I've installed 5.1.9 from source on a SUSE 10 box. But I can't get InnoDB tables respected. I have used the correct compilation flag (--with-innodb). SHOW VARIABLES; lists all the usual innodb variables. The innodb table space has been created in ~/var/ibdata1. But if I enter: CREATE TABLE a ( a int NOT NULL PRIMARY KEY ) ENGINE=InnoDB; SHOW CREATE TABLE a; CREATE TABLE `a` ( `a` int(10) NOT NULL PRIMARY KEY ) ENGINE=MyISAM As you can see, an InnoDB has become an MyISAM and will be stored in ~/var/test/a.* I am using the large table .cnf file. Everything else is much as default. Can anybody help me? Regards, Ben -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysq
RE: InnoDB problems under 5.1.9
Hi Ben, I thought the InnoDB engine was included without having to set a ./configure option. On my latest build (admittedly a 5.0.18 one) InnoDB was enabled without setting any ./configure option. My options were hambone /usr/dev/src/mysql-5.0.18 $ cat ../../build_scripts/mysql-5.0.18 #!/bin/bash ./configure \ --prefix=/usr/local/mysql-5.0.18 \ --enable-thread-safe-client \ --with-unix-socket-path=/tmp \ --with-openssl \ --with-example-storage-engine \ --with-archive-storage-engine \ --with-csv-storage-engine \ --with-blackhole-storage-engine \ --with-ndbcluster \ --with-ndb-test \ --with-ndb-port=3510 \ --with-ndb-port-base=3710 \ --with-federated-storage-engine This worked fine. If I get time later, I may give it a punt with your version. Sorry I can't be of more help. 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: Ben Clewett [mailto:[EMAIL PROTECTED] Sent: Tuesday, 23 May 2006 5:50 PM To: Logan, David (SST - Adelaide) Cc: mysql@lists.mysql.com Subject: Re: InnoDB problems under 5.1.9 Logan, David (SST - Adelaide) wrote: > Hi Ben, > > Try doing > > SHOW ENGINES; Here: (pertinent cols only) ++--+--+-++ | Engine | Support | Transactions | XA | Savepoints | ++--+--+-++ | CSV| YES | NO | NO | NO | | MEMORY | YES | NO | NO | NO | | MRG_MYISAM | YES | NO | NO | NO | | InnoDB | DISABLED | YES | YES | YES| | BLACKHOLE | YES | NO | NO | NO | | MyISAM | DEFAULT | NO | NO | NO | | BerkeleyDB | DISABLED | YES | NO | YES| | ARCHIVE| YES | NO | NO | NO | ++--+--+-++ Ok, now I believe this does mean I have compiled the InnoDB. Just to save me trawling though the manual, can you tell me how I should enable InnoDB? Thanks for the info! Ben > > and see what it says. It should say InnoDB is supported, if not then it > hasn't compiled in. > > 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: Ben Clewett [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 23 May 2006 4:57 PM > To: mysql@lists.mysql.com > Subject: InnoDB problems under 5.1.9 > > Dear MySQL, > > I've installed 5.1.9 from source on a SUSE 10 box. But I can't get > InnoDB tables respected. > > I have used the correct compilation flag (--with-innodb). > SHOW VARIABLES; lists all the usual innodb variables. > The innodb table space has been created in ~/var/ibdata1. > > But if I enter: > > CREATE TABLE a ( >a int NOT NULL PRIMARY KEY > ) ENGINE=InnoDB; > > SHOW CREATE TABLE a; > > CREATE TABLE `a` ( >`a` int(10) NOT NULL PRIMARY KEY > ) ENGINE=MyISAM > > As you can see, an InnoDB has become an MyISAM and will be stored in > ~/var/test/a.* > > I am using the large table .cnf file. Everything else is much as > default. > > Can anybody help me? > > Regards, > > Ben > > > > > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB problems under 5.1.9
Logan, David (SST - Adelaide) wrote: Hi Ben, Try doing SHOW ENGINES; Here: (pertinent cols only) ++--+--+-++ | Engine | Support | Transactions | XA | Savepoints | ++--+--+-++ | CSV| YES | NO | NO | NO | | MEMORY | YES | NO | NO | NO | | MRG_MYISAM | YES | NO | NO | NO | | InnoDB | DISABLED | YES | YES | YES| | BLACKHOLE | YES | NO | NO | NO | | MyISAM | DEFAULT | NO | NO | NO | | BerkeleyDB | DISABLED | YES | NO | YES| | ARCHIVE| YES | NO | NO | NO | ++--+--+-++ Ok, now I believe this does mean I have compiled the InnoDB. Just to save me trawling though the manual, can you tell me how I should enable InnoDB? Thanks for the info! Ben and see what it says. It should say InnoDB is supported, if not then it hasn't compiled in. 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: Ben Clewett [mailto:[EMAIL PROTECTED] Sent: Tuesday, 23 May 2006 4:57 PM To: mysql@lists.mysql.com Subject: InnoDB problems under 5.1.9 Dear MySQL, I've installed 5.1.9 from source on a SUSE 10 box. But I can't get InnoDB tables respected. I have used the correct compilation flag (--with-innodb). SHOW VARIABLES; lists all the usual innodb variables. The innodb table space has been created in ~/var/ibdata1. But if I enter: CREATE TABLE a ( a int NOT NULL PRIMARY KEY ) ENGINE=InnoDB; SHOW CREATE TABLE a; CREATE TABLE `a` ( `a` int(10) NOT NULL PRIMARY KEY ) ENGINE=MyISAM As you can see, an InnoDB has become an MyISAM and will be stored in ~/var/test/a.* I am using the large table .cnf file. Everything else is much as default. Can anybody help me? Regards, Ben -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: InnoDB problems under 5.1.9
Hi Ben, Try doing SHOW ENGINES; and see what it says. It should say InnoDB is supported, if not then it hasn't compiled in. 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: Ben Clewett [mailto:[EMAIL PROTECTED] Sent: Tuesday, 23 May 2006 4:57 PM To: mysql@lists.mysql.com Subject: InnoDB problems under 5.1.9 Dear MySQL, I've installed 5.1.9 from source on a SUSE 10 box. But I can't get InnoDB tables respected. I have used the correct compilation flag (--with-innodb). SHOW VARIABLES; lists all the usual innodb variables. The innodb table space has been created in ~/var/ibdata1. But if I enter: CREATE TABLE a ( a int NOT NULL PRIMARY KEY ) ENGINE=InnoDB; SHOW CREATE TABLE a; CREATE TABLE `a` ( `a` int(10) NOT NULL PRIMARY KEY ) ENGINE=MyISAM As you can see, an InnoDB has become an MyISAM and will be stored in ~/var/test/a.* I am using the large table .cnf file. Everything else is much as default. Can anybody help me? Regards, Ben -- 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]
InnoDB problems under 5.1.9
Dear MySQL, I've installed 5.1.9 from source on a SUSE 10 box. But I can't get InnoDB tables respected. I have used the correct compilation flag (--with-innodb). SHOW VARIABLES; lists all the usual innodb variables. The innodb table space has been created in ~/var/ibdata1. But if I enter: CREATE TABLE a ( a int NOT NULL PRIMARY KEY ) ENGINE=InnoDB; SHOW CREATE TABLE a; CREATE TABLE `a` ( `a` int(10) NOT NULL PRIMARY KEY ) ENGINE=MyISAM As you can see, an InnoDB has become an MyISAM and will be stored in ~/var/test/a.* I am using the large table .cnf file. Everything else is much as default. Can anybody help me? Regards, Ben -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
