Re: [Info-ingres] I know this topic has been talked about before but...

Hi,

If your program run without problem since years and now fall with this
error, perhap's there is a loop somehere drived directly by data in tables.

Does the data grow in a massive way in the last week/month and/or some
situation in the data give you some cartesian product in some query (to
explain the amount of data manipulated), or something in this area ...

OR

Has the system configuration changed recently ?

HTH,
Jean-Pierre

2006/8/29, M.Cressey <M.Cressey@xxxxxxxxxx>:

I suspect your program has a bug and is running out of file descriptors
and so cannot open the Ingres message file when it needs to. The
following bit of sample code reproduces the same problem on my Solaris
machine:


#include <fcntl.h>

int main(void)
{
exec sql begin declare section;
int t=1;
exec sql end declare section;
int i;

while (1)
{
i=open("silly.sc",O_RDONLY); /* Never close(i); */
printf("i=%d\n",i);

exec sql connect 'iidbdb' session :t;
t++;
exec sql commit;
}
return 0;
}

Running this gives:
i=3
i=6
i=8
i=10
...
...
i=250
i=252
i=254
ERlookup: Error accessing message text:
Error opening message file.
Check II_MSGDIR and II_LANGUAGE logical variables.
Check messages files in the installation.

INGRES ERROR: 9961473


-----Original Message-----
From: info-ingres-admin@xxxxxxxxxxxxxxx
[mailto:info-ingres-admin@xxxxxxxxxxxxxxx] On Behalf Of JIMC
Sent: 29 August 2006 13:18
To: info-ingres@xxxxxxxxxxxxxxx
Subject: [Info-ingres] I know this topic has been talked about before
but...

We have a C program with QUEL that starts up at the beginning of the
day and runs all day. After a few hours of running we get the
following error:

ERlookup: Error accessing message text:
Error opening message file.
Check II_MSGDIR and II_LANGUAGE logical variables.
Check messages files in the installation.

Ingres ERROR: 9961473

We then start the program up again and it run for a few hours more and
eventually fails again.

I asked the programmer to echo $II_SYSTEM for each connection to ingres
and its value is correct.

Why would we get this error sporadically ?

_______________________________________________
Info-ingres mailing list
Info-ingres@xxxxxxxxxxxxxxx
http://mailman.cariboulake.com/mailman/listinfo.py/info-ingres

_______________________________________________
Info-ingres mailing list
Info-ingres@xxxxxxxxxxxxxxx
http://mailman.cariboulake.com/mailman/listinfo.py/info-ingres




--
Jean-Pierre Zuate
+33(0)6 11 40 11 09

Relevant Pages