Ingres Replicator on HP-UX

Hi, all.

I'm about to start a project to evaluate Ingres Replicator for a
customer who wishes to implement a contingency plan between databases
at two different sites. The idea is relatively simple: from each site,
data will be replicated to an unprotected read-only target database at
the other site.

While I have had substantial experience with "older versions" of
Replicator, it's been a few years since I have really worked with it.
I believe that the last version that I really ever implemented was OI
2.0... which still was based on database rules instead of the newer
change recorder / distribution threads architecture.

I have a couple of questions for anyone with any experience with the
latest versions, and would greatly appreciate any help I can get!

1) The customer's version of Ingres is Ingres II 2.0/0001 (hpb.us5/00).
They are scheduled to migrate to Ingres II 2.5 in November. Are there
any major differences (architectural changes or bug fixes) between
these versions of Replicator? Can we expect any problems with migrating
replicator, or would there be any good reasons to wait and implement
replication only after 2.5 is installed?

2) I know that in the older versions, each "replicator server" must be
compiled and linked within the specific Ingres environment. I assume
this is still true (according to the manual, it still is). My customer
is hesitant to purchase HP-UX's software development kit for what is
initially just an evaluation phase. Does anyone know of another
alternative for C language compilation on an HP-UX 11i box?

3) If anyone has any caveats or recommendations for this kind of
environment, I will gladly receive suggestions! I'm mostly afraid of
possible locking / deadlock problems (which was what I suffered most
with in past versions!). Have there been any improvements in this
area?

Thanks in advance for any assistance!

James Gramling
Commit Work Informatica
Rio de Janeiro, Brasil

.

Relevant Pages

  • Re: [Info-ingres] Ingres Replicator on HP-UX
    ... > customer who wishes to implement a contingency plan between databases ... > data will be replicated to an unprotected read-only target database at ... > Replicator, it's been a few years since I have really worked with it. ... > They are scheduled to migrate to Ingres II 2.5 in November. ...
    (comp.databases.ingres)
  • Re: [Info-ingres] Replicator & role ingrep
    ... In my test environment I didn't use the WHERE clause and there is no duplicated update on the table involved (the replicator update and the rule update). ... On Ingres r3 versión I don't find the information about this kind of setting. ... R3 still sets the ingrep role as far as I know, so you should not need to change your rule WHERE clauses. ...
    (comp.databases.ingres)
  • Re: [Info-Ingres] Lets talk replication & ingres replicator
    ... Ingres to "replicate" a database and maintain a standby machine? ... What's involved in this and are the tools integral to Ingres? ... Let's talk replication & ingres replicator ... [Openroad-users] Let's talk replication & ingres replicator ...
    (comp.databases.ingres)
  • Re: restart replication after reload of database
    ... > Before Replicator 2.0 mean: ... > - need to compile replication server ... > - change recording by DBMS Server ... '00200' refers to both the Ingres and Replicator ...
    (comp.databases.ingres)
  • [Info-ingres] Re: Ingres/Replicator Stress Test
    ... I think the second row was caused by the update collision - although ... I'm replicating Peer-to-Peer as I wanted the replicated database to be ... Even more fun is if the Replicator Server can't find the data in the base ... Plus the deadlock contention is between user updates and the ...
    (comp.databases.ingres)