On Feb 26, 10:34 am, "Valentin Minzatu" <valentinminz..._at_yahoo.com>
wrote:
> On Feb 24, 11:30 pm, PKNa..._at_gmail.com wrote:
>
> > Hi,
> > I needed to alter a table that was in replication and while adding the
> > table back into replication (dbms_repcat.create_master_repobject)
> > after making the changes, I got a ORA-02992 and a ORA-02266. The
> > table that I was looking to add and the other table that has the
> > constraint are both exactly the same in both replication sites. I
> > have copy_rows parameter set to true.
>
> > I was able to add the table back into the replication group by 1)
> > disabling the constraint or 2) by changing copy_rows to false. I am
> > not sure what the problem is. Does copy_rows=true attempt to copy all
> > rows and just ignore the duplicate records?
>
> > Thanks
> > Pradeep
>
> When you add the table to the group, if copy_rows is set to true, it
> will attempt to copy everything at the source to the destination,
> assuming that the destination is an empty table.
> More details can be found in the advanced replication manual.
Thanks Valentin. I will look through it again. I skimmed through it
and seem to have missed it.
Received on Mon Feb 26 2007 - 11:48:56 CST
