Replication Cold Start
in [DB2]
|
From: Asphalt Blazer on 11 Mar 2010 09:08 I have 2 databases in two different instances that I am doing one-way replication to. I will be cold starting the replication when I first initialize it. But I do not want the target table to be refreshed. I have sychronized the capture side and apply side tables using export- import and then changed some column values on the target side after this export-import. I do not want these values to be overwritten. I just want the capture and apply to proceed from the current point on a cold start. Is there any way to do this? TIA.
From: whatever on 11 Mar 2010 11:45 On Mar 11, 9:08 am, Asphalt Blazer <asphaltbla...(a)gmail.com> wrote: > I have 2 databases in two different instances that I am doing one-way > replication to. I will be cold starting the replication when I first > initialize it. But I do not want the target table to be refreshed. I > have sychronized the capture side and apply side tables using export- > import and then changed some column values on the target side after > this export-import. I do not want these values to be overwritten. I > just want the capture and apply to proceed from the current point on a > cold start. Is there any way to do this? > > TIA. You have not mentioned whether this is SQL or Q Replication. If it is SQL Replication...once u do a COLD START of the capture ..you have to do a FAKE FULL REFRSH. Basically u have to update ASN.IBMSNAP_REGISTER SET DISABLE_REFRESH = 1 and also PRUNCTL Table. You have to change tables in the APPLY Side also. There should be lots of documentation regardin this in the info center..Pls check Cheers... Shashi Mannepalli
From: Asphalt Blazer on 11 Mar 2010 12:40 On Mar 11, 11:45 am, whatever <audheya2...(a)gmail.com> wrote: > On Mar 11, 9:08 am, Asphalt Blazer <asphaltbla...(a)gmail.com> wrote: > > > I have 2 databases in two different instances that I am doing one-way > > replication to. I will be cold starting the replication when I first > > initialize it. But I do not want the target table to be refreshed. I > > have sychronized the capture side and apply side tables using export- > > import and then changed some column values on the target side after > > this export-import. I do not want these values to be overwritten. I > > just want the capture and apply to proceed from the current point on a > > cold start. Is there any way to do this? > > > TIA. > This is Q-Replication. I have done the disable refresh already. But on starting the apply, replication is not working. Is there any particular documentation regarding this you can point me to?Thank you. > You have not mentioned whether this is SQL or Q Replication. > > If it is SQL Replication...once u do a COLD START of the capture ..you > have to do a FAKE FULL REFRSH. > Basically u have to update ASN.IBMSNAP_REGISTER SET DISABLE_REFRESH = > 1 and also PRUNCTL Table. > You have to change tables in the APPLY Side also. > > There should be lots of documentation regardin this in the info > center..Pls check > > Cheers... > Shashi Mannepalli
From: whatever on 11 Mar 2010 14:41 On Mar 11, 12:40 pm, Asphalt Blazer <asphaltbla...(a)gmail.com> wrote: > On Mar 11, 11:45 am, whatever <audheya2...(a)gmail.com> wrote:> On Mar 11, 9:08 am, Asphalt Blazer <asphaltbla...(a)gmail.com> wrote: > > > > I have 2 databases in two different instances that I am doing one-way > > > replication to. I will be cold starting the replication when I first > > > initialize it. But I do not want the target table to be refreshed. I > > > have sychronized the capture side and apply side tables using export- > > > import and then changed some column values on the target side after > > > this export-import. I do not want these values to be overwritten. I > > > just want the capture and apply to proceed from the current point on a > > > cold start. Is there any way to do this? > > > > TIA. > > This is Q-Replication. > I have done the disable refresh already. But on starting the apply, > replication is not working. Is there any particular documentation > regarding this you can point me to?Thank you. > > > > > You have not mentioned whether this is SQL or Q Replication. > > > If it is SQL Replication...once u do a COLD START of the capture ..you > > have to do a FAKE FULL REFRSH. > > Basically u have to update ASN.IBMSNAP_REGISTER SET DISABLE_REFRESH = > > 1 and also PRUNCTL Table. > > You have to change tables in the APPLY Side also. > > > There should be lots of documentation regardin this in the info > > center..Pls check > > > Cheers... > > Shashi Mannepalli- Hide quoted text - > > - Show quoted text - http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com..ibm.swg.im.iis.repl.qrepl.doc/topics/iiyrqcapcmtncold.html Look for Considerations for using the cold start mode cheers... Shashi Mannepalli
From: blazer462 on 12 Mar 2010 08:11 Make sure your queue is empty before doing the cold start. This would be the most common reason why applier would'nt start after the cold start.
|
Pages: 1 Prev: Doing a join on a non-numeric column? Next: how to sum a derived column |