[Info-ingres] E_CL1F0C ... WTF
Martin Bowes
Hi All,
On Ingres 11.0.0 (a64.lnx/100) +p15212
E_CL1F0C PM configuration file is found to be in bad internal format
during the timezone initiation process
I have found a reference to this error code with respect to OpenRoad where the privileges.user.username had bad characters in the username but that is not the case in this instance as the usernames are ingres and root.
Any other suggestions?
Martin Bowes
David Quigley
Hi Marty,
David Quigley in Australia here; what does ‘WTF’ mean, is it one of those Ingres facilities like OPF, PSF, RDF etc?????
Cheers, David
Alex Hanshaw
I suspect this comes from an underlying PM_FILE_BAD error in PMmLoad in pm.c
** PM_FILE_BAD The specified file contained a syntax error.
If you use iigetres to retrieve value it reports syntax errors in a more detailed format. I deliberately mangled the following line:
ii.uksl-lvl2hanal04-64.dbms.private.*.cache.p4k_status# ON
You don’t have to know the mangled line. An iigetres on a different line still reports the mangled line:
> iigetres ii.uksl-lvl2hanal04-64.dbms.private.*.cache.p2k_status
Syntax error at line 824 of "/devsrc/main/m1/install/build/ingres/files/config.dat".
After seeing this error run an iigetres on any config item replacing your host name in the string above and iigetres shoud report which line has the syntax error.
Alex
Martin Bowes
Hi David,
WTF really should be a facility.
Go TIGES!
Marty
From: David Quigley [mailto:David....@actian.com]
Sent: 25 September 2017 09:38
To: Martin Bowes; info-...@lists.planetingres.org
Subject: RE: [Info-ingres] E_CL1F0C ... WTF
Hi Marty,
David Quigley in Australia here; what does ‘WTF’ mean, is it one of those Ingres facilities like OPF, PSF, RDF etc?????
Cheers, David
From: info-ingr...@lists.planetingres.org [mailto:info-ingr...@lists.planetingres.org] On Behalf Of Martin Bowes
Sent: Monday, September 25, 2017 6:29 PM
To: info-...@lists.planetingres.org
Subject: [Info-ingres] E_CL1F0C ... WTF
Martin Bowes
Hi Alex,
The only line iigetres bitches about is the one I deliberately mangelled.
I’ve managed to trace this down to a functions call to DBI. It seems to be generated at the connect attempt. It may be the DBD:Ingres was compiled against Ingres 10 and not Ingres11. I’ll check that out and see if this is the root of the problem.
Marty
From: Alex Hanshaw [mailto:Alex.H...@actian.com]
Sent: 25 September 2017 09:55
To: Martin Bowes; info-...@lists.planetingres.org
Subject: RE: [Info-ingres] E_CL1F0C ... WTF
I suspect this comes from an underlying PM_FILE_BAD error in PMmLoad in pm.c
** PM_FILE_BAD The specified file contained a syntax error.
If you use iigetres to retrieve value it reports syntax errors in a more detailed format. I deliberately mangled the following line:
ii.uksl-lvl2hanal04-64.dbms.private.*.cache.p4k_status# ON
You don’t have to know the mangled line. An iigetres on a different line still reports the mangled line:
> iigetres ii.uksl-lvl2hanal04-64.dbms.private.*.cache.p2k_status
Syntax error at line 824 of "/devsrc/main/m1/install/build/ingres/files/config.dat".
After seeing this error run an iigetres on any config item replacing your host name in the string above and iigetres shoud report which line has the syntax error.
Alex
From: info-ingr...@lists.planetingres.org [mailto:info-ingr...@lists.planetingres.org] On Behalf Of Martin Bowes
Sent: 25 September 2017 09:29
To: info-...@lists.planetingres.org
Subject: [Info-ingres] E_CL1F0C ... WTF
Martin Bowes
Bingo,
Recompiled DBD:Ingres against Ingres11 and the problem has disappeared.
Marty
PS. GO TIGES!!!
David Quigley
For those who may not understand Marty’s PS. Richmond (the TIGES) are playing off in the Australian AFL Grand Final this Saturday for the first time in 37 years and are a sentimental warm favorite to win.
Cheers, David
P.S. Go TIGES
Martin Bowes
Correction…35 years since our last appearance in a Grand Final. 37 years since our last victory. 37 long hard years of bitter despair!
EAT ‘EM ALIVE TIGERS!