Can anyone tell me if a 2.6 installation can rollfoward a database
from a 2.0 checkpoint?

The short answer is no.
I can imagine situations in which you could MAYBE get it to work;
for instance, rollforward of an offline checkpoint with no journals might
possibly work, although you'd still have to upgradedb the result.
But in general, no.

Karl

Thought so... I did attempt it - but it just wan't having any of it.

Thanks for the quick reply.

Gareth

-----Original Message-----
From: Karl & Betty Schendel [mailto:schendel@kbcomputer.com]
Sent: 23 June 2004 12:01
To: 'info-ingres@ams.org'
Subject: Re: [Info-Ingres] rollforwarddb

Can anyone tell me if a 2.6 installation can rollfoward a database from a
2.0 checkpoint?

The short answer is no.
I can imagine situations in which you could MAYBE get it to work;
for instance, rollforward of an offline checkpoint with no journals might
possibly work, although you'd still have to upgradedb the result.
But in general, no.

Karl

English:- This message is confidential. If you are not the intended
recipient of the message then please notify the sender immediately. Any of
the statements or comments made above should be regarded as personal and not
necessarily those of Bro Morgannwg NHS Trust, any constituent part or
connected body. Cymraeg:- Mae'r neges hon yn gyfrinachol. Os nad chi yw'r
derbynnydd y bwriedid y neges ar ei gyfer, byddwch mor garedig â rhoi gwybod
i'r anfonydd yn ddi-oed. Dylid ystyried unrhyw ddatganiadau neu sylwadau a
wneir uchod yn rhai personol, ac nid o angenrhaid yn rhai o eiddo
Ymddiriedolaeth GIG Bro Morgannwg, nac unrhyw ran gyfansoddol ohoni na
chorff cysylltiedig.

<mailto:Gareth.Williams@bromor-tr.wales.nhs.uk> ]

<mailto:schendel@kbcomputer.com> ]

2.0 checkpoint?

Hi Gareth,

Karl is correct about online checkpoints and any attempt to recover to
point-in-time using the journals.

However, there is an unsupported way to get Ingres 2.6 to "adopt" and Ingres
2.0 offline checkpoint:-

*    Use infodb to identify ALL data locations
*    ingstop
*    Remove ALL underlying database files:-
    For each data_loc# do
        cd <data_loc#>; rm *
*    Recover the underlying database files from each .ckp file (using tar
or cpio) to their coreect data_loc#
*    Use cbf to format the transaction log file(s)
*    ingstart
*    Patch iidbdb to demote the dataabse back to version 2.0
    sql +Y iidbdb
    update iidatabase set dbcmptlvl = 8.0 where name = '<dbname>';\p\g\q
*    Upgradedb <dbname>
*    CHECKPOINT <dbname> AS SOON AS POSSIBLE

************************************************************************
DISCLAIMER
The information contained in this e-mail is confidential and is intended
for the recipient only.
If you have received it in error, please notify us immediately by reply
e-mail and then delete it from your system. Please do not copy it or
use it for any other purposes, or disclose the content of the e-mail
to any other person or store or copy the information in any medium.
The views contained in this e-mail are those of the author and not
necessarily those of Admenta UK Group.
************************************************************************