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 disable
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 InnoD
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 messa
Hi Dan,
This is what I have. What does this mean with regards to InnoDB?
++--++--+-++
| Engine | Support | Comment
| Transactions | XA | Savepoints |
+---
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 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 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
TED]
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)
++--+--+-+
t: Re: InnoDB problems under 5.1.9
Logan, David (SST - Adelaide) wrote:
> Hi Ben,
>
> Try doing
>
> SHOW ENGINES;
Here: (pertinent cols only)
++--+--+-++
| Engine | Support | Transaction
Logan, David (SST - Adelaide) wrote:
Hi Ben,
Try doing
SHOW ENGINES;
Here: (pertinent cols only)
++--+--+-++
| Engine | Support | Transactions | XA | Savepoints |
++--+--+-++
| CSV|
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 -
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
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.
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 followi
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
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
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
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
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 su
20 matches
Mail list logo
