Posted by : Arjun Lagisetty Tuesday, January 6, 2015

ODI is a very developer friendly tool when it comes to development because of its graphical nature.  But when something goes awry, Operator is not useful beyond certain level of debugging. To get debug at the application level an ODI personnel should understand structure of the ODI server side logs to be able to debug infrastructure issues.


Standalone Agent:

For standalone agent logging is pretty straightforward,

All the Log files for the Stand alone agent are present in directory


Log file names and comments

Log file name Generated from shell file Comments


  All the agent logs are written to this file. Connectivity error, startup, shutdown messages etc..















Configuration for Standalone Agent logging is described in this  blog post (Agent Logging)


Web Logic (J2EE) Agent:


ODI Component Log file location:

In J2EE agent is a part of odi managed server, where ODI agent is just a deployment

odiagent.log files are located in the following three locations (under each managed server and admin server – it comes along with the template installation in the domain) Even though the files are present in all the managed server. Its populated actively in the managed server folder where the deployment is active.


2015-01-06 17_19_00-_u01_app_test_fmw


Managed Server Log file location:

All the managed servers write the output for all the deployments to managed server log files. Checking these files is a good start for ODI infrastructure debugging issue.

2015-01-06 17_29_37-_u01_app_test_fmw



Studio Log file location:

Studio log files are written in the directory with the following name


2015-01-06 17_43_15-C__WINDOWS_system32_cmd.exe

Leave a Reply

Subscribe to Posts | Subscribe to Comments

Popular Post


Blog Archive

Copyright © ODI Pundits - Oracle Data Integrator - Maintained by Arjun Lagisetty