RE: 408 error

In my days in Informix technical support back in the very dim and distant past I used to be a bit if a specialist with 408 errors. They used to occur because the engine process had died and the application didn't know until they issued the next sql statement. You don't say what versions you are running of tool and engine. That would actually be quite useful if you think about it. As a guide to how to trace errors like this you will need to know which sql statements are performed when. Can you identify the session for the engine. If so do an onstat -g sql sid repeatedly while the application is running. If possible pause the program between opening the cursor and doing the fetch and look at onstat then. Then pause after each fetch. I did that once and the problem went away. We then took the pauses out and it never occurred again, but that's life! regards Malcolm -----Original Message----- From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of Floyd Wellershaus Sent: 15 August 2006 18:51 To: informix-list@iiug.org Subject: 408 error We are getting the 408 error about twice a month while running a program while doing a fetch cursor. Informix support really has no answers and suggests that we connect through tcp instead of through shared memory. We're racking our brains trying to find some pattern or reason why this happens. Does anyone have any experience solving for this error ? Thanks, floyd ======================== -<<Floyd Wellershaus>>- Database Administrator Unix Administrator email: fwellers@yahoo.com Home: 703-430-0805 Cell: 703-477-6045 ======================== http://www.one.org/