This chapter contains the following sections:
While installing 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 18-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 is running the |
|
|
<INSTALL_HOME>/dma_infa_master_install/dmalogs/dma_etl_install.log |
Contains a consolidated log file that is archived to <INSTALL_HOME>/ dma_infa_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_infa_master_install/dmalogs/tmplogs/<script_name>.error |
Contains an error file if the script is not executed successfully. |
|
<INSTALL_HOME>/dma_infa_master_install/dmalogs/tmplogs/<script_name>.done |
Indicates that the script is executed successfully. |
|
The installer generates the following reports: |
|
|
ORACLE_HOME/reports/dma_infa_install<time_stamp>.html |
Contains the installation summary of the Data Management Assembly for Informatica installation. |
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.
If the installer fails while executing the python script:
Review the logs.
Analyze and fix the issue.
Restart the installer with same installation home parameters.
For example, if the password expiry notification is displayed, reset the password and restart the installer.
If the installer fails while executing the ksh script:
Review the logs.
Analyze and fix the issue.
Restart the installer with same installation home parameters.
For example, if a particular directory does not have the write permission, provide the permission and restart the installer.
To skip any execution process, create a zero byte done file in the temp directory using the following steps:
Navigate to the following folders and select the appropriate script:
<INSTALL_HOME>/dma_infa_master_install/dmascripts/
Remove .ksh from the file, append .done to the file, and place a zero byte file in the temp log folder.
<INSTALL_HOME>/dma_infa_master_install/dmalogs/tmplogs