Can you post the failed SQL statement from your altered bin log, and maybe the preceding commands related to that table?
Scott Tanner AMi Entertainment.net On Thu, 2006-03-09 at 08:28, Goldblatt, Eric wrote: > Scott, > > The table already existed before the binlog. The strange thing is that > there were inserts into this table earlier in the binlog, and they did > not produce any error messages. > > > Eric > -----Original Message----- > From: Scott Tanner [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 08, 2006 3:46 PM > To: Goldblatt, Eric > Subject: Re: replication after editing bin logs > > On Wed, 2006-03-08 at 14:51, Goldblatt, Eric wrote: > snip- > > When I came to step 5, I submitted the SQL text file as a batch job: > > > > mysql -u root -p -e "source binlogs_045_052_parsed" > > > > After many hours I received the following error message: > > > > ERROR 1036 (HY000) at line 1387471 in file: 'binlogs_045_052_parsed': > > Table 'AB4539p2' is read only > > > > At this point, the mysql batch job terminated. > > If its saying the table is read only, it could be a simple permissions > issue. Is this table being created from the binlog, or is it an existing > table? > > > Regards, > > Scott Tanner > AMi Entertainment -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
