List:General Discussion« Previous MessageNext Message »
From:Gabriel Tucker Date:May 4 2004 3:54pm
Subject:RE: InnoDB - Foreign Key - Error 150.
View as plain text  
Hooray!

The last problem was b/c I did not have the same InnoDB settings in my cnf file.

Again, thank you all for your time in this matter!

Gabe

-----Original Message-----
From: GTUCKER@stripped 
Sent: Tuesday, May 04, 2004 11:29 AM
To: Victoria Reznichenko; mysql@stripped
Subject: RE: InnoDB - Foreign Key - Error 150.


Victoria 

That seemed to work well, thank you.

However, I received another error that I am not sure how to troubleshoot during the
restore:
	ERROR 1114 at line 83 in file: '/bb/bin/mysql/backups/archive_4320.sql': The table
	'cur_reject_tk_sum' is full

What can I do here?

Thanks - Gabe

-----Original Message-----
From: Victoria Reznichenko [mailto:victoria.reznichenko@stripped]
Sent: Tuesday, May 04, 2004 10:35 AM
To: mysql@stripped
Subject: Re: InnoDB - Foreign Key - Error 150.


"Tucker, Gabriel" <GTucker@stripped> wrote:
> Marvin
> 
> I believe that is the problem with the restore.  When I create the =
> archive file using the mysqldump command and options previously listed, =
> I get the create table in the order listed below and thus, the foreign =
> key constraint is created on table cur_reject_tk_sum before the =
> object_type table has been created.
> 
> Now my questions are:
> [1] Is the above scenario my problem?
> [2] Is so, how can I correct it?  Is this a problem with the way I am =
> using mysqldump? [see commands below]  Or, is this a problem with how I =
> am restoring the database? [Which, I create a "default" mysql database =
> on its own port and then run from the prompt "mysql --port=3D =
> --socket=3D -p < archive_file.sql"

Add to the beginning of the dump file command:

SET FOREIGN_KEY_CHECKS = 0;

and then restore tables.

Or in the mysql client execute the following commands:

SET FOREIGN_KEY_CHECKS = 0;
SOURCE archive_file.sql;
SET FOREIGN_KEY_CHECKS = 1;



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Victoria Reznichenko
 / /|_/ / // /\ \/ /_/ / /__   Victoria.Reznichenko@stripped
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
       <___/   www.mysql.com





-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=1


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=1

Thread
InnoDB - Foreign Key - Error 150.Gabriel Tucker4 May
  • Re: InnoDB - Foreign Key - Error 150.Josh Trutwin4 May
RE: InnoDB - Foreign Key - Error 150.Marvin Wright4 May
RE: InnoDB - Foreign Key - Error 150.Gabriel Tucker4 May
  • Re: InnoDB - Foreign Key - Error 150.Victoria Reznichenko4 May
RE: InnoDB - Foreign Key - Error 150.Marvin Wright4 May
  • Re: InnoDB - Foreign Key - Error 150.Ken Menzel4 May
RE: InnoDB - Foreign Key - Error 150.Gabriel Tucker4 May
  • Re: InnoDB - Foreign Key - Error 150.Josh Trutwin4 May
  • Re: InnoDB - Foreign Key - Error 150.Luciano Barcaro4 May
RE: InnoDB - Foreign Key - Error 150.Gabriel Tucker4 May
RE: InnoDB - Foreign Key - Error 150.Gabriel Tucker4 May
  • Re: InnoDB - Foreign Key - Error 150.Victoria Reznichenko5 May
RE: InnoDB - Foreign Key - Error 150.Gabriel Tucker4 May