This appendix describes solutions to common problems that you might encounter when installing Oracle Data Integrator. It contains the following sections:
If you encounter an error during installation:
Read the Oracle Fusion Middleware Release Notes for the latest updates. The most current version of the release notes is available on Oracle Technology Network:
http://www.oracle.com/technetwork/documentation/index.html#middleware
Verify your system and configuration is certified. Refer to the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document on the Oracle Fusion Middleware Supported System Configurations page:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
Verify your system meets the minimum system requirements. Refer to the System Requirements and Specifications document:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html
If you entered incorrect information on one of the installation screens, return to that screen by clicking Back until you see the screen.
If an error occurred while the installer is copying or linking files:
Note the error and review the installation log files.
Remove the failed installation by following the steps in Chapter 4, "Deinstalling Oracle Data Integrator".
Correct the issue that caused the error.
Restart the installation.
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.
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.
To create a log file of your configuration session, start the Configuration Wizard with the -log option, as shown below:
On UNIX operating systems:
./config.sh -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 Other values that can be specified with
|
|
|
Specify the level of detail you want included in your logs. The acceptable values are listed below, from most detailed to least detailed:
|
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:
Edit the ODI_ORACLE_HOME/oui/oraparam.ini (on UNIX operating systems) or ODI_ORACLE_HOME\oui\oraparam.ini (on Windows operating systems) file to point to the new JRE location.
Use the -jreLoc command line option to point to the new JRE location. See Section 2.4.2, "Starting the Installer" for more information.
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 |
11.1.1.6.0 and 11.1.1.0.7 |
04.03.04.02 |
|
11.1.1.5.0 |
04.03.03.08 |
|
|
11.1.1.3.0 |
04.03.02.04 |
|
|
10.1.3.6 |
4.2.03.01 |
|
|
10.1.3.5 |
4.2.02.01 |
|
|
10.1.3.4, 10.1.3.3, 10.1.3.2 |
4.2.01.01 |
|
|
Sunopsis |
4.2 |
4.1.02.01 |
|
4.1 |
4.1.01.01 |
|
|
4.0 |
4.0.01.01 |
|
|
3.2.0.3 |
3.2.03.01 |
If this appendix does not solve the problem you encountered, try looking for a solution on My Oracle Support (formerly OracleMetaLink):
https://support.oracle.com/
If you are unable to find a solution for your problem, open a service request.