Generation of huge files in the [install]/temp directory

[blom0344]

In the rarest of cases we observe that Cognos tends to generate massive sized files in the \temp directory. The reports themselves perform quite well (30 seconds) with 20-40 pages PDF output. The temp files seem to persist 25-30 minutes before being deleted again.
In one case we witnessed 1.2 Gb with a customer.

The observed error : USA-SOR-0005 Unable to write to....   appears in the fix list (FP1) of 8.4.1. However, I'd like to be sure this is not just a matter of applying a fix pack since this would be a logistical challenge   :-\

My own nagging suspicion is that something changed going from 8.1 to 8.4.1. Cognos nows makes it a habit to omit query items that are not used in the report or associated with a report object. Anyone got a clue why the temp files are generated and why they are so massive?

[MFGF]

I'd hazard a guess that these are used for queries where local processing is required.  Can you pin the temp files down to where a particular report is being run?  If so, you could take a look at the processing in the report to see what's going on...

Cheers!

MF.

[blom0344]

Yes, after running the data queries one for one , I isolated the one that peaked to more than 1 Gb locally. Looks as though 2 facts are involved with separate handling and subsequent restitching through a full outer join. The database does not handle this, I am just surprised that such small sets result in such huge temp files   >:(

[sir_jeroen]

It can be explained by the fact that in you case the results are joined (stitched) at a detail level and not on a aggregated level.
In this case local processing will query for all detail rows which are then processed locally by cognos.
So in your report there can e.g. 10 records be shown, but the can be based on e.g. 10000 records.

But local processing can also be caused by your database.
As for Oracle 9 and 10: Cognos doesn't allow Full Outer Joins.
Take a look at the file cogdmor.ini. There you can find lines like:

Code Select Expand


[Exceptions Joins]
Full_Outer=T
..
Full_Syntax=" FULL OUTER JOIN "

[Exceptions Joins ORACLE8.1.7]
Full_Outer=F
...

[Exceptions Joins ORACLE9.0.1]
Nested_Inner=T
Full_Outer=F

[Exceptions Joins ORACLE9.1]
Nested_Inner=F
Full_Outer=F

[Exceptions Joins ORACLE9.2.0]
Left_Pre=" "
Left_Post=" "
Right_Pre=" "
Right_Post=" "
Full_Pre=" "
Full_Post=" "
;Oracle 9.2 has data integrity issue (trakker 368200) with
;full outer join. Problem is fixed in Oracle 10 release.
Full_Outer=F
Nested_Inner=F

[Exceptions Joins ORACLE10.1.0]
Full_Outer=F


As you can see the FULL_OUTER joins are disabled for 9 and 10.1