My Oracle Support Banner

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

Last updated on MAY 06, 2022

Applies to:

Oracle Transportation Management - Version 6.2.7 and later
Information in this document applies to any platform.


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.$document.root$$glog.bipreports.web.tempDir$$webserver$:$webserver.port$$glog.bipreports.web.tempDir$$document.root$$glog.bipreports.web.tempDir$$temp.dir$/bipublisher/$$$webserver$:$webserver.port$$glog.bipreports.web.tempDir$$temp.dir$$temp.dir$

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


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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