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 ha
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 something problem on
> exceeding
> a r
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 i
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 an
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
