Re: Assert Failed in informix.log

I tracked down a very similar problem with a temp table in an ESQL/C module. Our program contained a loop with three basic components. The first one checked and updated some control tables. This was in a begin work - commit work transaction. The second portion performed a select distinct into a temp table. It then checked to see if the temp table contained rows and, if so, processed them. Since the temp table was not being updated, it was not in a transaction. The third portion did the processing of the info from the temp table. It was in a transaction. This whole thing executed every 30 seconds. The problem boiled down to the first begin work statement. After the process went through its first cycle, which included dropping the temp table and freeing all cursors, the program would generate an informix assert failure that I could track to the temp table. The strange part was that it reported it when you hit the begin work. I talked to tech support and they indicated that someone else reported it as well. You'll never guess what the recommendation was -- ignore it! They said it was corrected in later versions and carried no ill effects. It was true that the program did not seem to suffer any in my case either. However, after a number of these assertion failures, the engine would segv. To me that is an ill effect. Our solution was to frame the temp table code with a transaction. Problem gone. Can't explain why. Hope this helps. cludwigsen@harrahs.com Chuck Ludwigsen Harrah's Entertainment, Inc. +----------------------------------------------------+ :Proud daddie of my 7 lb 14 oz baby girl born 8/15/96: +----------------------------------------------------+