List:General Discussion« Previous MessageNext Message »
From:Nagaraj S Date:February 8 2011 7:55am
Subject:Re: Replication Error on Slave
View as plain text  
All,

Thanks for your replies and as per the advise I switched to row-based
replication but replication ended with below error.



*Last_Error: Error 'Table 'b.sdefrent' doesn't exist' on query. Default
database: 'b. Query: 'drop table sdefrent'*


above error is due to non existence of database and table. However bit
confused on the error I got, if its row based replication why its taking as
statement. Please help me here. Thank you

-Naga


On Thu, Jan 27, 2011 at 3:23 PM, Johan De Meersman <vegivamp@stripped>wrote:

>  On Thu, Jan 27, 2011 at 10:40 AM, Nagaraj S <nagaraj.chk@stripped>wrote:
>
>> **On Slave Server I replicate database *A alone* and my replication not
>> working due to data fetching happen on B database.
>>
>
> Well, yes. Statement-based replication does what it says on the box: it
> executes the exact same statement on the slave. If database B is not there,
> then insert into A select from B will not work.
>
> You may switch to row-based replication (which of course has it's own
> caveats, see the online manuals); or you can simply choose to also replicate
> database B.
>
>
>
> --
> Bier met grenadyn
> Is als mosterd by den wyn
> Sy die't drinkt, is eene kwezel
> Hy die't drinkt, is ras een ezel
>

Thread
Replication Error on SlaveNagaraj S27 Jan
  • Re: Replication Error on SlaveJohan De Meersman27 Jan
    • Re: Replication Error on SlaveNagaraj S8 Feb
  • Re: Replication Error on SlaveKristian Davies3 Feb