Skip Headers
Oracle® Fusion Middleware Installation Guide for Oracle Data Integrator
11g Release 1 (

Part Number E16453-06
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
PDF · Mobi · ePub

H Troubleshooting

This appendix describes solutions to common problems that you might encounter when installing Oracle Data Integrator. It contains the following sections:

H.1 General Troubleshooting Tips

If you encounter an error during installation:

H.2 Installation and Configuration Log Files

This section contains information about the log files that are created when running the Oracle Data Integrator installer and the Oracle Fusion Middleware Configuration Wizard. Log files contain information that can help you troubleshoot problems with your installation or configuration.

H.2.1 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location/log (on UNIX operating systems) or Oracle_Inventory_Location\logs (on Windows operating systems) directory. On UNIX operating systems, if you do not know the location of your Oracle Inventory directory, you can find it in the oraInst.loc file in the following directories (default locations):

  • Linux: /etc/oraInst.loc

  • HP-UX and Solaris: /var/opt/oracle/oraInst.loc

On Windows operating systems, the location for the inventory directory is C:\Program Files\Oracle\Inventory\logs. If you are using a 32-bit installer on a 64-bit Windows machine, the inventory directory is C:\Program Files (x86)\Oracle\Inventory\logs.

The following install log files are written to the log directory:

  • installdate-time-stamp.log

    This is the main log file.

  • installdate-time-stamp.out

    This log file contains the output and error streams during the installation.

  • installActionsdate-time-stamp.log

    This file is used by the installer GUI to keep track of internal information.

  • installProfiledate-time-stamp.log

    This log file contains the overall statistics like time taken to complete the installation, as well as configuration, memory and CPU details.

  • oraInstalldate-time-stamp.log

    This log file contains the output stream of the copy session.

If you start the installer with the -printtime parameter, the timeTakendate-time-stamp.log and timedate-time-stamp.log files are created in the same directory:

  • timeTakendate-time-stamp.log

    This file contains information for the amount of time taken to move between screens (applicable for GUI installations only).

  • timedate-time-stamp.log

    This file contains time information for the copy session.

If you start the installer with the -printmemory parameter, the memorydate-time-stamp.log file is created. This file contains memory usage information for the copy session.

H.2.2 Configuration Log Files

To create a log file of your configuration session, start the Configuration Wizard with the -log option, as shown below:

On UNIX operating systems:

./ -log=log_filename -log_priority=log_level

On Windows operating systems:

config.cmd -log=log_filename -log_priority=log_level

See Table H-1 for more details about the -log and -log_priority options.

Table H-1 Configuration Wizard Log File Options

Parameter Description


Specify the location of your log file.

If you specify an absolute path with your log_filename then your log file will be created there. If you only specify a file name with no path, then the log files are created in the MW_HOME/logs (on UNIX operating systems) or MW_HOME\logs (on Windows operating systems) directory.

Other values that can be specified with -log are:

  • stdout

    This writes the error message to the standard output stream.

  • stderr

    This writes the error messages to the standard error stream.

  • disable

    This disables default logging so that no log files are generated in MW_HOME/logs (on UNIX operating systems) or MW_HOME\logs (on Windows operating systems).


Specify the level of detail you want included in your logs.

The acceptable values are listed below, from most detailed to least detailed:

  • debug

  • info

  • warning

  • error

  • fatal

H.3 Keeping Track of Your JRE Location

The JRE location used by the installer is stored in the ODI_ORACLE_HOME/oui/oraparam.ini (on UNIX operating systems) or ODI_ORACLE_HOME\oui\oraparam.ini (on Windows operating systems) file. This file is used by OPatch and Oracle Universal Installer (OUI) to determine the location of your preferred JRE.

It is possible to change the location of your JRE (for example, the JRE directory is moved out of the Middleware home). If this happens, you will get an error message when trying to run OPatch or OUI since the JRE location can no longer be found. If this happens, you can do one of the following:

H.4 ODI Client and Repository Compatibility

If you are using Oracle Data Integrator with other Oracle Fusion Middleware products, make sure you have read the Oracle Fusion Middleware Interoperability and Compatibility Guide.

Oracle strongly recommends that you use identical versions of different ODI components such as ODI Studio, ODI Console, standalone and J2EE Agents, and executable scripts for a specific site or platform. In addition, you should make sure your Master and Work Repository versions are compatible with these components (Table H-2).

Table H-2 ODI Component and Repository Compatibility

Product Component Version Repository Version

Oracle Data Integrator and,,





H.5 Need More Help?

If this appendix does not solve the problem you encountered, try looking for a solution on My Oracle Support (formerly OracleMetaLink):

If you are unable to find a solution for your problem, open a service request.