Hi All,

As part of a Disaster Recovery Plan I'm in the process of trialling a Perl based configuration file editor.

All I'm changing is the database extent directory. I'm not adding new locations, I'm simply amending the path strings to reflect the new host and installation.

Other than the path name, I'm changing only the integer field which holds the path length.

The amended file is then written to disk. It has the same length as the original. My editor has no problem re-reading the amended file and displayingits contents....but Ingres sure doesn't like it!

An infodb bombs out with E_DM923A_CONFIG_OPEN_ERROR

And in the errlog we see:
E_DM923C_CONFIG_FORMAT_ERROR Error in configuration file format.
E_DM923A_CONFIG_OPEN_ERROR Error occurred opening configuration file (aaaaaaaa.cnf).


Anyone got any idea what else I need to change?

Martin Bowes

Hi Marty,

You usually get this if another session is in CBF or the like & hence
has the config.dat locked.

Regards,

Ian



From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of
Martin Bowes
Sent: 25 November 2011 11:32
To: Ingres and related product discussion forum
Subject: [Info-Ingres] Editing a configuration file



Hi All,



As part of a Disaster Recovery Plan I'm in the process of trialling a
Perl based configuration file editor.



All I'm changing is the database extent directory. I'm not adding new
locations, I'm simply amending the path strings to reflect the new host
and installation.



Other than the path name, I'm changing only the integer field which
holds the path length.



The amended file is then written to disk. It has the same length as the
original. My editor has no problem re-reading the amended file and
displaying its contents....but Ingres sure doesn't like it!



An infodb bombs out with E_DM923A_CONFIG_OPEN_ERROR



And in the errlog we see:

E_DM923C_CONFIG_FORMAT_ERROR Error in configuration file format.

E_DM923A_CONFIG_OPEN_ERROR Error occurred opening configuration file
(aaaaaaaa.cnf).





Anyone got any idea what else I need to change?



Martin Bowes

Only what I can tell to this is:
It incarnates the need of "finddbs" tool


--
bilgihan

Yep. I checked the open source and that was definitly the gist of what I read in dm0c.c etc.

This has me puzzelled! I've opened and closed the files to edit them. Nothing else should be holding a lock on them so I'm stumped. Is a lock status written into the config file itself? Something that's says 'Hi I've been opened by application X.'?

Marty

From: Ian Kirkham [mailto:Ian.Kirkham (AT) actian (DOT) com]
Sent: 25 November 2011 14:36
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] Editing a configuration file

Hi Marty,
You usually get this if another session is in CBF or the like & hence has the config.dat locked.
Regards,
Ian

From: info-ingres-bounces (AT) kettleriver...ting (DOT) com [mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Martin Bowes
Sent: 25 November 2011 11:32
To: Ingres and related product discussion forum
Subject: [Info-Ingres] Editing a configuration file

Hi All,

As part of a Disaster Recovery Plan I'm in the process of trialling a Perl based configuration file editor.

All I'm changing is the database extent directory. I'm not adding new locations, I'm simply amending the path strings to reflect the new host and installation.

Other than the path name, I'm changing only the integer field which holds the path length.

The amended file is then written to disk. It has the same length as the original. My editor has no problem re-reading the amended file and displayingits contents....but Ingres sure doesn't like it!

An infodb bombs out with E_DM923A_CONFIG_OPEN_ERROR

And in the errlog we see:
E_DM923C_CONFIG_FORMAT_ERROR Error in configuration file format.
E_DM923A_CONFIG_OPEN_ERROR Error occurred opening configuration file (aaaaaaaa.cnf).


Anyone got any idea what else I need to change?

Martin Bowes

I am not sure that config.dat is related to this.
I believe that the cnf has a special format.
Whenever I needed to do this I did it with a hex editor (If needed to do manually)
There was also in support an editor for cnf written in C IIRC so if still around maybe you can get it



On Nov 25, 2011, at 9:07 AM, Martin Bowes wrote:

FYI. The config file structure is in:
$ING_SRC/back/dmf/hdr/dm0c.h
$ING_SRC/back/dmf/dmp/dm0c.c.

But best of luck reading the code!

Marty
From: Armand Pirvu (gmail) [mailto:armand.pirvu (AT) gmail (DOT) com]
Sent: 25 November 2011 15:27
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] Editing a configuration file

I am not sure that config.dat is related to this.
I believe that the cnf has a special format.
Whenever I needed to do this I did it with a hex editor (If needed to do manually)
There was also in support an editor for cnf written in C IIRC so if still around maybe you can get it



On Nov 25, 2011, at 9:07 AM, Martin Bowes wrote:


Yep. I checked the open source and that was definitly the gist of what I read in dm0c.c etc.

This has me puzzelled! I've opened and closed the files to edit them. Nothing else should be holding a lock on them so I'm stumped. Is a lock status written into the config file itself? Something that's says 'Hi I've been opened by application X.'?

Marty

From: Ian Kirkham [mailto:Ian.Kirkham (AT) actian (DOT) com]
Sent: 25 November 2011 14:36
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] Editing a configuration file

Hi Marty,
You usually get this if another session is in CBF or the like & hence has the config.dat locked.
Regards,
Ian

From: info-ingres-bounces (AT) kettleriver...ting (DOT) com> [mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Martin Bowes
Sent: 25 November 2011 11:32
To: Ingres and related product discussion forum
Subject: [Info-Ingres] Editing a configuration file

Hi All,

As part of a Disaster Recovery Plan I'm in the process of trialling a Perl based configuration file editor.

All I'm changing is the database extent directory. I'm not adding new locations, I'm simply amending the path strings to reflect the new host and installation.

Other than the path name, I'm changing only the integer field which holds the path length.

The amended file is then written to disk. It has the same length as the original. My editor has no problem re-reading the amended file and displayingits contents....but Ingres sure doesn't like it!

An infodb bombs out with E_DM923A_CONFIG_OPEN_ERROR

And in the errlog we see:
E_DM923C_CONFIG_FORMAT_ERROR Error in configuration file format.
E_DM923A_CONFIG_OPEN_ERROR Error occurred opening configuration file (aaaaaaaa.cnf).


Anyone got any idea what else I need to change?

Martin Bowes
_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulti...ting (DOT) com>
http://ext-cando.kettleriverconsulti...fo/info-ingres

On Nov 25, 2011, at 6:32 AM, Martin Bowes wrote:

DM923C looks like an extent count mismatch. There's only one of them in dm0c.c.
There are a few conditions that could cause the mismatch. If I were doing it,
I'd probably whip up a server with dm0c compiled debug, and step through that
loop to see which bit of the cnf file is buggered up.

Karl

Ah I see the problem....

There are seven integers at the end of the path string. I'd set them all to zeroes rather than preserve the original contents. Whoops.

So now my edit works and infodb likes the result but my recovery now fails with:
E_DM130C_RFP_DELETE_ALL Error deleting files from directory before restoring from checkpoint.

What I'd forgotten was that my edited cnf becomes the rfc and then the rollforwarddb extracts an un-edited cnf from the checkpoint tar file. Their disagreement on directory paths must be creating a conniption fit.

OK...I think I'll have to tackle this by making a special template file (cktmpl.def) that will monster the unedited cnf file before the delete phase starts via the BRDD: ...

Sometimes the best we can hope for is that the lesser of two evils is also the funniest.

Marty

-----Original Message-----
From: Karl Schendel [mailto:schendel (AT) kbcomputer (DOT) com]
Sent: 25 November 2011 23:59
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] Editing a configuration file


On Nov 25, 2011, at 6:32 AM, Martin Bowes wrote:

DM923C looks like an extent count mismatch. There's only one of them in dm0c.c.
There are a few conditions that could cause the mismatch. If I were doing it,
I'd probably whip up a server with dm0c compiled debug, and step through that
loop to see which bit of the cnf file is buggered up.

Karl



_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres

Marty,

We've been editing CNF files for many years as part of batch processes and
we've never had to do that as part of the cktmpl file.

If you make the changes to the cnf file in the data area and the dmp area
AND also the c*.dmp file, it will do the delete perfectly.

Cheers,
Lin



Internet
martin.bowes (AT) ctsu (DOT) ox.ac.uk
Sent by: info-ingres-bounces (AT) kettleriver...ting (DOT) com
28/11/2011 11:36
Please respond to
info-ingres (AT) kettleriverconsulting (DOT) com


To
info-ingres (AT) kettleriverconsulting (DOT) com
cc
karl.schendel (AT) ingres (DOT) com
Subject
Re: [Info-Ingres] Editing a configuration file






Ah I see the problem....

There are seven integers at the end of the path string. I'd set them all
to zeroes rather than preserve the original contents. Whoops.

So now my edit works and infodb likes the result but my recovery now fails
with:
E_DM130C_RFP_DELETE_ALL Error deleting files from directory before
restoring from checkpoint.

What I'd forgotten was that my edited cnf becomes the rfc and then the
rollforwarddb extracts an un-edited cnf from the checkpoint tar file.
Their disagreement on directory paths must be creating a conniption fit.

OK...I think I'll have to tackle this by making a special template file
(cktmpl.def) that will monster the unedited cnf file before the delete
phase starts via the BRDD: ...

Sometimes the best we can hope for is that the lesser of two evils is also
the funniest.

Marty

-----Original Message-----
From: Karl Schendel [mailto:schendel (AT) kbcomputer (DOT) com]
Sent: 25 November 2011 23:59
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] Editing a configuration file


On Nov 25, 2011, at 6:32 AM, Martin Bowes wrote:

and installation.
displaying its contents....but Ingres sure doesn't like it!
DM923C looks like an extent count mismatch. There's only one of them in
dm0c.c.
There are a few conditions that could cause the mismatch. If I were doing
it,
I'd probably whip up a server with dm0c compiled debug, and step through
that
loop to see which bit of the cnf file is buggered up.

Karl



_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres


_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres


__________________________________________________ _________
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is prohibited.

Please refer to http://www.bnpparibas.co.uk/en/infor...de=ECAS-845C5H for additional disclosures.

Hi Lin,

Thanks for that. I'll try monkeying with the c*.dmp first and see if that shakes the problem loose.

Marty

From: lin.a.bradbrook (AT) uk (DOT) bnpparibas.com [mailto:lin.a.bradbrook (AT) uk (DOT) bnpparibas.com]
Sent: 28 November 2011 11:59
To: info-ingres (AT) kettleriverconsulting (DOT) com
Cc: karl.schendel (AT) ingres (DOT) com; info-ingres (AT) kettleriverconsulting (DOT) com; info-ingres-bounces (AT) kettleriver...ting (DOT) com
Subject: Re: [Info-Ingres] Editing a configuration file


Marty,

We've been editing CNF files for many years as part of batch processes and we've never had to do that as part of the cktmpl file.

If you make the changes to the cnf file in the data area and the dmp area AND also the c*.dmp file, it will do the delete perfectly.

Cheers,
Lin

Internet
martin.bowes (AT) ctsu (DOT) ox.ac.uk

Sent by: info-ingres-bounces (AT) kettleriver...ting (DOT) com

28/11/2011 11:36
Please respond to
info-ingres (AT) kettleriverconsulting (DOT) com


To

info-ingres (AT) kettleriverconsulting (DOT) com

cc

karl.schendel (AT) ingres (DOT) com

Subject

Re: [Info-Ingres] Editing a configuration file







Ah I see the problem....

There are seven integers at the end of the path string. I'd set them all tozeroes rather than preserve the original contents. Whoops.

So now my edit works and infodb likes the result but my recovery now fails with:
E_DM130C_RFP_DELETE_ALL Error deleting files from directory before restoring from checkpoint.

What I'd forgotten was that my edited cnf becomes the rfc and then the rollforwarddb extracts an un-edited cnf from the checkpoint tar file. Their disagreement on directory paths must be creating a conniption fit.

OK...I think I'll have to tackle this by making a special template file (cktmpl.def) that will monster the unedited cnf file before the delete phase starts via the BRDD: ...

Sometimes the best we can hope for is that the lesser of two evils is also the funniest.

Marty

-----Original Message-----
From: Karl Schendel [mailto:schendel (AT) kbcomputer (DOT) com]
Sent: 25 November 2011 23:59
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] Editing a configuration file


On Nov 25, 2011, at 6:32 AM, Martin Bowes wrote:

DM923C looks like an extent count mismatch. There's only one of them in dm0c.c.
There are a few conditions that could cause the mismatch. If I were doing it,
I'd probably whip up a server with dm0c compiled debug, and step through that
loop to see which bit of the cnf file is buggered up.

Karl



_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres


_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres


__________________________________________________ _________
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is prohibited.

Please refer to http://www.bnpparibas.co.uk/en/infor...de=ECAS-845C5H for additional disclosures.