-157 ISAM error: Interrupted ISAM call

Hello everyone, In a scheduling process done by one of the applications that connect to our Informix instance, we had many errors with the following message: "ERROR [IX000] [IBM][IDS/UNIX64] Statement interrupted by user. (-157 ISAM error: Interrupted ISAM call) -157 ISAM error: Interrupted ISAM call. An interrupt that was detected from client process has terminated the operation. Restart the operation." I didn't find much information about this error, and I would like to know what may have caused it. I guess that it is generated by an interruption received from the client application side during the scheduling process, and that it is not caused by a problem in Informix, but I would like to know if anyone can confirm this information. Thanks! ------------------------------ Celso Freitas ------------------------------ #Informix

Any kind of query timeout at play here? The db server session(s) must have received an interrupt signal in the middle of processing some SQL, and normally such signalling comes from client side. JDBC setQueryTimeout() might be a candidate, but we don't even know if JDBC is involved. ------------------------------ Andreas Legner ------------------------------