Hi Chloe,

There are means of doing this with rollforwarddb, I've certainly
managed to make a creeping rollforwarddb, however....

Do you really want to use an unsupported means of recovering
a database to make a hot standby? You would have to use your own
code to support this and when you finally need the database and you
find out how bad it may have been -- do you really want to go up to the
boss and tell them it was your dodgy code and not CA?

My suggestion is that you look seriously at the implications of
Replicator before considering an alternative.

Martin Bowes
> Hi
>
> I've been asked to look at options for setting up remote standby copy
> of our Ingres 2.6 database. One option is obviously replication, but
> this would involve some development work (long column/table names,
> unique keys).
>
> The method we're looking at for the Oracle and SQL Server components
> of the system (don't ask - just don't ask) is log shipping. While this
> isn't supported in Ingres (at least this version) I believe there is
> an unsupported approach involving rollforwarddb which has been
> implemented in various organisations. If anyone has any documentation
> on how this was done it would be much appreciated.
>
> Chloe Crowder
> The British Library
--

Random Duckman Quote #53:
Nurse: Maam, please wait outside, the doctor may need to start
slamming his
fist on the patient's chest and yelling 'Live, damn you, live' and that
may be hard to watch.