Using OTM for WO report generation results in oracle.apps.xdo.xdoexception (Doc ID 1533687.1)

Last updated on JULY 20, 2024

Applies to:

Goal

When using OTM for WO report generation the following error message is received:

oracle.apps.xdo.xdoexception: /tmp/ no space left on device. mount point /tmp/ was got 100% full.

After removing files from /tmp/ to free up space, the issue usually goes away.
The /tmp is used for temporary operations. It is a standard mount point provided by Linux and is being used by other activities as well.
Is there any way to change this /tmp to some other mount point for OTM to avoid such cases?

Looking at an OTM system, there are lots of properties that show a temp.dir.

glog.bipreports.properties:glog.bipreports.web.tempDir=/bipublisher/temp/
glog.bipreports.properties:glog.bipreports.web.ImageDir=$document.root$$glog.bipreports.web.tempDir$
glog.bipreports.properties:glog.bipreports.web.image.uri=http://$webserver$:$webserver.port$$glog.bipreports.web.tempDir$
glog.bipreports.properties:glog.bipreports.web.out=$document.root$$glog.bipreports.web.tempDir$
glog.bipreports.properties:glog.bipreports.app.tempDir=$temp.dir$/bipublisher/
glog.bipreports.properties:glog.bipreports.app.ImageDir=$glog.bipreports.app.tempDir$
glog.bipreports.properties:report_server_url=http://$webserver$:$webserver.port$$glog.bipreports.web.tempDir$
glog.bipreports.properties:glog.bipreports.content.path=$temp.dir$
glog.bipreports.properties:glog.bipreports.report.path=$temp.dir$

How can the one that might control it be identified?
Also, how would the $temp.dir$ be set?
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.