🚀 go-pugleaf

Easiest way is attach to the database from the other server via ReplManager
and choose remove system objects, if you can't do that then you can manually
remove the 3 REPL tables (REPL_LOG etc)
You then need to remove all the triggers that are on each table that you
replicate (typically there are 3 per table to deal with insert, update and
delete) not sure if you need to remove the triggers first as they depend on
the REPL_... tables.

First way is defenately the easiest, but depending on the line you use to
connect to the database (ie local network, wan, modem dial up) this could
take a while.

HTH
Steve


"Steve Weston" <sweston{no spam}@westonmuir.com> wrote in message
news:40a22827$1@newsgroups.borland.com...
> I have restored an IB 7.1 db onto another server. How do I remove the repl
> objects (tables, triggers, etc.)?
>
> -- 
> Steven S. Weston
>
>

Manual removal worked. But there were a couple of other objects (generator,
etc.) and, of course, the triggers had to be removed first. Thanks.

-- 
Steven S. Weston

Greetings...

But after ReplManager has removed "System Objects" (tables and triggers), if
you backup the database, you notice there is some priveledges for a user
called REPL$XXX... and that user doesn't appear in isc4.gdb (or
security.fdb).

Do you know how to remove every trace of the Replicator?

TIA,

Sergio H.

"Steve Ball" <SteveBall@noSpam.uku.co.uk> escribi� en el mensaje
news:40a7501d@newsgroups.borland.com...
> Easiest way is attach to the database from the other server via
ReplManager
> and choose remove system objects, if you can't do that then you can
manually
> remove the 3 REPL tables (REPL_LOG etc)
> You then need to remove all the triggers that are on each table that you
> replicate (typically there are 3 per table to deal with insert, update and
> delete) not sure if you need to remove the triggers first as they depend
on
> the REPL_... tables.
>
> First way is defenately the easiest, but depending on the line you use to
> connect to the database (ie local network, wan, modem dial up) this could
> take a while.
>
> HTH
> Steve
>
>
> "Steve Weston" <sweston{no spam}@westonmuir.com> wrote in message
> news:40a22827$1@newsgroups.borland.com...
> > I have restored an IB 7.1 db onto another server. How do I remove the
repl
> > objects (tables, triggers, etc.)?
> >
> > --
> > Steven S. Weston
> >
> >
>
>

I can't remember the exact syntax, but just run an SQL command to revoke 
privilages.
something like

REVOKE ALL on MYTABLE from REPL$XXX
hth
Steve

"Sergio H." <topx@geocities.com> wrote in message 
news:41671f87$1@newsgroups.borland.com...
> Greetings...
>
> But after ReplManager has removed "System Objects" (tables and triggers), 
> if
> you backup the database, you notice there is some priveledges for a user
> called REPL$XXX... and that user doesn't appear in isc4.gdb (or
> security.fdb).
>
> Do you know how to remove every trace of the Replicator?
>
> TIA,
>
> Sergio H.
>
> "Steve Ball" <SteveBall@noSpam.uku.co.uk> escribi� en el mensaje
> news:40a7501d@newsgroups.borland.com...
>> Easiest way is attach to the database from the other server via
> ReplManager
>> and choose remove system objects, if you can't do that then you can
> manually
>> remove the 3 REPL tables (REPL_LOG etc)
>> You then need to remove all the triggers that are on each table that you
>> replicate (typically there are 3 per table to deal with insert, update 
>> and
>> delete) not sure if you need to remove the triggers first as they depend
> on
>> the REPL_... tables.
>>
>> First way is defenately the easiest, but depending on the line you use to
>> connect to the database (ie local network, wan, modem dial up) this could
>> take a while.
>>
>> HTH
>> Steve
>>
>>
>> "Steve Weston" <sweston{no spam}@westonmuir.com> wrote in message
>> news:40a22827$1@newsgroups.borland.com...
>> > I have restored an IB 7.1 db onto another server. How do I remove the
> repl
>> > objects (tables, triggers, etc.)?
>> >
>> > --
>> > Steven S. Weston
>> >
>> >
>>
>>
>
> 

Oh yes, REVOKE.  But I ended up using statements directly to the RDB$
tables.

So, after using "Remove System Objects" in the ReplManager, one has to run:

DROP TRIGGER REPL_GEN_SEQNO;
DROP TABLE MANUAL_LOG;
DROP TABLE REPL_LOG;
DROP TABLE REPL_SEPARATOR;
DELETE FROM RDB$USER_PRIVILEGES WHERE RDB$USER LIKE 'REPL%%';

And I think this sould be done by the ReplManager.

Finally, I didn't want to use IBReplicator because it never went with my
trigger-generated primary keys.  I'm trying to post here the message I got
rejected from ibp_replicator@lists.ibphoenix.com because of being >17 Kb
long.

Regards,

Sergio H. Guerrero R.

"Steve Ball" <SteveBall@noSpam.uku.co.uk> escribi� en el mensaje
news:416b0493$1@newsgroups.borland.com...
> I can't remember the exact syntax, but just run an SQL command to revoke
> privilages.
> something like
>
> REVOKE ALL on MYTABLE from REPL$XXX
> hth
> Steve
>

Well the Drop Trigger stuff normally is done via ReplManager.
My guess is that you might have been dropping a scheme but not the one in 
the database. Its all done via the scheme numbers and this does work. Its 
careful as you could have more than 1 scheme in a database.
Steve

"Sergio H." <topx@geocities.com> wrote in message 
news:416d5dad@newsgroups.borland.com...
> Oh yes, REVOKE.  But I ended up using statements directly to the RDB$
> tables.
>
> So, after using "Remove System Objects" in the ReplManager, one has to 
> run:
>
> DROP TRIGGER REPL_GEN_SEQNO;
> DROP TABLE MANUAL_LOG;
> DROP TABLE REPL_LOG;
> DROP TABLE REPL_SEPARATOR;
> DELETE FROM RDB$USER_PRIVILEGES WHERE RDB$USER LIKE 'REPL%%';
>
> And I think this sould be done by the ReplManager.
>
> Finally, I didn't want to use IBReplicator because it never went with my
> trigger-generated primary keys.  I'm trying to post here the message I got
> rejected from ibp_replicator@lists.ibphoenix.com because of being >17 Kb
> long.
>
> Regards,
>
> Sergio H. Guerrero R.
>
> "Steve Ball" <SteveBall@noSpam.uku.co.uk> escribi� en el mensaje
> news:416b0493$1@newsgroups.borland.com...
>> I can't remember the exact syntax, but just run an SQL command to revoke
>> privilages.
>> something like
>>
>> REVOKE ALL on MYTABLE from REPL$XXX
>> hth
>> Steve
>>
>
>