16 Data Model Troubleshooting

16.1 Installation Log Files

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:

java.io.FileNotFoundException: /<INSTALL_HOME>/inventory/Components21/
oracle.hsgbu.hc.datamodel/7.2.1.0.0/context.xml

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.

16.2 Seed Data Troubleshooting

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.

16.2.1 Error Logging and Debugging

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:

    Table 16-2 Integration ID Pattern for Tables Populated with Seed Data

    Table Name Columns to be Concatenated to Generate the Integration ID

    HDM_USER

    LOGIN

    HDM_CD_SYS

    SYS_CD~SYS_VERSION

    HDM_CD_REPOSITORY

    CD~SYS_CD~SYS_VERSION

    HDM_CD_TYP

    TYP_CD

    HDM_CD_REPOSITORY_CD_TYP

    CD~SYS_CD~ SYS_VERSION~ TYP_CD

16.2.2 Seed Data Error Types

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.

select * from HDM_CD_REPOSITORY where CD_NM = '<CODE NAME SPECIFIED IN THE ERROR STATEMENT>';

For example,

SQL> select * from HDM_CD_REPOSITORY where CD_NM = 'Patient Withdrew';

Search Code Repository for the record with the code name as specified in the Error Description.

select * from HDI_CD_REPOSITORY where CD_NM = '<CODE NAME SPECIFIED IN THE ERROR STATEMENT>';

For example,

SQL> select * from HDI_CD_REPOSITORY where CD_NM = 'Patient Withdrew';

Resolution

After identifying the code name, select one of the following options:

  • Delete the conflicting seed data record inserted by the Oracle seed data procedure (identified by the EHA user) and use your own seed data.

  • Delete the data record that you have inserted which caused the code clash and instead use the Oracle seed data record.

Resolution

After identifying the code name, select one of the following options:

  • Delete the conflicting seed data record inserted by the Oracle seed data procedure (identified by the EHA User) and use your own seed data.

  • Delete the data record that you have inserted which caused the code clash and instead use the Oracle seed data record.

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.

select * from <HDM_X_SEED_DATA_ERR_LOG.ERR_TBL_NM> where INTEGRATION_ID = '<HDM_X_SEED_DATA_ERR_LOG.ERR_INT_ID>' and CURRENT_FLG='Y';

For example,

SQL> select * from HDM_CD_REPOSITORY where INTEGRATION_ID ='SPCMN_TYP_CD_IVFEHA_CUSTOM_CD_SYS1.0' and CURRENT_FLG='Y';

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.

select * from <HDI_X_SEED_DATA_ERR_LOG.ERR_TBL_NM> t1 where INT_ID = <HDI_X_SEED_DATA_ERR_LOG.ERR_INT_ID> and SRC_CHANGED_ON_DT = (select max(SRC_CHANGED_ON_DT) from <HDI_X_SEED_DATA_ERR_LOG.ERR_TBL_NM> t2 where t1.int_id = t2.int_id);

For example,

SQL> select *from HDI_CD_REPOSITORY cr1 where INT_ID ='SPCMN_TYP_CD_ IVFEHA_CUSTOM_CD_SYS1.0' and SRC_CHANGED_ON_DT = (select max(SRC_CHANGED_ON_DT) fromHDI_CD_REPOSITORY cr2 where cr1.int_id = cr2.int_id);

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.

select * from <HDM_X_SEED_DATA_ERR_LOG.ERR_TBL_NM> where INTEGRATION_ ID=<HDM_X_SEED_DATA_ERR_LOG.ERR_INT_ID> and CURRENT_FLG='Y';

For example,

SQL> select *from HDM_CD_REPOSITORY where INTEGRATION_ID ='SPCMN_TYP_CD_IVFEHA_CUSTOM_CD_SYS1.0' and CURRENT_FLG='Y';

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.

select * from <HDM_X_SEED_DATA_ERR_LOG.ERR_TBL_NM> where INTEGRATION_ID = <HDM_X_SEED_DATA_ERR_LOG.ERR_INT_ID> and CURRENT_FLG='Y';

For example,

SQL> select * from HDM_CD_REPOSITORY where INTEGRATION_ID ='SPCMN_TYP_CD_IVFEHA_CUSTOM_CD_SYS1.0' and CURRENT_FLG='Y';

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.

select * from <HDI_X_SEED_DATA_ERR_LOG.ERR_TBL_NM> t1 where INT_ID=<HDI_X_ SEED_DATA_ERR_LOG.ERR_INT_ID> and SRC_CHANGED_ON_DT=(select max(SRC_CHANGED_ON_DT) from <HDI_X_SEED_DATA_ERR_LOG.ERR_TBL_NM> t2 where t1.int_id = t2.int_id);

For example,

SQL> select * from HDI_CD_REPOSITORY cr1 where INT_ID ='SPCMN_TYP_CD_IVFEHA_CUSTOM_CD_SYS1.0' and SRC_CHANGED_ON_DT = (select max(SRC_CHANGED_ON_DT) from HDI_CD_REPOSITORY cr2 where cr1.int_id = cr2.int_id);

Resolution

After examining the conflicting data, select one of the following options:

  • To insert Oracle seed data, modify the integration ID of the conflicting record that you have inserted and run the seed data procedure again.

  • If the Oracle supplied seed data is not required, ignore the Oracle provided seed data.

Resolution

After examining the conflicting data, you can select one of the following options:

  • To insert Oracle seed data, modify the integration ID of the conflicting record that you have inserted and run the seed data procedure again.

  • If the Oracle supplied seed data is not required, ignore the Oracle provided seed data.

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.