error -349

An application and some long data loads have crashed with error -349 - database not open, or so I am told by the application people but have not seen the problem myself and do not have a reliable log of the errors. The problem seems to be intermittent and I cannot reproduce it. The version of Informix is 9.4 UC6 on AIX 5.2. Has anyone else had an issue with this? I don't see any error messages in the Informix log, nor anything odd occurring, like long checkpoints or anything like that. Is there somewhere else I could check?

First thing to do is to modify the app to display it's session id once it connects to the server. That way when it gets a strange error like this you can use onstat -g ses <session id> to see if the engine's view of the problem is different. The display includes the last SQLCODE error the session encountered on the server side. You can also see if the server thought the client had a database open. Art S. Kagel ----- Original Message ----- From: Mary Lacroix <ids@iiug.org> At: 7/20 19:18:16 An application and some long data loads have crashed with error -349 - database not open, or so I am told by the application people but have not seen the problem myself and do not have a reliable log of the errors. The problem seems to be intermittent and I cannot reproduce it. The version of Informix is 9.4 UC6 on AIX 5.2. Has anyone else had an issue with this? I don't see any error messages in the Informix log, nor anything odd occurring, like long checkpoints or anything like that. Is there somewhere else I could check? ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Hello, I'm not aware of how to diagnose what's causing a -349 error message other than to diagnose the application that is having the problem when it has the problem. An issue that I can think of which results in a -349 error is if all 4 of the following is true: 1) The application is on Windows 2) MDAC 2.8 SP1 is in use 3) The Informix OLEDB provider is being used 4) Transactions (DTC) is being used If the above describes your application, please contact Informix Support and request a fix for PTS bugs 173869 and 176969. For these bugs... MDAC 2.8SP1 now unenlists OLEDB connections, and Informix OLEDB provider depends on the previous behavior that once an OLEDB connection was enlisted it was never unenlisted... unenlisting an Informix OLEDB connection results in a -349 error upon further use of the connection. Thanks ----- Original Message ----- From: "ART KAGEL, ...." <kagel@bloomberg.net> To: <ids@iiug.org> Sent: Friday, July 21, 2006 7:23 AM Subject: Re: error -349 [7154] > > First thing to do is to modify the app to display it's session id once it > connects to the server. That way when it gets a strange error like this > you > can > use onstat -g ses <session id> to see if the engine's view of the problem > is > different. The display includes the last SQLCODE error the session > encountered > on the server side. You can also see if the server thought the client had > a > database open. > > Art S. Kagel > > ----- Original Message ----- > From: Mary Lacroix <ids@iiug.org> > At: 7/20 19:18:16 > > An application and some long data loads have crashed with error -349 - > database not open, or so I am told by the application people but have not > seen > the problem myself and do not have a reliable log of the errors. The > problem > seems to be intermittent and I cannot reproduce it. The version of > Informix is > 9.4 UC6 on AIX 5.2. Has anyone else had an issue with this? I don't see > any > error messages in the Informix log, nor anything odd occurring, like long > checkpoints or anything like that. Is there somewhere else I could check? > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > >