17 Data Management Assembly for Oracle Data Integrator Troubleshooting

17.1 Installation Log Files

While installing the Data Management Assembly, the installer generates the following log files. When the installer is running the python script, the execution log is redirected to the below log files:

Table 17-1 Installation Log Files

File Name Description

installActions<timestamp>.log

Records the action of the installer and can be used to diagnose issues with the installer.

oraInstall<timestamp>.out

Records the output of SQL scripts run by the installer.

oraInstall<timestamp>.err

Records the errors from the SQL scripts run by the installer.

The log files are time stamped and each installation session creates a new log file.

On a Linux machine, the log files are located at $ORACLE_BASE/oraInventory/logs.

For example, /u01/app/oraInventory/logs.

When the installer runs the ksh script, the execution log is redirected to the below log files:

<INSTALL_HOME>/dma_odi_master_install/dmalogs/dma_etl_install.log

Contains a consolidated log file that is archived to <INSTALL_ HOME>/dma_odi_master_install/dmalogs/tmplogs/ with the time stamp for next execution of the installer. In case of restart, logs are appended to the existing dma_etl_install.log file.

<INSTALL_HOME>/dma_odi_master_install/dmalogs/tmplogs/<script_name>.error

Contains an error file if the script is not executed successfully.

<INSTALL_HOME>/dma_odi_master_install/dmalogs/tmplogs/<script_name>.done

Indicates that the script is executed successfully.

The installer generates the following report:

<INSTALL_HOME>/reports/dma_odi_install<time_stamp>.html

Contains the installation summary of the Data Management Assembly for ODI installation.


17.2 Troubleshooting Guidelines

  • The OUI installer does not fix any issues automatically. If the installation fails, you must verify and fix the issues before restarting the installer.

  • You must provide unique repository schema names. The installer imports the ETL metadata into these schemas. However, upon restarting the installer for any failures, you must specify the same values that were entered for the previous execution.

  • When reporting any problems that occur during installation, make sure that you include all the above log files. Check which components were installed successfully using the following query by connecting to the enterprise schema:

    Select * from W_EHA_PRODUCT_VERSION

    Send the result of the query when reporting any problems to Oracle support.