407: Error number zero received from the sqlexec process.

After months with no problem, I now get this error each time I try to launch an "update statistics high". It runs for about 10 minutes, and then stops with the error message in the subject. After dbexport/dbimport of the database, the problem is still the same but occurs after more than one hour. Update statistics medium works well in 10 minutes but I have some querieswhich take too much time to complete now. Error code 407 means: "This internal error indicates a problem in the communication between the database server and the library functions that call it. Make sure that your program software is compatible with the database engine in use. If the error recurs, note all circumstances and contact Informix Technical Support." The program software which runs "update statistics high" is dbaccess. So, it is compatible with the database engine. Some usefull informations about my system: Informix 7 SE on HP-UX 11 The database is a datawarehouse. Nearly all the tables are deleted and recreated each day. Some help would be usefull. Thanks. Regis

R'gis wrote: > After months with no problem, I now get this error each time I try to launch > an "update statistics high". > It runs for about 10 minutes, and then stops with the error message in the > subject. > After dbexport/dbimport of the database, the problem is still the same but > occurs after more than one hour. > Update statistics medium works well in 10 minutes but I have some queries> which take too much time to complete now. > > Error code 407 means: > > "This internal error indicates a problem in the communication between the > database server and the library functions that call it. Make sure that your > program software is compatible with the database engine in use. If the error > recurs, note all circumstances and contact Informix Technical Support." > > The program software which runs "update statistics high" is dbaccess. So, it > is compatible with the database engine. > > Some usefull informations about my system: > > Informix 7 SE on HP-UX 11 > The database is a datawarehouse. Nearly all the tables are deleted and > recreated each day. > > Some help would be usefull. > Thanks. SE 7.what? HP-UX 11.what? (00 or 11 aka i)? Your sqlexec process is likely crashing (though -408 is the more normal error for that) - so maybe it would be a good idea to run secheck on the tables in the database. It would also be a good idea to look at whether you have the most current version of SE. I'm not sure that SE pays much attention to statistics low, medium, high, etc -- I thought none, but I'm open to correction on it. -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2003.04 -- http://dbi.perl.org/

> R'gis wrote: > > After months with no problem, I now get this error each time I try to launch > > an "update statistics high". > > It runs for about 10 minutes, and then stops with the error message in the > > subject. > > After dbexport/dbimport of the database, the problem is still the same but > > occurs after more than one hour. > > Update statistics medium works well in 10 minutes but I have somequeries > > which take too much time to complete now. > > > > Error code 407 means: > > > > "This internal error indicates a problem in the communication between the > > database server and the library functions that call it. Make sure that your > > program software is compatible with the database engine in use. If the error > > recurs, note all circumstances and contact Informix Technical Support." > > > > The program software which runs "update statistics high" is dbaccess. So, it > > is compatible with the database engine. > > > > Some usefull informations about my system: > > > > Informix 7 SE on HP-UX 11 > > The database is a datawarehouse. Nearly all the tables are deleted and > > recreated each day. > > > > Some help would be usefull. > > Thanks. > > SE 7.what? HP-UX 11.what? (00 or 11 aka i)? > > Your sqlexec process is likely crashing (though -408 is the more > normal error for that) - so maybe it would be a good idea to run > secheck on the tables in the database. It would also be a good idea > to look at whether you have the most current version of SE. > > I'm not sure that SE pays much attention to statistics low, medium, > high, etc -- I thought none, but I'm open to correction on it. SE 7.24.UC8A; HP-UX 11.00 Some queries are really faster after update statistics high, so it is important that I can continue to run it. I wrote a script which runs an update statistics high for each table in the database separately. I found the only one table on which the process fails with error 407. Same problem after drop/create/load from. secheck found no error. Here is the schema of the table: drop table tttxt010; create table tttxt010( ctxt integer, clan char(1), seqe integer, text char(240) ); load from "/usr/data/load/mk/ttttxt010700.S"delimiter "$" insert into tttxt010; create index tttxt010_ix01 on tttxt010 (ctxt); create index tttxt010_ix02 on tttxt010 (clan); create index tttxt010_ix03 on tttxt010 (seqe);