Categorized in: 

ODI Performance Tuning

Insufficient memory setting for ODI Studio or the ODI Agent

This can be an issue if you have not increased the memory parameters associated with ODI Studio or the Agent and/or you see a memory related error.

For ODI Studio the change is made using the “odi.conf” or “ide.conf” files to increase the amount of Java memory available for the GUI.

The “ide.conf” file is located:

– in the “$ODI_HOME/jdeveloper/ide/bin (ODI 12c)

The “odi.conf” file is located:
– in the “$ODI_HOME/odi/studio/bin” directory (ODI 12c)

When using the standalone Agent the memory parameters are changed using the odiparams.bat/.sh file associated with the running Standalone Agent.

If you are running the JEE Agent then the parameters are controlled by the web server and changed there.

Inefficient Repository queries generated by ODI Modules / Bugs

This is highly unlikely. If you have installed the Repository database locally, confirmed that the bottleneck is not due to your network, and taken all steps to eliminate other possibilities, and still face unacceptable slow performance, please send a dump of your Repositories to Oracle Support for analysis.

Large number of executions under Execution tab

When you open an ODI Object, the information on all the tabs is loaded into the GUI.

As such, an Integration Interface with a very large number of executions in the “Executions” tab will take a proportionally long to open. In such cases, it may be useful to purge the ODI Journal.

Add new comment