Impacts Of The Physical Architecture On Performance Of ODI Mappings And Integration Interfaces
Last updated on JUNE 28, 2016
Applies to:Oracle Data Integrator - Version 10.1.3.2.0 and later
Information in this document applies to any platform.
The execution of an Oracle Data Integrator (ODI) Mapping / Integration Interface is excessively slow, despite the fact that both the staging area and target Datastore are physically on the same Data Server.
Further analyze of the execution demonstrates that ODI uses a resource intensive loading phase.
Is the loading phase really necessary and how is it possible to optimize the operation?
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