Replication Error on Slave

--90e6ba6e8fb2f636a4049ad0bcd9
Content-Type: text/plain; charset=ISO-8859-1

I have setup mysql replication with below scenario



**On master server I have two databases *A and B*. App team use database B
temporarily for there application to compute calculation and insert the
values on A database.



**On Slave Server I replicate database *A alone* and my replication not
working due to data fetching happen on B database.


Kindly help me out to resolve this issue.

-Naga

--90e6ba6e8fb2f636a4049ad0bcd9--

Re: Replication Error on Slave

--0015174c16e6da27ee049ad0eb4a
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jan 27, 2011 at 10:40 AM, Nagaraj S 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

--0015174c16e6da27ee049ad0eb4a--

Re: Replication Error on Slave

> **On master server I have two databases *A and B*. App team use database =
B
> temporarily for there application to =A0compute calculation and insert th=
e
> values on A database.

For certain statements you could start with "SET SQL_BIN_LOG=3D0" so it
doesn't log that statement, and it won't be replicated.

-Kristian

--
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: Replication Error on Slave

--20cf304346b647dbb3049bc0adeb
Content-Type: text/plain; charset=ISO-8859-1

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 wrote:

> On Thu, Jan 27, 2011 at 10:40 AM, Nagaraj S 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
>

--20cf304346b647dbb3049bc0adeb--