Got error 139 from storage engine (InnoDB)

--000e0cd32f32aa6181048a9ba10a
Content-Type: text/plain; charset=ISO-8859-1

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.

Any have idea how to fix this?

Thanks.

Regards,
James

--000e0cd32f32aa6181048a9ba10a--

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 and it's something problem on
> exceeding
> a row-length limit in the InnoDB table.
>
> Any have idea how to fix this?
>
> Thanks.
>
> Regards,
> James
>

I can not recall having seen that error before. I did a slight amount
of googling and it sounds like it might be a innodb tuning issue.
Please post:
1. Any relevant entries in your error log file.
2. Your my.cnf.
3. You servers specs and whether the server also runs other daemons.


--
Rob Wultsch
wultsch@gmail.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: Got error 139 from storage engine (InnoDB)

--0015175cb8a00b9159048aa77fff
Content-Type: text/plain; charset=ISO-8859-1

I think this is related to foreign key constraint data types don't match
up... so verify your CREATE TABLE structure or post the CREATE TABLE
statement for your table.

Or there is chance of data type size and the value you are inserting.. such
type of problem occurs if the data import ie source 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 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.
> >
> > Any have idea how to fix this?
> >
> > Thanks.
> >
> > Regards,
> > James
> >
>
> I can not recall having seen that error before. I did a slight amount
> of googling and it sounds like it might be a innodb tuning issue.
> Please post:
> 1. Any relevant entries in your error log file.
> 2. Your my.cnf.
> 3. You servers specs and whether the server also runs other daemons.
>
>
> --
> Rob Wultsch
> wultsch@gmail.com
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
> http://lists.mysql.com/mysql?unsub=aim.prabhat@gmail.com
>
>


--
Best Regards,

Prabhat Kumar
MySQL DBA
Datavail-India Mumbai
Mobile : 91-9987681929
www.datavail.com

My Blog: http://adminlinux.blogspot.com
My LinkedIn: http://www.linkedin.com/in/profileprabhat

--0015175cb8a00b9159048aa77fff--

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 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.
>>
>> Any have idea how to fix this?
>>
>> Thanks.
>>
>> Regards,
>> James
>>
>
> I can not recall having seen that error before. I did a slight amount
> of googling and it sounds like it might be a innodb tuning issue.
> Please post:
> 1. Any relevant entries in your error log file.
> 2. Your my.cnf.
> 3. You servers specs and whether the server also runs other daemons.
>
>
> --
> Rob Wultsch
> wultsch@gmail.com
>

It would also be helpful for you to run the import with the verbose
flag. Then we would have a better understanding of exactly what
statement was causing the error.

--
Rob Wultsch
wultsch@gmail.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: Got error 139 from storage engine (InnoDB)

James, all,


James Corteciano wrote:
> Hi All,
>=20
> 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.

you are putting overload on our crystal balls - why don't you tell us
(at least!) the MySQL version and the platform?


"error 139" looks like it is some Unix/Linux.
On all these platforms, the exit code "139" means the process died
because of signal 11 ("segmentation violation", "SIGSEGV"),
and then a core dump was taken (indicated by the value 128).
139 == 11 + 128.

You should use your debugger of choice to get a stack backtrace, unle=
ss
this was already done automatically during crash analysis / recovery.


>=20
> Any have idea how to fix this?

Only when the backtrace is known, there may be some educated guesses
about the cause of the problem.
But all such effort is wasted unless you tell the versions.


Jörg

--=20
Joerg Bruehe, MySQL Build Team, Joerg.Bruehe@Sun.COM
ORACLE Deutschland B.V. & Co. KG, Komturstrasse 18a, D-12099 Berl=
in
Geschaeftsfuehrer: Juergen Kunz, Marcel v.d. Molen, Alexander v.d. Ve=
n
Amtsgericht Muenchen: HRA 95603


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg

Re: Got error 139 from storage engine (InnoDB)

--000e0cd20d648e991e048ab9c3e6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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 has 24GB memory and Quad-Core CPU. The platform is RHEL 5.=
5
x64 and mysql-server-5.0.77-4.el5_4.2.

*Rob Wultsch *and Prabhat Kumar, thanks for your response.


Regards,
James


On Tue, Jul 6, 2010 at 5:19 PM, Joerg Bruehe wrote:

> James, all,
>
>
> James Corteciano wrote:
> > Hi All,
> >
> > I have received error message "ERROR 1030 (HY000) at line 167: Got erro=
r
> 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.
>
> you are putting overload on our crystal balls - why don't you tell us
> (at least!) the MySQL version and the platform?
>
>
> "error 139" looks like it is some Unix/Linux.
> On all these platforms, the exit code "139" means the process died
> because of signal 11 ("segmentation violation", "SIGSEGV"),
> and then a core dump was taken (indicated by the value 128).
> 139 == 11 + 128.
>
> You should use your debugger of choice to get a stack backtrace, unless
> this was already done automatically during crash analysis / recovery.
>
>
> >
> > Any have idea how to fix this?
>
> Only when the backtrace is known, there may be some educated guesses
> about the cause of the problem.
> But all such effort is wasted unless you tell the versions.
>
>
> Jörg
>
> --
> Joerg Bruehe, MySQL Build Team, Joerg.Bruehe@Sun.COM
> ORACLE Deutschland B.V. & Co. KG, Komturstrasse 18a, D-12099 Berlin
> Geschaeftsfuehrer: Juergen Kunz, Marcel v.d. Molen, Alexander v.d. Ven
> Amtsgericht Muenchen: HRA 95603
>
>

--000e0cd20d648e991e048ab9c3e6--