Re: Using ER for Migration from 10.0 to 11.5

On Dec 19, 9:41 am, "Andrew Ford" <af...@networkip.net> wrote: > We are in the process of migrating from one server running IDS 10.00.UC5 32 bit Red Hat Linux 3 to another running IDS 11.50.FC3 64 > bit Red Hat Linux 5. > > I would like to us ER to keep the new server in sync with the old server until we actually migrate. > > I have unloaded the data from the old server and loaded it into the new server. > > I have defined and started replication from the old server to the new server for all tables. > > What is the best way to syncronize the new server with the old server in order to capture the changes that have occurred since the > start of the old server unload and the start of replication? > > I'm more interested in minimizing the impact to the old server (production) when syncronizing large tables than I am with the speed > of the syncronization. > > Is the 'cdr check replicate' command with the repair option preferred or is the 'cdr sync replicate' option preferred in this > scenario? > > Thanks, > > Andrew You should use CDR sync. Define the replicate as "always apply" so that you will have upsert support. Since this is to be only a 2 node system and all of the updates are being made on one node, you don't really need to worry about conflict resolution. Use cdr sync. CDR sync will not hit the logical logs and will not require that the scan is ordered. CDR check will scan the data by primary key and will generally take longer to perform than a sync unless the majority of the data is on both nodes. Also cdr sync will coordinate the scan of the table with the transfer of the data to avoid spooling or log wrap. The internal cdr sync scan was implemented in IDS10xC4.