This chapter contains the following sections:
While installing the Data Model, the installer generates the following log files:
Table 16-1 Installation Log Files
File Name | Description |
---|---|
installActions<timestamp>.log |
Records the actions of the installer and can be used to diagnose issues with the installer. |
oraInstall<timestamp>.out |
Records the output of the SQL scripts run by the installer. Database objects are installed using the Python framework. |
oraInstall<timestamp>.err |
Records the errors from the SQL scripts run by the installer. You can ignore the following error:
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. |
<INSTALL_HOME>/dm/install.err |
Contains any SQL errors. Database objects are installed using the Python framework and the error logging is redirected to this location. |
<INSTALL_HOME>/reports/dm_install<timestamp>.html |
Contains the installation summary for the Data Model installation. |
If the installation fails, check the log files for errors. You must fix the issues and rerun the installer from the installation home location.
While 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.
Seed data scripts are executed as part of the installation process for both the HDI schema and the HDM schema. The seed data that is loaded in each schema is identical although the format is specific to each of the two schemas.
These errors that occur while populating seed data using the seed data load procedures are logged in the HDM_X_SEED_DATA_ERR_LOG table for the HDM schema and the HDI_X_ SEED_DATA_ERR_LOG table for the HDI schema.
The following are the key columns in the error log table (HDM_X_SEED_DATA_ERR_ LOG or HDI_X_SEED_DATA_ERR_LOG):
ERR_ID - Unique identifier for a record in the error log table.
ERR_TBL_NM - Specifies the table name for which the error record was logged. For example, for an error in the HDM code repository will have a value HDM_CD_REPOSITORY in this column.
ERR_TYP - Indicates the type of error that is logged. There are five types of errors that can be logged. For the different types of errors, see Seed Data Error Types.
ERR_DESC - A short description of the error.
ERR_INT_ID - Indicates the integration ID of the record for which the error was logged. This column along with the error table name (ERR_TBL_NM) can be used to debug the error. The Integration ID for tables that are populated with seed data has the following pattern:
This section describes the different error types that can be logged and the resolution:
Note:
In Table 16-3, non-EHA user refers to individuals using the application.Table 16-3 Seed Data Error Types
Error Type | Description | Resolution for HDM Identification | Resolution for HDI Identification |
---|---|---|---|
Error Type - EHA_WARNING: Code name exists |
Code name: <CODE NAME> exists. New Oracle seed data record inserted with same code name. |
Search Code Repository for the record with the code name specified in the Error Description.
For example,
|
Search Code Repository for the record with the code name as specified in the Error Description.
For example,
|
Resolution After identifying the code name, select one of the following options:
|
Resolution After identifying the code name, select one of the following options:
|
||
EHA_ERROR: Insert failed: Creation of version failed |
Non-EHA user has versioned a record. Unable to create a new version of the record. |
Navigate to the table identified in HDM_X_SEED_DATA_ERR_LOG.ERR_TBL_NM and use HDM_X_SEED_DATA_ERR_LOG.ERR_INT_ID to identify the error record.
For example,
|
Navigate to the table identified in HDI_X_SEED_DATA_ERR_LOG.ERR_TBL_NM and use HDI_X_SEED_DATA_ERR_LOG.ERR_INT_ID to identify the error record.
For example,
|
Resolution This error occurs when Oracle provided seed data was previously updated and versioned by a non-EHA user. This indicates that you have taken "ownership" of the data and any subsequent updates through the Oracle seed data process are rejected with this error message. Ignore the Oracle provided seed data. |
Resolution This error occurs when Oracle provided seed data was previously updated and versioned by a non-EHA user. This indicates that you have taken "ownership" of the data and any subsequent updates through the Oracle seed data process are rejected with this error message. Ignore the Oracle provided seed data. |
||
EHA_ERROR: Update failed |
Non-EHA user has changed the record. Unable to update the record. |
Navigate to the table identified in HDM_X_SEED_DATA_ERR_LOG.ERR_TBL_NM and use HDM_X_SEED_DATA_ERR_LOG.ERR_INT_ID to identify the error record.
For example,
|
This error will not occur in HDI as no updates are supported in HDI. |
Resolution This error occurs when Oracle provided seed data has previously been updated by a non-EHA user. This indicates that you have taken "ownership" of the data and any subsequent updates through the Oracle seed data process are rejected with this error message. Ignore the Oracle provided seed data. |
|||
EHA_ERROR: Insert failed: Duplicate integration ID |
Non-EHA user has created a record with the same integration ID. Unable to create a new record. |
Navigate to the table identified in HDM_X_SEED_DATA_ERR_LOG.ERR_TBL_NM and use HDM_X_SEED_DATA_ERR_LOG.ERR_INT_ID to identify the error record.
For example,
|
Navigate to the table identified in HDI_X_SEED_DATA_ERR_LOG.ERR_TBL_NM and use HDI_X_SEED_DATA_ERR_LOG.ERR_INT_ID to identify the error record.
For example,
|
Resolution After examining the conflicting data, select one of the following options:
|
Resolution After examining the conflicting data, you can select one of the following options:
|
||
EHA_ERROR: PL/SQL_ERROR |
- |
Other PL SQL errors that are encountered when inserting seed data. |
Other PL SQL errors that are encountered when inserting seed data. |