Re: Got error 139 from storage engine (InnoDB)

Hi Joerg, Thanks for your reply. I found out that this error was limitation row length of 8000 bytes on InnoDB. I have check the dump sql file and one particular table is causing error 139. What I did is just to use MyISAM engine rather than InnoDB for a specific table only. BTW, the machine

Re: Got error 139 from storage engine (InnoDB)

James, all, James Corteciano wrote: > Hi All, > > I have received error message "ERROR 1030 (HY000) at line 167: Got error 139 > from storage engine" when importing dump database to MySQL server. The MySQL > server is using InnoDB. I have google it and it's someth

Re: Got error 139 from storage engine (InnoDB)

On Mon, Jul 5, 2010 at 9:06 AM, Rob Wultsch wrote: > On Sun, Jul 4, 2010 at 8:35 PM, James Corteciano > wrote: >> Hi All, >> >> I have received error message "ERROR 1030 (HY000) at line 167: Got error 139 >> from storage engine" when importing dump datab

Re: Got error 139 from storage engine (InnoDB)

ource and restore ie target are of different versions . Thanks, On Mon, Jul 5, 2010 at 9:36 PM, Rob Wultsch wrote: > On Sun, Jul 4, 2010 at 8:35 PM, James Corteciano > wrote: > > Hi All, > > > > I have received error message "ERROR 1030 (HY000) at line 167: Got e

Re: Got error 139 from storage engine (InnoDB)

On Sun, Jul 4, 2010 at 8:35 PM, James Corteciano wrote: > Hi All, > > I have received error message "ERROR 1030 (HY000) at line 167: Got error 139 > from storage engine" when importing dump database to MySQL server. The MySQL > server is using InnoDB. I have google it a

Got error 139 from storage engine (InnoDB)

Hi All, I have received error message "ERROR 1030 (HY000) at line 167: Got error 139 from storage engine" when importing dump database to MySQL server. The MySQL server is using InnoDB. I have google it and it's something problem on exceeding a row-length limit in the InnoDB table.

Re: Error: "Got error 139 from storage engine"

I was running the 'perror' command from the bash command line of a Linux system. That explains it. This is a Windows server, not Linux. A column of type text will allow a maximum of 65'535 characters being stored, but this could be less when a multibyte character set is used. Not using a mu

Re: Error: "Got error 139 from storage engine"

On Tue, 4 Nov 2008, Jesse wrote: > > prompt> perror 139 > > MySQL error code 139: Too big row > > > > Seems you are exceeding some limit. > > Where did you run the "perror" command from? I tried to run that in the > MySQL command line utility and got an error? > > At any rate, the field in que

Re: Error: "Got error 139 from storage engine"

prompt> perror 139 MySQL error code 139: Too big row Seems you are exceeding some limit. Where did you run the "perror" command from? I tried to run that in the MySQL command line utility and got an error? At any rate, the field in question is a Text field. My understanding is that the li

Re: Error: "Got error 139 from storage engine"

ags. When > it tries to save the text to the table in the database, I get the error, > "#HY000Got error 139 from storage engine". Does anyone know what this is and > how to fix it? prompt> perror 139 MySQL error code 139: Too big row Seems you are exceeding some limit

Error: "Got error 139 from storage engine"

the database, I get the error, "#HY000Got error 139 from storage engine". Does anyone know what this is and how to fix it? Thanks, Jesse -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Innodb dealing with blobs in 4.1: Error 139 from storage engine

sorry for this monologue-thread, but... Nico Sabbi wrote: [snip] If it can help, seems that the largest value I can store in a blob field without triggering that error is 192 characters long. I just read the restrictions on Innodb tables, and I'm not convinced that what is going on is expe

Re: Innodb dealing with blobs in 4.1: Error 139 from storage engine

Nico Sabbi wrote: Hi, with mysql 4.1[234], importing a dump of Innodb tables containing at least a blob field I invariably get_ ERROR 1030 (HY000) at line 21027: Got error 139 from storage engine I read in the bugzilla that this problem is due to low memory conditions, but surely it'

Innodb dealing with blobs in 4.1: Error 139 from storage engine

Hi, with mysql 4.1[234], importing a dump of Innodb tables containing at least a blob field I invariably get_ ERROR 1030 (HY000) at line 21027: Got error 139 from storage engine I read in the bugzilla that this problem is due to low memory conditions, but surely it's not my case: the s

Inserting long text gives Error 139

Hi there, I've encountered a problem trying to insert large strings into a MySQL database. I'm running mysql Ver 11.15 Distrib 3.23.39, for dec-osf4.0f The details follow. Round 1: When I tried to insert very long text strings into a LONGTEXT column of a MyISAM table I was getting errors tha

Re: Error 139

Hi! >I received a table handler error 139 on several occasions while trying >to convert a table to type InnoDB (alter table data type=InnoDB). I >ran a check table and optimize table on it, and converted it from >MyISAM to BDB successfully. Today, when I tried it again to get

Error 139

I received a table handler error 139 on several occasions while trying to convert a table to type InnoDB (alter table data type=InnoDB). I ran a check table and optimize table on it, and converted it from MyISAM to BDB successfully. Today, when I tried it again to get the exact error

Re: [Got error 139 from table handler using InnoDB]

itch to InnoDB because > some table files (*.MYD) are approaching the OS limit. You can use the special RAID table type to overcome that. > I get the above error (139) when trying to enter a moderately sized > (~ 23k) into a text column. This error also occurs on sparc running > Solari

Re: [Got error 139 from table handler using InnoDB]

Heikki, I've downloaded the latest InnoDB (3.23.40b) and recompiled mysql 3.23.40. Unfortunately I'm still getting the same error. Do I still need to increase UNIV_PAGE_SIZE and UNIV_PAGE_SIZE_SHIFT in /path/to/mysql/innobase/include/univ.i? If so, how large can I set these values? (I increased

[Got error 139 from table handler using InnoDB]

it. I get the above error (139) when trying to enter a moderately sized (~ 23k) into a text column. This error also occurs on sparc running Solaris 2.5. I have increased max_allowed_packet as well as net_buffer_length with no change. Has anyone else experienced this? Is there a workaround?

Re: [Got error 139 from table handler using InnoDB]

My mistake. The latest InnoDB works as expected. Sorry to clutter the list with my own lack of attention. Never compile the same code on 2 different boxes with different operating systems and different configurations at the same time. Thanks for all your work Heikki! Cheers, Brian > Heikki, >

Re: [Got error 139 from table handler using InnoDB]

is problem has already been solved. I've been using MySQL for development for sometime. Up until now I've been using MyISAM tables. I've decided to switch to InnoDB because some table files (*.MYD) are approaching the OS limit. I get the above error (139) when trying to enter a mo