Xdo_http_*.dt in /tmp

Question

Hello All,
I tried running the Oracle Base "Accounts Payable Trial Balance(1)" request on our newly upgraded R12.1.3 (test) system. This is by detail version of the report.
The request had to be killed since, it started filling up the /tmp space. One of the file system is at 100%. The request created a large "xdo_http_*.dt" file under /tmp. This is in addition to a large req#.out file for the conc. request.
Does any one know what that file is? Why is getting generated? Any resources, pointers about that file are appreciated.
Some details:
Oracle Apps R12.1.3
OS: IBM AIX on POWER Systems (64-bit) AIX 6.1
DB Version: 11.1.0.x.
Thanks,
Monkey
Edited by: OAF_Monkey on Mar 2, 2012 9:49 AM

Answer 1

With this new data template, the conc. request initially errored out with the following message (versus the base report keeps on running filling up the file system to 100% with out any error message in the OPP log or the conc. req. log...necessiating the termination of the req):
JVMDUMP013I Processed dump event "systhrow", detail "java/lang/OutOfMemoryError".
****Warning!!! Due to high volume of data, got out of memory exception...***
****Please retry with scalable option or modify the Data template to run in scalable mode...***
JVMDUMP006I Processing dump event "systhrow", detail "java/lang/OutOfMemoryError" - please wait.Please see scalability options as per these docs.
How to Configure the Planning Detail Report in Release 12 for Large Reports [ID 1082672.1]
How to Configure the Account Analysis Report in Release 12 for Large Reports [ID 737311.1]
How to Configure the Planning Detail Report in Release 12 for Large Reports [ID 1082639.1]
Below is what I've observed:
1. The data that gets written to the 'gt' table is only "1794279" records. I believe the total of these records matches with the output displayed when the report is run in Summary mode ( but I have no way of validating that...)
2. When the conc. req runs, it is populating the 'gt' table. It is only after it is trying to run my select statement in the data template that it failed with the above message
3. When it runs the select statement in the data template, it still generates "xdo_http_X.dt" file that keeps growing up to 1152773621 (about 1.15gig). At this point the
%Used in the file system grows to 29% and then the req. failed with the above message.
I referred to the notes 390968.1 and 758143.1 for help. Per the note 390968.1, I tried the conc. request with option -Xmx2048m and it finally completes ok (it failed with JVM options for 512mb and 1gig earlier). The out file is around 1.9 gig which I cannot open on my PC (which is kinda pre-historic)
My Questions:
1. Is there any other mode like scalable mode in which such ‘supposedly’ large reports can be run? Pls. note that my data template has the following statement:
<properties>
<property name="scalable_mode" value="on" />
</properties>
<properties><property name="debug_mode" value="on" /></properties>
<properties>
<property name="db_fetch_size" value="20" />
</properties> R12: Troubleshooting Known XML Publisher and E-Business Suite (EBS) Integration Issues [ID 1410160.1] -- === 2.1 XML Data generation ===
2. Now even if the conc. request completes successfully, if the out file itself cannot be opened, how will the rtf template open the output? Should such reports be run as ‘pdf’ so that the final output can be opened?Yes.
3. How much RAM is need on the user PC to be able to open up such large outputs?This should be independent of the memory settings at the application/database tier node. You could download the output file from the application server and see how much is needed to open the output file.
Pls. help……I am kinda lost now. Have you tried to log a SR?
Thanks,
Hussein