My Oracle Support Banner

Excessive Number of Temporary Files Created During Execution of an ODI Mapping or Interface which Reads from a JMS Queue (Doc ID 1509286.1)

Last updated on MARCH 01, 2019

Applies to:

Oracle Data Integrator - Version and later
Information in this document applies to any platform.


When running an Oracle Data Integrator (ODI) 12c Mapping (or 11g/10g Integration Interface) which reads messages from JMS queue using knowledge modules such as the following:

... a large number of *.tmp files (jms<NUMBER>.tmp) are created (for example in the /var/tmp directory in Unix like systems) and appear to accumulate over time in the operating system temporary director and are not removed when the ODI execution successfully terminates.

The configuration is set up in the following way:

  1. The ODI Mapping / Interface listens to the JMS Message Queue, and waits for messages to arrive.
  2. When a JMS message is received it is loaded into a table and loops back to the Mapping / Interface again and listens for the next message.
  3. This looping continues until the max number of counts in the loop is reached ,at which point the ODI Session will end.

    If the loop is defined as 1 (one), then temporary files created in the Operating System Temporary directory are being removed.

    If If the loop count is greater than 1 (one), then only the last file created in the temporary directory is removed.




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.