Reinitialize EDR
Andrea Verni could not redefine Enterprise Replication after deleting it; cdr define server --init gave 'Replication already active', even after dropping syscdr. Madison Pruet said cdr delete server should suffice. Wile E. Coyote said on IDS 7.31 syscdr remains; define without --init or drop syscdr and rebuild sysmaster. Madison said to open a support case and never drop syscdr manually.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hi guys,
I'm tyring to set up EDR between two test servers.
Is it possible that I have to make 'oninit -iy' each time I want to
start with EDR from scratch ?
Exactly... the first time I start with EDR all works perfectly, then I
delete the replication, delete the server but when I try to re-define
the remote server with command
cdr define server --connet=remote_server --init --sync=g_local g_remote
I get this error:
Replication already active.
I tried to drop 'syscdr' database but it seams not enough. I saw that
also sysmaster keeps information about edr so...
what is the correct way to recreate an edr environment WITHOUT
re-initialize the whole server ?
TIA
1) Which version of the engine?
2) All that should really be necessary is to run "cdr delete server" for
the server that you want
to remove from the enterprise.
Andrea Verni wrote:
> Hi guys,
>
> I'm tyring to set up EDR between two test servers.
>
> Is it possible that I have to make 'oninit -iy' each time I want to
> start with EDR from scratch ?
>
> Exactly... the first time I start with EDR all works perfectly, then I
> delete the replication, delete the server but when I try to re-define
> the remote server with command
>
> cdr define server --connet=remote_server --init --sync=g_local g_remote
>
> I get this error:
>
> Replication already active.
>
> I tried to drop 'syscdr' database but it seams not enough. I saw that
> also sysmaster keeps information about edr so...
>
> what is the correct way to recreate an edr environment WITHOUT
> re-initialize the whole server ?
>
> TIA
Madison Pruet wrote: > > 1) Which version of the engine? I suppose IDS 7.31 > 2) All that should really be necessary is to run "cdr delete server" for > the server that you want > to remove from the enterprise. In this version it is not enough to do a "cdr delete server". the syscdr database remains in the server. To redefine your cdr server you have the following possibillities: 1. cdr define server without --init/-I 2. drop syscdr database, rebuild sysmaster database Wile
"Wile E. Coyote" wrote: > Madison Pruet wrote: > > > > 1) Which version of the engine? > > I suppose IDS 7.31 > > > 2) All that should really be necessary is to run "cdr delete server" for > > the server that you want > > to remove from the enterprise. > > In this version it is not enough to do a "cdr delete server". the > syscdr database remains in the server. If the syscdr database remains on an 7.31 instance after a cdr delete server has been run on that instance, then that indicates that there is a problem. Please open a case with tech support so that the problem can be correctly resolved. You should never have to manually drop the syscdr database. That can lead to inconsistancy problems with the global dictionary between the various instances. Additionally this will cause inconsistancies with sysmaster. > > > To redefine your cdr server you have the following possibillities: > > 1. cdr define server without --init/-I > 2. drop syscdr database, rebuild sysmaster database > > Wile