FW: FW: defunct sqlexecd

Juergen, I looked into Intersolv's 32-bit ODBC drivers. You might(not sure) have to buy I-NET for the PC for every client you have. Plus the cost is enormous compared to Openlink 32 bit ODBC drivers. Mitchell Nelson AT&T Holmdel, NJ mitchell.nelson@att.com ---------- From: informix-list-owner[SMTP:rmy.emory.edu!informix-list-owner@caig2.att.att. com] Sent: Monday, November 11, 1996 8:17 PM To: informix-list Subject: Re: FW: defunct sqlexecd Nelson, Your problem does indeed sound similiar to mine. Since I can't seem to get answers from either Intersolv or Informix I have little choice but to try either Intersolv's 32-bit ODBC drivers or another vendors. Thanks, Juergen Nelson, Mitchell wrote: } } Juergen, } } I have the same problem with Visionware's 16 bit ODBC drivers. I and my } colleagues called up their Technical Support and they could not find why } it happens. I think it is because the request terminates(normally? or } abnormally? - cannot tell!) before ending the (Visionware's) server } process. (The server process spawns the sqlexec process). This only } happens MOST of the time, not ALL of the time. The only thing I could do, } is to periodically check for the Visionware server process and have my SA } do a kill -9 on them. } } Since, I am getting pretty sick of doing this and SCO (they own } Visionware SQL-Retriever) does not want to help us, I will be moving } Openlink's ODBC drivers. During my testing of Openlink ODBC drivers it } appears that orphaned processes do not happen! } } I think it is the type of ODBC architecture that was developed by the } different companies. } } I am running Informix SE 5.03 on a dual 486/50 NCR 3450 running NCR } MP-RAS 2.02 (NCR's version of SVR4). } } Mitchell Nelson } AT&T } Holmdel, NJ } mitchell.nelson@att.com } } ---------- } From: } informix-list-owner[SMTP:rmy.emory.edu!informix-list-owner@kcig1.att.att. } com] } Sent: Tuesday, November 05, 1996 2:17 PM } To: informix-list } Subject: defunct sqlexecd } } Informix SE 7.10.UC1 } Digital Unix 3.2d } Intersolv 16-bit ODBC drivers V2.11 for Windows } } Problem: } ======== } } Every time a client connects via ODBC to our Informix database a defunct } process is created which is a child of the sqlexecd dameon. } } These defunct processes continue to increase in numbers as users execute } queries, but never get cleaned up and eventually consume, for lack of a } better word, all the DEC's resources, ie I receive "unable to fork" } messages. The only way to return the system to normal is to kill the } sqlexecd daemon and restart it (or reboot). Once I kill the sqlexecd } dameon all the defunct process disappear. } } Can someone explain what might be causing this problem? Does it look } like a problem caused by the client or the server ? } } Thanks, } Juergen