subject:"Re\: Innodb problems"

Re: InnoDB problems under 5.1.9

2006-05-23 Thread Ben Clewett


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

2006-05-23 Thread Ben Clewett


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

2006-05-23 Thread Dan Buettner

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

2006-05-23 Thread Ben Clewett


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

2006-05-23 Thread Dan Buettner

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

2006-05-23 Thread Ben Clewett


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

2006-05-23 Thread Ben Clewett


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

2006-05-23 Thread gerald_clark


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

2006-05-23 Thread Ben Clewett


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

2006-05-23 Thread Logan, David (SST - Adelaide)

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

2006-05-23 Thread Ben Clewett


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

2006-05-23 Thread Logan, David (SST - Adelaide)

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]

Re: InnoDB problems ...

2005-03-31 Thread Ware Adams

On Mar 31, 2005, at 1:13 AM, Rafal Kedziorski wrote:
I'm working with JBoss and MySQL 4.0.22 (and 4.0.18 on Testsystem). 
But under the load, I get sometimes Exceptions like this:

java.sql.SQLException: Deadlock found when trying to get lock; Try 
restarting transaction message from server: "Lock wait timeout 
exceeded; Try restarting transaction"

It looks like InnoDB problem. Is there a way to find out why this 
happens?
InnoDB has detected a deadlock, which is described pretty well in the 
InnoDB manual (at innodb.com or the mysql.com version of the manual).

When this happens run
show innodb status\G
from the command line client.  InnoDB will print out status info, and 
at the top will be details of the last detected deadlock which will 
show the conflicting queries.  You then need to modify the queries or 
the application so it doesn't happen.

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

Re: InnoDB problems with 4.0.18-max

2004-04-06 Thread Heikki Tuuri

Rick,

- Original Message - 
From: "Rick Ellis" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, April 01, 2004 11:27 AM
Subject: InnoDB problems with 4.0.18-max


> Hi Guys,
>
> We are currently using MySQL as the backend to the RT Request Tracker
> Ticketing system. The problem is that we are seeing total data loss from
> the InnoDB after a proper shutdown of the database using mysqladmin
> shutdown.
>
> We have observed this once on a Sparc Enterprise 420R with 4 CPU's and 4
> gigs of RAM, using the my-large.cnf as a template and Solaris 9, but we
> see this most often on mysql 4.0-18-max running on a Enterprise 220R
> with 2 CPU's and 2 gigs of ram, based on my-small.cnf and Solaris 8.
>
> Both setups are using perl 5.8.3 and the latest Apache 3 release.
>
> On restarting the Mysql server, (which serves a number of other
> application, not using InnoDB perfectly) we cannot log in. Going into
> Mysql itself, and use rt3; it complains that most of the tables are
> blank. See extract below from the .err log file:
>
>
> 040310  7:03:37  /usr/local/mysql/bin/mysqld: Normal shutdown
>
> 040310  7:03:38  InnoDB: Starting shutdown...
> 040310  7:03:42  InnoDB: Shutdown completed
> 040310  7:03:42  /usr/local/mysql/bin/mysqld: Shutdown Complete
>
> 040310 07:04:06  mysqld started
> 040310  7:04:07  InnoDB: Database was not shut down normally.
> InnoDB: Starting recovery from log files...
> InnoDB: Starting log scan based on checkpoint at
> InnoDB: log sequence number 0 2488475
> InnoDB: Doing recovery: scanned up to log sequence number 0 2488475
> 040310  7:04:07  InnoDB: Flushing modified pages from the buffer pool...
> 040310  7:04:07  InnoDB: Started
> /export/mysql4/bin/mysqld: ready for connections.
> Version: '4.0.18-max'  socket: '/tmp/mysql.sock'  port: 3306
> 040310  7:05:41  InnoDB error:
> Cannot find table rt3/Users from the internal data dictionary
> of InnoDB though the .frm file for the table exists. Maybe you
> have deleted and recreated InnoDB data files but have forgotten
> to delete the corresponding .frm files of InnoDB tables, or you
> have moved .frm files to another database?
> Look from section 15.1 of http://www.innodb.com/ibman.html
> how you can resolve the problem.
> 040310  7:05:41  InnoDB error:
> Cannot find table rt3/Users from the internal data dictionary
> of InnoDB though the .frm file for the table exists. Maybe you
> have deleted and recreated InnoDB data files but have forgotten
> to delete the corresponding .frm files of InnoDB tables, or you
> have moved .frm files to another database?
> Look from section 15.1 of http://www.innodb.com/ibman.html
> how you can resolve the problem.
> 040310  7:05:41  InnoDB error:
> Cannot find table rt3/Users from the internal data dictionary
> of InnoDB though the .frm file for the table exists. Maybe you
> have deleted and recreated InnoDB data files but have forgotten
> to delete the corresponding .frm files of InnoDB tables, or you
> have moved .frm files to another database?
> Look from section 15.1 of http://www.innodb.com/ibman.html
> how you can resolve the problem.
> 040310  7:05:41  InnoDB error:
> Cannot find table rt3/Users from the internal data dictionary
> of InnoDB though the .frm file for the table exists. Maybe you
> have deleted and recreated InnoDB data files but have forgotten
> to delete the corresponding .frm files of InnoDB tables, or you
> have moved .frm files to another database?
> Look from section 15.1 of http://www.innodb.com/ibman.html
> how you can resolve the problem.
> 040310  7:05:41  InnoDB error:
> Cannot find table rt3/Users from the internal data dictionary
> of InnoDB though the .frm file for the table exists. Maybe you
> have deleted and recreated InnoDB data files but have forgotten
> to delete the corresponding .frm files of InnoDB tables, or you
> have moved .frm files to another database?
> Look from section 15.1 of http://www.innodb.com/ibman.html
> how you can resolve the problem.
>
> Settings from the worst affected system' my.cnf file are:
>
> # Uncomment the following if you are using InnoDB tables
> innodb_data_home_dir = /usr/local/mysql/data/
> innodb_data_file_path = ibdata1:10M:autoextend
> innodb_log_group_home_dir = /usr/local/mysql/data/
> innodb_log_arch_dir = /usr/local/mysql/data/
> # You can set .._buffer_pool_size up to 50 - 80 %
> # of RAM but beware of setting memory usage too high
> set-variable = innodb_buffer_pool_size=32M
> set-variable = innodb_additional_mem_pool_size=2M
> # Set .._log_file_size to 25 % of buffer pool size
> set-variable = innodb_log_file_size=5M
> set-variable = innodb_log_buffer_size=8M
> innodb_flush_log_at_trx_commit=1
> set-variable = innodb_lock_wait_timeout=50
> #set-variable = innodb_force_recovery=4
>
> We are doing an sqldump every hour and before any shutdowns now, because
> we can't guarantee that the database will come back up.
>
> If anyone can spot the problem or suggest a course of action to debug
> the iss

Re: InnoDb Problems

2003-02-07 Thread Stefan Hinz

Davy,

DO> I have been trying to get InnoDb to run on my windows XP machine.
DO> (...)
DO> #innodb_data_home_dir =
DO> #innodb_log_group_home_dir =
DO> #innodb_data_file_path = /ibdata/ibdata1:10M:autoextend

The remarks are in German, but I guess you will know what to do if
you look at the following excerpt from my my.ini file on a Win2K
machine:

# InnoDB
# Speicherort fuer Tablespaces (Vorgabe: DATADIR)
innodb_data_home_dir=c:\mysql\innodb
# Vorgabemaessig wird ab MySQL 4.0
#  ein 64 MB grosser Tablespace namens ibdata1
#  (per Vorgabe in DATADIR) angelegt.
#  Folgende Einstellungen ueberschreiben diesen Wert.
innodb_data_file_path = ibdata1:100M;ibdata2:100M
# Speicherort fuer Logdateien
innodb_log_group_home_dir=c:\mysql\innodb
innodb_log_arch_dir = c:\mysql\innodb
# Logarchivierung anschalten (1) oder abschalten (0)
innodb_log_archive=0
# Einstellungen fuer Logdateien
# set-variable = innodb_mirrored_log_groups=1
# set-variable = innodb_log_files_in_group=3
set-variable = innodb_log_file_size=5M
set-variable = innodb_log_buffer_size=8M
# Puffer-Poolgroesse auf 50% bis 80%
# des Arbeitsspeichers Ihres Computers setzen
set-variable = innodb_buffer_pool_size=70M
set-variable = innodb_additional_mem_pool_size=10M
# Transaktionen immer sicher (1) oder nicht (0)
innodb_flush_log_at_trx_commit=1
set-variable = innodb_file_io_threads=4
set-variable = innodb_lock_wait_timeout=50

Regards,
--
  Stefan Hinz <[EMAIL PROTECTED]>
  iConnect GmbH 
  Heesestr. 6, 12169 Berlin (Germany)
  Telefon: +49 30 7970948-0  Fax: +49 30 7970948-3


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: InnoDb Problems

2003-02-06 Thread Natale Babbo

i see that you don't specify any path for
innodb_data_home_dir, innodb_log_group_home_dir and 
innodb_data_file_path  ... write down the correct path
and retry.

regards.



 --- Davy Obdam <[EMAIL PROTECTED]> ha scritto: > Hi
People,
> 
> I have been trying to get InnoDb to run on my
> windows XP machine. I have 
> MySQL 3.23.55 installed and i am running the
> mysqld-max-nt server. I 
> have added the following lines to my my.ini file:
> (note the # because i 
> didnt get it to work, i dissabled it)
> [mysqld]
> 
> .
> #innodb_data_home_dir =
> #innodb_log_group_home_dir =
> #innodb_data_file_path =
> /ibdata/ibdata1:10M:autoextend
> 
> When i start my MySQL server with this config, i get
> and error and the 
> server wont start. What am i doing wrong here?? Any
> help is appreciated, 
> thanks for your time.
> 
> Best regards,
> 
> Davy Obdam
> mailto:[EMAIL PROTECTED]
> 
> -- 
>

> Davy Obdam - Obdam webdesign©
> mailto:[EMAIL PROTECTED]   web: www.davyobdam.com
>

> 
> 
> 
> 
>
-
> Before posting, please check:
>http://www.mysql.com/manual.php   (the manual)
>http://lists.mysql.com/   (the list
> archive)
> 
> To request this thread, e-mail
> <[EMAIL PROTECTED]>
> To unsubscribe, e-mail
>
<[EMAIL PROTECTED]>
> Trouble unsubscribing? Try:
> http://lists.mysql.com/php/unsubscribe.php
>  

__
Yahoo! Cellulari: loghi, suonerie, picture message per il tuo telefonino
http://it.yahoo.com/mail_it/foot/?http://it.mobile.yahoo.com/index2002.html

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: Innodb problems

2002-03-06 Thread Heikki Tuuri


Wendell,

InnoDB writes a checksum to a database page when it is written to disk. If
the checksum does not correspond to the page contents when the page is read
back in, you get the below error. Below page 36819 in table
registrydb_tn/TBL_AllNames appears to be corrupt, like it says. The checksum
is 0, which does not correspond to page contents.

When you encounter this kind of error, the first thing to try is rebooting
the computer, like it says below. Next you can try dumping, dropping, and
reimporting the corrupt table. The last resort is to recover from a backup.

>020306 09:01:16  mysqld restarted
>020306  9:01:16  Can't start server: Bind on TCP/IP port: Address already
in
>use
>020306  9:01:16  Do you already have another mysqld server running on port:
>3306 ?

The last error you got was probably that Linux had not killed the entire
mysqld process though mysqld had called exit(1). Then you should look with
ps -A what processes are running, and kill -9 them manually.

Please send me all error messages and hex dumps you have, from both servers.
What version you are running?

Linux kernels 2.2 -2.5 seem to have bugs in the i/o system, especially in
connection with RAID disks. But let us look first at the hex files.

Regards,

Heikki

-Original Message-
From: "Wendell Dingus" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Date: Thursday, March 07, 2002 6:16 AM
Subject: Innodb problems


>I've been using MyISAM tables for a long time on a lot of machines and
>(knock on wood) have basically never had a problem. Now though on a larger
>server I decided we should use INNODB tables and am having problems. I
>didn't realize until today that it's been 'crashing' and recovering
>repeatedly for the past few weeks. Today it died though and could not
repair
>itself. Since I'm doing replication to a second server I just copied
>databases from the backup server to the primary and got things back going.
>Looking at the log files on the second/backup server it has the same type
of
>errors in the log file though. Not bad hardware unless both (identical)
>servers have the same bad hardware.
>
>Here's where it crashed and dumped a heck of a lot of hex data into the log
>file:
>
>..;Inno
D
>B: End of page dump
>InnoDB: Page checksum 1558702454 stored checksum 0
>InnoDB: Page lsn 4 226263974, low 4 bytes of lsn at page end 0
>InnoDB: Page may be an index page where index id is 0 565
>InnoDB: Database page corruption or a failed
>InnoDB: file read of page 36819.
>InnoDB: You may have to recover from a backup.
>InnoDB: It is also possible that your operating
>InnoDB: system has corrupted its own file cache
>InnoDB: and rebooting your computer removes the
>InnoDB: error.
>
>Number of processes running now: 0
>020306 08:55:21  mysqld restarted
>020306  8:55:25  InnoDB: Database was not shut down normally.
>InnoDB: Starting recovery from log files...
>InnoDB: Starting log scan based on checkpoint at
>InnoDB: log sequence number 4 229089185
>InnoDB: Last MySQL binlog file offset 0 465620, file name ./shelby1-bin.001
>020306  8:55:26  InnoDB: Flushing modified pages from the buffer pool...
>020306  8:55:26  InnoDB: Started
>/usr/sbin/mysqld-max: ready for connections
>InnoDB: Database page corruption or a failed
>InnoDB: file read of page 36819.
>InnoDB: You may have to recover from a backup.
>InnoDB: Page dump in ascii and hex (16384 bytes):
> len 16384; hex 8fd30005851f00058
>
>
>Here's where it gave up the ghost entirely:
>
>..;Inno
D
>B: End of page dump
>InnoDB: Page checksum 1558702454 stored checksum 0
>InnoDB: Page lsn 4 226263974, low 4 bytes of lsn at page end 0
>InnoDB: Page may be an index page where index id is 0 565
>InnoDB: and table registrydb_tn/TBL_AllNames index LastName
>InnoDB: Database page corruption or a failed
>InnoDB: file read of page 36819.
>InnoDB: You may have to recover from a backup.
>InnoDB: It is also possible that your operating
>InnoDB: system has corrupted its own file cache
>InnoDB: and rebooting your computer removes the
>InnoDB: error.
>
>Number of processes running now: 0
>020306 09:01:16  mysqld restarted
>020306  9:01:16  Can't start server: Bind on TCP/IP port: Address already
in
>use
>020306  9:01:16  Do you already have another mysqld server running on port:
>3306 ?
>020306  9:01:16  Aborting
>
>020306  9:01:16  /usr/sbin/mysqld-max: Shutdown Complete
>
>020306 09:01:16  mysqld ended
>
>
>Here's the my.cnf file:
>
>[mysqld]
>datadir=/var/lib/mysql
>socket=/var/lib/mysql/mysql.sock
>log-bin
>server-id=1
>
>default-table-type=innodb
>innodb_data_file_path =
>ibdata1:2000M;ibdata2:2000M;ibdata3:2000M;ibdata4:2000M;ibdata5:2000M;ibdat
a
>6:2000M
>innodb_data_home_dir = /var/lib/innodb/
>set-variable = innodb_mirrored_log_groups=1
>innodb_log_group_home_dir = /var/lib/iblogs
>set-variable = innodb_log_files_in_group=3
>set-vari

Re: InnoDB problems

2001-09-10 Thread Nuno Dias


On Mon, Sep 10, 2001 at 02:28:05PM +0300, Heikki Tuuri wrote:
> Nuno,
> 
> I noticed a similar unexplained restriction
> on our Linux 2.4. We have 512 MB physical memory,
> no swap partition, and for some reason I cannot
> malloc more than 256 MB. The Unix errno just says
> 'Cannot allocate memory'.
> 
> On our other machine with 900 MB RAM and 512 MB swap
> I can malloc 900 MB.
> 
> What is your my.cnf like? Is it possible that you
> have allocated so much memory to PostgreSQL, MyISAM,
> and other programs that the 2 GB or 3 GB you have is
> almost totally used?

Here's my.cnf:

[mysqld]
innodb_data_file_path = data/data1:2000M;data/data2:2000M
innodb_data_home_dir = /servers/mysql/
set-variable = innodb_mirrored_log_groups=1
innodb_log_group_home_dir = /servers/mysql/data/logs/
set-variable = innodb_log_files_in_group=3
set-variable = innodb_log_file_size=50M
set-variable = innodb_log_buffer_size=20M 
innodb_flush_log_at_trx_commit=0
innodb_log_arch_dir = /servers/mysql/data/logs/
innodb_log_archive=0
set-variable = innodb_buffer_pool_size=50M 
set-variable = innodb_additional_mem_pool_size=20M
set-variable = innodb_file_io_threads=4
set-variable = innodb_lock_wait_timeout=50
innodb_flush_method=O_DSYNC


This problem arose before the installation of PostGres. Even then I could not reserve 
more than 50M for innodb_buffer_pool_size.
The only thing that is also running on the machine is a HTTP server that uses at most 
60M of mem.


> 
> At 10:55 AM 9/10/01 +0100, you wrote:
> >On Fri, Sep 07, 2001 at 08:47:16PM +0300, Heikki Tuuri wrote:
> >> Nuno,
> >> 
> >> what does
> >> 
> >> ulimit -a
> >> 
> >> say (assuming you are running on Unix)?
> >> ulimit tells the limits set for the user.
> >> I think there are also hard limits decided
> >> at kernel compile time.
> >
> >core file size (blocks)  0
> >data seg size (kbytes)   unlimited
> >file size (blocks)   unlimited
> >max memory size (kbytes) unlimited
> >stack size (kbytes)  8192
> >cpu time (seconds)   unlimited
> >max user processes   256
> >pipe size (512 bytes)8
> >open files   1024
> >virtual memory (kbytes)  2105343
> >
> >I'm running Linux.
> >
> >> 
> >> What does
> >> 
> >> free
> >> 
> >> say?
> >> 
> >
> > total   used   free sharedbuffers cached
> >Mem:   20967202094180   2540  01073620 786400
> >-/+ buffers/cache: 2341601862560
> >Swap:  1052248   32921048956
> >
> >
> >But I'm running two SQL servers (MySQL and PostGres) and I'm running some
> scripts. Apart from that, the machine is totally dedicated to SQL stuff.
> >When installing InnoDB I should have most of the memory available.
> >
> >
> >> Regards,
> >> 
> >> Heikki
> >> http://www.innodb.com
> >> 
> >> >Nuno Dias wrote:
> >> > 
> >> >> I installed mysql with innodb support on a machine with 2G of RAM.> 
> >> >> The manual recommends that one should set innodb_buffer_pool_size in
> >> my.cnf to 
> >> >up to 80% of the physical memory available.
> >> > 
> >> >> However, if I set a value above 50M!!! I get this error:
> >> > 
> >> >> Innobase: Fatal error: cannot allocate memory!
> >> >> Innobase: Cannot continue operation!
> >> >> Innobase: Check if you can increase the swap file of your
> >> >> Innobase: operating system.
> >> > 010906 15:31:27  mysqld ended
> >> > 
> >> >> Anyone as any clue about this?
> >> > > --> Nuno Dias <[EMAIL PROTECTED]>
> >> >> Novis - Dir. Rede - ISP 
> >> >> Ed. Atrium Saldanha - Pça. Dq. de Saldanha, 1, 7o / 1050 - 094 Lisboa
> >> >> tel: +351 21 0104437 - fax: +351 21 0104301> 
> >> >> I may not be able to walk, but I drive from a sitting position.
> >> 
> >> 
> >> 
> >> -
> >> Before posting, please check:
> >>http://www.mysql.com/manual.php   (the manual)
> >>http://lists.mysql.com/   (the list archive)
> >> 
> >> To request this thread, e-mail <[EMAIL PROTECTED]>
> >> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> >> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
> >> 
> >
> >-- 
> >Nuno Dias <[EMAIL PROTECTED]>
> >Novis - Dir. Rede - ISP  
> >Ed. Atrium Saldanha - Pça. Dq. de Saldanha, 1, 7o / 1050 - 094 Lisboa
> >tel: +351 21 0104437 - fax: +351 21 0104301
> >
> >
> >Brandy Davis, an outfielder and teammate of mine with the Pittsburgh Pirates,
> >is my choice for team captain.  Cincinnatti was beating us 3-1, and I led
> >off the bottom of the eighth with a walk.  The next hitter banged a hard
> >single to right field.  Feeling the wind at my back, I rounded second and
> >kept going, sliding safely into third base.
> > With runners at first and third, and home-run hitter Ralph Kiner at
> >bat, our manager put in the fast Brandy Davis to run for the player at first.
> >Even with Kiner hitting and a change to win the game with a home run, Brandy
> >took off for second and made it.  Now w

Re: InnoDB problems

2001-09-10 Thread Heikki Tuuri


Nuno,

I noticed a similar unexplained restriction
on our Linux 2.4. We have 512 MB physical memory,
no swap partition, and for some reason I cannot
malloc more than 256 MB. The Unix errno just says
'Cannot allocate memory'.

On our other machine with 900 MB RAM and 512 MB swap
I can malloc 900 MB.

What is your my.cnf like? Is it possible that you
have allocated so much memory to PostgreSQL, MyISAM,
and other programs that the 2 GB or 3 GB you have is
almost totally used?

Regards,

Heikki

At 10:55 AM 9/10/01 +0100, you wrote:
>On Fri, Sep 07, 2001 at 08:47:16PM +0300, Heikki Tuuri wrote:
>> Nuno,
>> 
>> what does
>> 
>> ulimit -a
>> 
>> say (assuming you are running on Unix)?
>> ulimit tells the limits set for the user.
>> I think there are also hard limits decided
>> at kernel compile time.
>
>core file size (blocks)  0
>data seg size (kbytes)   unlimited
>file size (blocks)   unlimited
>max memory size (kbytes) unlimited
>stack size (kbytes)  8192
>cpu time (seconds)   unlimited
>max user processes   256
>pipe size (512 bytes)8
>open files   1024
>virtual memory (kbytes)  2105343
>
>I'm running Linux.
>
>> 
>> What does
>> 
>> free
>> 
>> say?
>> 
>
> total   used   free sharedbuffers cached
>Mem:   20967202094180   2540  01073620 786400
>-/+ buffers/cache: 2341601862560
>Swap:  1052248   32921048956
>
>
>But I'm running two SQL servers (MySQL and PostGres) and I'm running some
scripts. Apart from that, the machine is totally dedicated to SQL stuff.
>When installing InnoDB I should have most of the memory available.
>
>
>> Regards,
>> 
>> Heikki
>> http://www.innodb.com
>> 
>> >Nuno Dias wrote:
>> > 
>> >> I installed mysql with innodb support on a machine with 2G of RAM.> 
>> >> The manual recommends that one should set innodb_buffer_pool_size in
>> my.cnf to 
>> >up to 80% of the physical memory available.
>> > 
>> >> However, if I set a value above 50M!!! I get this error:
>> > 
>> >> Innobase: Fatal error: cannot allocate memory!
>> >> Innobase: Cannot continue operation!
>> >> Innobase: Check if you can increase the swap file of your
>> >> Innobase: operating system.
>> > 010906 15:31:27  mysqld ended
>> > 
>> >> Anyone as any clue about this?
>> > > --> Nuno Dias <[EMAIL PROTECTED]>
>> >> Novis - Dir. Rede - ISP 
>> >> Ed. Atrium Saldanha - Pça. Dq. de Saldanha, 1, 7o / 1050 - 094 Lisboa
>> >> tel: +351 21 0104437 - fax: +351 21 0104301> 
>> >> I may not be able to walk, but I drive from a sitting position.
>> 
>> 
>> 
>> -
>> Before posting, please check:
>>http://www.mysql.com/manual.php   (the manual)
>>http://lists.mysql.com/   (the list archive)
>> 
>> To request this thread, e-mail <[EMAIL PROTECTED]>
>> To unsubscribe, e-mail <[EMAIL PROTECTED]>
>> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>> 
>
>-- 
>Nuno Dias <[EMAIL PROTECTED]>
>Novis - Dir. Rede - ISP  
>Ed. Atrium Saldanha - Pça. Dq. de Saldanha, 1, 7o / 1050 - 094 Lisboa
>tel: +351 21 0104437 - fax: +351 21 0104301
>
>
>Brandy Davis, an outfielder and teammate of mine with the Pittsburgh Pirates,
>is my choice for team captain.  Cincinnatti was beating us 3-1, and I led
>off the bottom of the eighth with a walk.  The next hitter banged a hard
>single to right field.  Feeling the wind at my back, I rounded second and
>kept going, sliding safely into third base.
>   With runners at first and third, and home-run hitter Ralph Kiner at
>bat, our manager put in the fast Brandy Davis to run for the player at first.
>Even with Kiner hitting and a change to win the game with a home run, Brandy
>took off for second and made it.  Now we had runners at second and third.
>   I'm standing at third, knowing I'm not going anywhere, and see Brandy
>start to take a lead.  All of a sudden, here he comes.  He makes a great slide
>into third, and I scream, "Brandy, where are you going?"  He looks up, and
>shouts, "Back to second if I can make it."
>   -- Joe Garagiola, "It's Anybody's Ball Game"
>



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: InnoDB problems

2001-09-07 Thread Heikki Tuuri


Nuno,

what does

ulimit -a

say (assuming you are running on Unix)?
ulimit tells the limits set for the user.
I think there are also hard limits decided
at kernel compile time.

What does

free

say?

Regards,

Heikki
http://www.innodb.com

>Nuno Dias wrote:
> 
>> I installed mysql with innodb support on a machine with 2G of RAM.> 
>> The manual recommends that one should set innodb_buffer_pool_size in
my.cnf to 
>up to 80% of the physical memory available.
> 
>> However, if I set a value above 50M!!! I get this error:
> 
>> Innobase: Fatal error: cannot allocate memory!
>> Innobase: Cannot continue operation!
>> Innobase: Check if you can increase the swap file of your
>> Innobase: operating system.
> 010906 15:31:27  mysqld ended
> 
>> Anyone as any clue about this?
> > --> Nuno Dias <[EMAIL PROTECTED]>
>> Novis - Dir. Rede - ISP 
>> Ed. Atrium Saldanha - Pça. Dq. de Saldanha, 1, 7o / 1050 - 094 Lisboa
>> tel: +351 21 0104437 - fax: +351 21 0104301> 
>> I may not be able to walk, but I drive from a sitting position.



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Re: InnoDB problems under 5.1.9

Re: InnoDB problems under 5.1.9

Re: InnoDB problems under 5.1.9

Re: InnoDB problems under 5.1.9

Re: InnoDB problems under 5.1.9

Re: InnoDB problems under 5.1.9

Re: InnoDB problems under 5.1.9

Re: InnoDB problems under 5.1.9

Re: InnoDB problems under 5.1.9

RE: InnoDB problems under 5.1.9

Re: InnoDB problems under 5.1.9

RE: InnoDB problems under 5.1.9

Re: InnoDB problems ...

Re: InnoDB problems with 4.0.18-max

Re: InnoDb Problems

Re: InnoDb Problems

Re: Innodb problems

Re: InnoDB problems

Re: InnoDB problems

Re: InnoDB problems

20 matches

Site Navigation

Mail list logo

Footer information