Hi everyone,

I have a "little" problem.
I have a directory containing all the files of a backup of an ingres
database in an older version but I've no running servers with that
version of ingres.
I installed ingres r3, I created a new db and then I replaced new
files with old files.
Trying to look at the database I obtain and error saying:

VMWS001 ::[II\INGRES\8dc , 06713dc0]: Thu Jul 05 13:07:41 2007
E_DM928B_CONFIG_NOT_COMPATABLE Configuration file is not compatible
with the current version of the DBMS. Config version = 4.1, DBMS
version = 6.1.
[cut]
VMWS001 ::[II\INGRES\8dc , 06713dc0]: Thu Jul 05 13:07:41 2007
E_DM0113_DB_INCOMPATABLE Database is incompatible with the current
version of the DBMS.
VMWS001 ::[II\INGRES\8dc , 06713dc0]: Thu Jul 05 13:07:41 2007
E_US0008 The requested database is not compatible with this server.
If a Release 5 database, convert it to Release 6.4 with the CONVTO60
utility,
then upgrade it with UPGRADEDB utility.
If a Release 6 database, upgrade it with the UPGRADEDB utility.

I serached for CONVTO60 but it's not present under the distribution
and anyway it would convert from release 5 and not 4 as error says.
How can I recover my old data? I can't find any conversion utility on
the web. Please help.
Thanks in advance.

At 12:05 PM +0000 7/5/07, Gibson wrote:
>Hi everyone,
>
>I have a "little" problem.
>I have a directory containing all the files of a backup of an ingres
>database in an older version but I've no running servers with that
>version of ingres.
>I installed ingres r3, I created a new db and then I replaced new
>files with old files.
[snip]

The situation is not necessarily unrecoverable, but I'm not sure
how practical it is to get you through this remotely. You may need
Tech Support help.

First question is: is your backup any good? If the backup was
taken with Ingres up and running, it's quite likely that the files
were in an inconsistent state, with some updates held in the Ingres
buffer cache and some not. On the other hand, if this is your only
backup, I guess you have to work with what you have.

Now, as to being able to access the database: you'll need to use
upgradedb, but before doing that, you need to fiddle the iidatabase
entry in iidbdb. You created what looks like an r3 database, but
the aaaaaaaa.cnf file says it's older. I can't tell exactly what
version from the error message, because it's reporting a
*config file* version (NOT an Ingres version). Config file v4
lasted for quite a while, 6.x thru OpenIngres 1.x and maybe even
Ingres II 2.0 (not sure).

Anyway, what you need to do is:
- update the iidatabase entry for your database to match what
the original database version is;
- run upgradedb against the database.

Sounds simple enough, if you know what dbcmptlvl and dbcmptminor
you need to put into the iidatabase entry. The good news is that
those values are in the aaaaaaaa.cnf file of the db. The bad
news is that there's no simple way of getting the info. "strings"
might give you the dbcmptlvl, it's a 4-character string e.g. 6.4,
6.53, 8.01, etc. The dbcmptminor is an integer immediately following,
and the only way you'll get it out short of writing a config file
dumper is a tool like od.

(There have always been rumors of a standalone config file dumper,
but I've never seen one, nor had the motivation to write one.)

Karl

> (There have always been rumors of a standalone config file dumper,
> but I've never seen one, nor had the motivation to write one.)
>
> Karl

Someone called Matthew Jones wrote one and advertised it on
comp.databases.ingres newsgroup:

http://groups.google.com/group/comp....6?dmode=source

I have a copy of it and it does seem to work on Solaris for Ingres 2.00.

My config file (for a Ingres II 2.0/0001 (su4.us5/00) 7097 db) has the
following header details according to the program:

??Header-(256
bytes)???????????????????????????????????????????? ????????????????
? Section len: 256 Section type: 00000006
?
? CNF version: 00040001 DB version: 00000003
?
? Unknown: 00000003 Status: 00000001
?
? Open DB count: 00000000
?
? Unknown: 000000000000000200000002
?
? Database ID: 341e692b
?
? Unused: 00000000
?
? Extents: 5
?
? Last table ID: 13597
?
? Unknown: 0000001000000000382e30200000000100000000
?
? Name: test_db
?
? DBA: testuser
?
? Unused:
00000000000000000000000000000000000000000000000000 0000000000 ?
?????????????????????????????????????????????????? ??????????????????????????????
It also shows the checkpoint, journal, dump and location information.

At 3:57 PM +0100 7/5/07, William wrote:
> > (There have always been rumors of a standalone config file dumper,
>> but I've never seen one, nor had the motivation to write one.)
>>
>> Karl
>
>Someone called Matthew Jones wrote one and advertised it on
>comp.databases.ingres newsgroup: ....
>My config file (for a Ingres II 2.0/0001 (su4.us5/00) 7097 db) has the
>following header details according to the program:
>
>??Header-(256
>bytes)??????????????????????????????????????????? ?????????????????
>? Section len: 256 Section type: 00000006
>?
>? CNF version: 00040001 DB version: 00000003
>?
>? Unknown: 00000003 Status: 00000001
>?
>? Open DB count: 00000000
>?
>? Unknown: 000000000000000200000002
>?
>? Database ID: 341e692b
>?
>? Unused: 00000000
>?
>? Extents: 5
>?
>? Last table ID: 13597
>?
>? Unknown: 0000001000000000382e30200000000100000000
...................................^^^^^^^^.^^^^^^ ^

Which shows us that the dbcmptlvl is 8.0 and the dbcmptminor is 1.
(The dbcmptlvl is 4 ascii characters, and the minor is the i4 that
follows.)

So if the OP can get this to run on his box, it can be used to figure
out the exact values needed for plugging into iidatabase.

Or, if he knows the exact original version, the cmptlvl/minor can
be determined at least in most cases.

Karl