IDS 9.30 consumes too much temp dbspace

Has anyone got a similar problem ? We use Crystal report 8.x to create a complex report joining a number of tables to get results. For some reasons, the temp dbspace (1 GB) and most of root dbspace was almost consumed in the creation of this report. Sometimes the tempspace was not released in time. It took 5-10 minutes to release tem space after termination of the report. Consequently, running any reports after that caused error in allocating temp dbspace. Is this because we set set PDQ onconfig params wrongly ? or Improper setup of log files configuration ? Please help. Many thanks in advance Viet Tran sending to informix-list

There is a bug in 9.30.UC3 where the temporary dbspace on the secondary server in a HDR pair is not released after use. Can be worked around by bouncing the secondary. I believe this is fixed, certainly in 9.40.UC3. Crystal Reports can also be very inefficient as many if not all of your selection criteria are applied by Crystal itself and not by using SQL. Thus queries can involve processing a lot of data by the DBMS and thus can use a lot of temporary space. We have worked around this "feature" of Crystal by selecting our data from a view which means that the view definition can exclude data we're not interested in and the DBMS does not have to work so hard. Ben.