Excessive Number Of Temporary Files Created During Execution Of An ODI Integration Interface Which Reads From a JMS Queue
Last updated on FEBRUARY 08, 2017
Applies to:Oracle Data Integrator - Version 10.1.3.6.4 and later
Information in this document applies to any platform.
When running an ODI Integration Interface which reads messages from JMS queue using Knowledge Modules such as the following:
- LKM : LKM JMS TO SQL
- IKM : IKM SQL CONTROL APPEND
a large number of *.tmp files (jmsXXXXX.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 Interface execution successfully terminates.
The configuration is set up in the following way:
- The ODI Integration Interface listens to the message queue and waits for messages to arrive.
- When a JMS message is received it is loaded into a table and loops back to the Interface again and listens for the next message.
- This looping continues until the max number of counts in the loop is reached at which point the Interface session will end. If the loop is defined as 1 then temporary files created in the Operating System Temporary directory are being removed. If If the loop count is more than 1 then only the last file created in the temporary directory is removed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms