ODI ECC KM Fills /usr/sap Directory With Work Files
(Doc ID 2221072.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Data Integrator - Version 10.1.3.6.9 and later
Information in this document applies to any platform.
ODI interface extracts data out of SAP ECC.
When running an ODI interface that is using the ECC SAP KM's with using the FTP transfer method specified in the KM options.
The work files that are generated on the CI server in /usr/sap and filling up the directory.
The KM will extract a ZODI_<ODI_PROGRAM_NAME>.txt file into /usr/sap//DVEBMGS02/work directory on the ECC CI.
Then through the ODI SAP KM, SAP will transfer it to a server where the ODI agent resides to load into a target system.
The ZODI_* files that are getting generated by the SAP KM and are filling up the filesystem on the CI server.
When the CI fills up SAP stops.
How to control what directory these ZODI_* files gets created prior to SAP transferring them over to the target system?
Is there a way to specify a different directory instead of /usr/sap or is there a setting to clean up the file after the integration is complete?
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|