Logs fill during SELECT?

My question concerns Informix 7.3 on NT. I have a database at one of my clients sites where the logs keep filling and ontape -a has to be done every so often. The cause for the fillup wasn'tclear until yesterday when we discovered that when presenting the server with a complex query (i.e. joins or nested queries etc), it causes the logs to fill. The database has unbuffered logging mode and from what it looks like, the server is using implicit transactions on its temporary tables during the execution of the query. These transactions, depending on the query's complexity, cause the logs to fill up way too early than expected. I want to emphasize that we're not using SELECT ... INTO TEMP or FOR UPDATE, only a query to get the data and nothing more. My question is, presuming this the reason for the logs to fill, what can be done to stop the logs from filling up? Increase their size? We tried that and they just keep filling. Can I prevent the server from using transactions on the temporary tables? Any kind of help would be greatly appreciated. -- Itamar Haber M.N.S. Ltd.

Do you have tempdb spaces and are they in DBSPACETEMP? Are you using the PSORT_DBTEMP variable to move sort-work files out of the database and into filesystem space where they would not be logged? Art S. Kagel Itamar Haber wrote: > > My question concerns Informix 7.3 on NT. > > I have a database at one of my clients sites where the logs keep filling and > ontape -a has to be done every so often. The cause for the fillup wasn't> clear until yesterday when we discovered that when presenting the server > with a complex query (i.e. joins or nested queries etc), it causes the logs > to fill. > > The database has unbuffered logging mode and from what it looks like, the > server is using implicit transactions on its temporary tables during the > execution of the query. These transactions, depending on the query's > complexity, cause the logs to fill up way too early than expected. > > I want to emphasize that we're not using SELECT ... INTO TEMP or FOR UPDATE, > only a query to get the data and nothing more. > > My question is, presuming this the reason for the logs to fill, what can be > done to stop the logs from filling up? Increase their size? We tried that > and they just keep filling. Can I prevent the server from using transactions > on the temporary tables? > > Any kind of help would be greatly appreciated. > > -- > Itamar Haber > M.N.S. Ltd.