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:
[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
---
-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
: 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
: 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
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
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
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
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;
Hi Dan,
This is what I have. What does this mean with regards to InnoDB?
++--++--+-++
| Engine | Support | Comment
| Transactions | XA | Savepoints |
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
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
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
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
Hi,
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
Andy,
- Alkuperäinen viesti -
Lähettäjä: Andy Davidson [EMAIL PROTECTED]
Vastaanottaja: Heikki Tuuri [EMAIL PROTECTED]
Lähetetty: Tuesday, January 04, 2005 5:02 PM
Aihe: Re: BIG InnoDB problems!
...¨
On Mon, 3 Jan 2005, Heikki Tuuri wrote:
the problem you had was serious corruption
A few days ago I did the following:
Turned off MySQL. Installed 4.1.8a, then I went into the directory
where all of the database files are located. I moved everything
having to do with INNODB tables and logs into another location for
safekeeping. Then I started up the new version of MySQL.
I
InnoDB problems!
Greetings Heikki and Happy New Year!
Here's what I got. I hope it's useful.
beech:/home/jfreeman # resolve_stack_dump -s /tmp/mysqld.sym -n
mysqld.stack
0x815f0cf handle_segfault + 575
0xe420 _end + -138916432
0x82e71d5 buf_read_page + 165
0x82e71d5 buf_read_page + 165
[EMAIL PROTECTED]
Vastaanottaja: Heikki Tuuri [EMAIL PROTECTED]
Kopio: mysql@lists.mysql.com
Lähetetty: Friday, December 31, 2004 5:21 PM
Aihe: Re: BIG InnoDB problems!
Greetings Heikki and Happy New Year!
Here's what I got. I hope it's useful.
beech:/home/jfreeman
.
Regards,
Heikki
- Alkuperäinen viesti -
Lähettäjä: jsf [EMAIL PROTECTED]
Vastaanottaja: Heikki Tuuri [EMAIL PROTECTED]
Kopio: mysql@lists.mysql.com
Lähetetty: Monday, January 03, 2005 4:31 PM
Aihe: Re: BIG InnoDB problems!
Hi Heikki,
Please see below...
On Mon, 3 Jan 2005 15:14:12 +0200, Heikki
, 2005 4:31 PM
Aihe: Re: BIG InnoDB problems!
Hi Heikki,
Please see below...
On Mon, 3 Jan 2005 15:14:12 +0200, Heikki Tuuri [EMAIL PROTECTED]
wrote:
Joshua,
the stack trace below shows that you are trying to drop a database? Why?
At that point, I'd heard from our developer of so
]
Kopio: mysql@lists.mysql.com
Lähetetty: Monday, January 03, 2005 4:56 PM
Aihe: Re: BIG InnoDB problems!
well, since we were having so many problems with the InnoDB tables, we
created a non-InnoDB version of the database in question...
Basically we want to do whatever it will take to get InnoDB tables
up MyISAM
tables
http://www.innodb.com/order.php
Order MySQL technical support from https://order.mysql.com/
- Original Message -
From: jsf [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Friday, December 31, 2004 12:26 AM
Subject: BIG InnoDB problems!
I've been
I've been struggling with this problem for the last few days. I've
enlisted the help of some colleagues on the NYLUG (NY Linux User's
Group) list but finally we figured this is the best place to look for
some help.
We have a server running SLES 9.0 (SuSE Linux Enterprise Server 9.0) and:
It looks like your tablespace is corrupt. Check this doc out:
http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
On Thu, 30 Dec 2004 17:21:40 -0500, jsf [EMAIL PROTECTED] wrote:
I've been struggling with this problem for the last few days. I've
enlisted the help of some colleagues on
Thanks Eric,
We already tried levels 1, 3 and 5...
no soap. I'm on the verge of thinking it's a bug.
:-(
J.
On Fri, 31 Dec 2004 00:06:28 +, Eric Bergen [EMAIL PROTECTED] wrote:
It looks like your tablespace is corrupt. Check this doc out:
Order MySQL technical support from https://order.mysql.com/
- Original Message -
From: jsf [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Friday, December 31, 2004 12:26 AM
Subject: BIG InnoDB problems!
I've been struggling with this problem for the last few days. I've
DESCRIPTION:
Mysqld appears to crash every few days or so. The .err file shows
that it may be an innodb problem. (See below for detail)
How-To-Repeat
I am not able to repeat the problem. The query that runs when the
mysqld server dies, is automatically re-run when the server comes back
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
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
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
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
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]
.
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
. 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
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
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'.
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
38 matches
Mail list logo
