Hi all!



I am in the process of upgrading from Ingres 2.6 to Ingres 9.1.1-103 (Ingres
2006 r2) on a tru64 5.1b box, production environment.

For this, I have two identical machines (same OS, same ingres
configuration,etc), one I use for production environment and the other is
for contingency pourpose.

My plan is make upgrade to 2006, directly over production machine; before
this I am going to have a snapshot of DBs over the contingency machine.

Suppose the upgrade process is success and production environment is active
and transactions are processed over Ingres 9.1.1 version and after a few
hours I have performance problems or whatever occurs and I have to go back
to Ingres 2.6 version. For this, I have data snapshot on Ingres 2.6 on
contingency machine, before 2006 is going to production, but new
transactions is on Ingres 9.1.1 machine.

What I need to know is if it is possible to use journals files from 9.1.1
version, copy them to Ingres 2.6 installation and perform a rollforwarddb on
2.6 in order to have again Ingres 2.6 data up to date?



Many thanks for your help



Regards



Oscar





Lic. Oscar Carlés Barriocanal

ITIL V3 Certified

Director de Servicios

Íntegra SRL

(59521) 424473 RA

Asunción - Paraguay

On Apr 25, 2009, at 10:31 AM, Oscar Carlés wrote:


I know for sure that some log records have had format changes, but
I don't know whether there was any change to the log record
header (which would prevent any of them working with 2.6).

The best answer is no, you can't apply 9.1.1 journals on a
2.6 installation. You *might* get lucky, and have it work,
but I don't think you could count on it. All it takes is
one unrecognized journal record to stop the rollforward, even
if it manages to recognize most of the journal data.

You might have better luck running auditdb on the 9.1.1
side to create audit trail files; auditdb can write them
in a format that you can copy into a table, and then a
reasonably simple program can apply the changes. This
doesn't cover all possible changes, but it will allow you
to replay inserts, updates, and deletes which are probably
the important bits in your situation. (ija will do this
for you, but I don't know if it understands auditdb output
or not; it's been ages since I played with ija.)

Karl

Hi Oscar,



If a retreat becomes absolutely necessary your best option is probably an unload/reload.



Martin Bowes







From: info-ingres-bounces (AT) kettleriver...ting (DOT) com [mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Oscar Carlés
Sent: 25 April 2009 15:32
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: [Info-Ingres] Go back from Ingres 9.1.1-103 to Ingres 2.6, tru64



Hi all!



I am in the process of upgrading from Ingres 2.6 to Ingres 9.1.1-103 (Ingres 2006 r2) on a tru64 5.1b box, production environment.

For this, I have two identical machines (same OS, same ingres configuration,etc), one I use for production environment and the other is for contingency pourpose.

My plan is make upgrade to 2006, directly over production machine; before this I am going to have a snapshot of DBs over the contingency machine.

Suppose the upgrade process is success and production environment is active and transactions are processed over Ingres 9.1.1 version and after a few hours I have performance problems or whatever occurs and I have to go back to Ingres 2.6 version. For this, I have data snapshot on Ingres 2.6 on contingency machine, before 2006 is going to production, but new transactions is on Ingres 9.1.1 machine.

What I need to know is if it is possible to use journals files from 9.1.1 version, copy them to Ingres 2.6 installation and perform a rollforwarddb on 2.6 in order to have again Ingres 2.6 data up to date?



Many thanks for your help



Regards



Oscar





Lic. Oscar Carlés Barriocanal

ITIL V3 Certified

Director de Servicios

Íntegra SRL

(59521) 424473 RA

Asunción - Paraguay